Page 1 of 1

Voyager ignores external velocity

Posted: Tue Feb 21, 2017 4:04 pm
by trebmonster
When I play from another keyboard (Kronos or Blofeld) via midi, the Voyager does not respond to velocity. Playing the Voyager keyboard responds to velocity fine. With the external keyboard, each note has a different velocity and is stuck at that level, for example F#4 is stuck at high velocity value and G4 is stuck at mid velocity value. What the hell is happening???

I've disconnected the cable to the VX351 and no other CVs are connected - all there is is midi in (direct to midi out of another keyboard) and audio out to my mixer.

If I go in Master settings and change Local Control to Off then the external keyboard works correctly again (but the Voyager keyboard (correctly) doesn't. This must be a clue!

Help!

Thanks

Re: Voyager ignores external velocity

Posted: Tue Feb 21, 2017 6:29 pm
by MC
Go to Edit->Keyboard Modes and set it to "last key" or "1 key only"

It's a quirk of the Voyager being a monophonic synth whose integral keyboard can generate polyphonic MIDI key data. With keyboard mode in low priority (the default), the Voyager retains velocity data for independent keys. Same with high priority. When you use a MIDI controller, the Voyager ignores MIDI velocity and uses the last known velocity of the integral keyboard.

The Voyager is also capable of chaining multiple Voyagers for a polyphonic system.

That's the practical way to implement polyphonic chaining using a "master" Voyager as a MIDI controller. Nature of the beast. Nothing is malfunctioning.

Using "last key" or " 1 key only" gets around this.

We really need a sticky "FAQ" thread as this question pops up often. Mods?

Re: Voyager ignores external velocity

Posted: Tue Feb 21, 2017 6:37 pm
by trebmonster
Fantastic - many thanks. So I've now got to go through 1000 patches and edit them! There's no global way to do this?