Skip to main content

ARP Omni repair - trouble with ADSR

I purchased my Omni totally non functional in 2012. I came across all the issues: oxidized contacts and sliders, bad caps, dead CI, bad solder joints. However, I still have an issue with the envelope generator.

The envelope generators

The ARP Omni has 2 sections, each one with an envelope generator.
  • The string section has an AR (Attack-Release) envelope
  • The synth section has an ADSR (Attack-Decay-Sustain-Release) envelope
Both envelope generators are triggered with the keyboard. One important thing: the AR envelope drives the overall volume. In other words, a short release on the AR will cut the volume of the synth section, no matter how long is the Release on the ADSR. The

The issues

String's AR envelope: Attack is always short, Release is OK. Synth's ADSR: some combinations of settings don't produce the expected results.
I then draw a table of the combinations of A, D, S and R I've tested (with VCF FREQ half, VCF ADSR full, other sliders down). The idea was to find a pattern, but no luck, unfortunately.

The Fix

After some time on the workbench, I finally noticed that monitoring pin 1 of Z4 with my scope changed the behavior of the ADSR! Z4 is a quad NAND gate in CMOS (CD4011UDE). CMOS are sensitive to ESD; could this be a bad gate? I changed both Z3 and Z4 and ... the problem was gone!

I've checked both chips on breadboard, and yes, both had one bad gate.

Conclusion

Always have a couple of CMOS in spare.

Update

I noticed after some time the issue with the Synthesizer envelope was not gone. I suspected the sliders (which I had already cleaned up, but were still pretty stiff) so I decided to install the Precision Kit from Synthchaser. When I install the new sliders on the String Control board, a green capacitor (BREL) fell down: one leg was unnoticedly broken, the second just broke. Once the capacitor replaced, everything worked perfectly!

Labels:

Comments

Post a Comment

Popular posts from this blog

Drive replacement for Fostex DMT8-vl

The IDE hard drive on my Fostex DMT8-vl multitrack recorder shows signs of its imminent death; when getting hot, I could not record anymore. Must be said this drive comes from an old Sun Station, and has been replaced because I/O failures were detected by Solaris. It worked at least 5 years in my recorder: not so bad. However, time is now to replace it. The DMT8-vl is not able to handle drives bigger than 8.4 GB. Well, it is able to (the current drive is 15 GB), but only 8.4 GB will be usable. My tought was to use a 8 GB CompactFlash; having no moving parts means no noise, which is quite temptating for a music recording device. I purchased a CompactFlash-IDE adapter on the internet (8$) and I had to build a male-male IDE cable adapter (4$). Unfortunately, this doesn't work. The drive is correctly discovered by the operating system, which proposes to format it ("format IDE?"). After answering "yes", the formating runs pretty fast (faster than on a real drive), ...
6 comments
Read more

Samba: Clients get "system error 1223" (or 123) after a server reboot

Facts: a Linux+Samba server shares anonymously a folder. After a reboot, Win clients could not attach the share drive anymore. C:\>net use \\mylinux\folder Enter the user name for 'mylinux': System error 1223 has occurred. The operation was canceled by the user. C:\>net view \\mylinux\ System error 123 has occurred. The filename, directory name, or volume label syntax is incorrect. The process are present, and tcpdump doesn't provide much information. What's going on? After hours of headscratching, the light came: the firewall was on and no rules for the Samba protocol! Grrr!
2 comments
Read more

Issue with Soundpool MO4

I have a Atari STe with a Soundpool MO4 MIDI extension. It used to work very well, but unfortunatelly doesn't anymore: Cubase still detects it, and I can output MIDI to it but nothing is coming out from any MIDI Out. It took me a while to tackle it (lack of time, lack of tool, other items to play with), but I gave a glance last week-end. The parallel port on the Atari uses only the following signals: Pin 1 : Strobe (Atari -> MO4) Pin 2 : Data 0 (Atari -> MO4) Pin 3 : Data 1 (Atari -> MO4) Pin 4 : Data 2 (Atari -> MO4) Pin 5 : Data 3 (Atari -> MO4) Pin 6 : Data 4 (Atari -> MO4) Pin 7 : Data 5 (Atari -> MO4) Pin 8 : Data 6 (Atari -> MO4) Pin 9 : Data 7 (Atari -> MO4) Pin 11: Busy (MO4 -> Atari) The MO4 also decodes few other pins, but since the Atari doesn't, my guess is the MO4 was also targeted for PC. Inside the box, the MO4 is architectured around a CPLD (IspLSI1016 from Lattice) which contains the logi...
7 comments
Read more