First off, I’m very happy with my new Voyager! - The Keys and controls feel very solid and reliable (very impressed)… I have been particularly inspired by the Touch Screen… checking out the presets and wiggling my finger on the TS I find it a very expressive and creative tool…
Its when I finally got around to connecting it to a sequencer that I discovered its limitations… searching this forum my fears were confirmed… Only the MSB is sent and it doesn’t seem to respond to 25% or 50% values, etc
With the 3.4 OS (which was what the unit was shipped with) giving better resolution when more than 1 pot is altered surely the next logical step would be for the TS to send both MSB and LSB and conform to the 25% or 50% settings for the amount of modulation??? I’ve also noticed it does not go back to the original parameters when the TS gate is off (even if the memory option is off). Couldn’t it send the original parameters when the gate is off to allow this performance feature?? (great with rhythmical movements)
My next project will be mainly midi based and I really want to take advantage of the Touch Sceen… although at the moment it seems impossible to recreate the effects of the ‘non-midi’ touchscreen when using it with a sequencer.
Scaling of outgoing data should not be done by the sender, but by the receiving midi instrument. That is the way the MIDI specs were done. One very common example is pitch bend:
you would not like to reduce the sended pitch bend for a certain range of values und less you have all synths available set to the very same pitch bend range. And of cause to use the pitch bend data to change the pitch.
But I really hope (I am not using midi other then sysex) the Voyager is scaling ingoing data the way the preset scales the TS data played live on the instrument.
But you are right: if you use the TS to modify external other synths filters or other parameters, some scaling would be nice, because I don’t know of a synth scaling each individual ingoing CC to a certain amount. But what you are asking for is a master keyboard/controller function. And this is not the prime usage of a Voyager. There are other more important things for a next OS update I would like to see. For example a way to lock the Voyager storage from being altered. Just like the Memory Moog had the number code to protect the memory. Of cause this protection should also work on sysex data going in. But of cause there should be a way of turing this function off when you are at home in your studio.