while playing arround on my beloved VOS i discovered a problem.
only, if i hold the lowest key (F) and play a little on keys below, the last note mode stops working after a short time - that means i cannot hear the F anymore and a new envelope is triggered by one of those below played higher notes.
A situation just like you described can happen if you have, in the volume envelope settings, long attack and delay and sustain level down to zero. In legato mode (the default for the OS), the volume envelope is triggered when you press a key and will not be retriggered unless you let go of all the keys. If not, the envelope for the volume attack an decays this note to sustain level 0, and no other notes will sound until you let go of all the keys.
Check your attack, decay and sustain knob position in the envelope section. Bring everything back to the gray spots on the dials.
Another alternative, to pinpoint your problem is to power you OS in multi-trigger mode (hold the two upper keys while turning on the unit). You would still have to make proper settings to the envelope section, but new notes will sound at the press of any key.
Well, after a bit of trying, I can confirm there is some kind of bug with the OS and the lowest F. What I did was very similar to what waxdoctor described : pressing the key, hold it down and press other keys. The sound of the lowest key should keep on as long as is held down (after releasing other pressed keys). But very often, when two other keys are pressed at the same time, the lowest F will stop sounding and the Voyager becomes totally silent even with the Lowest F still depressed. It seems that once you have discovered the effect, if only because now you know about it, it happens more and more.
And that happened only with the lowest key of the keyboard. In the few minutes of testing, I could not duplicate the effect with any other key. The situation is minor but very real.
Yes, I also can reproduce this. Sometimes the low F will stop playing even while still held when playing notes above it. Seems to happen at random. As the others have found, I can’t get this behavior to occur with any other key.
The key scanner is the only digital component in the OS. Perhaps that’s where the problem is?
It’s simple to replicate: while holding lower F and a second higher key, press and release a third key, the second key will now retrigger and sound. Now the release the second higher key. The lower F will not retrigger and there will be no gate. Keyboard scanning is the only digital element in this synth and it appears to have a slight bug. However minor it’s still a interesting find…would have taken me years to discover.
Mine is doing the same thing. It happens every time if I hold down low F then any three other keys at once. It doesn’t seem to do it with the low F and two other keys. Quirky.
I contacted Moog and was informed that they are now aware of the problem. I received a nice email from Ryan, the tech support manager, and they’re going to look at updating the code for the keyscan board to fix this.
If you are having this issue, I suggest you get in touch with Moog’s tech support so you can be contacted directly when there is more info about a resolution.
Actually three keys isn’t important. It can happen with any number of keys depressed while holding down the low F but it happens sooner with more keys depressed. Good to hear they are working on a solution.