Hi Amos and till
Amos wrote:The touch pad does not send MIDI by default, I don't think... I thought you always had to go in and edit your patch to assign specific MIDI CC numbers to the different touch pad axes, if you wanted it to send MIDI. This setting is saved per patch, so after you make these changes you need to re-save the patch for the changes to persist. Is this different now than it used to be?
Well, yes it is different now in the way that the panel controls are also disconnected from the Voyager when set to local off. And since as of your statement the touch pad doesn'd send MIDI by default, the Voyager no longer responds to incoming touch pad MIDI data when connected to itself via the MIDI patch bay. And I can't use it in local on mode.
But let me explain a bit:
I use a live setup with four keyboards, one of which is the Voyager. I also have a couple of expander modules. All of these are connected to the MIDI patch bay and all of the keyboards are in local off mode. This way I can route all of the instruments independently - routing, merging, layering, splitting - you name it. And this may change for every song in the set, so it's not a static connection.
For example - in one song, the voyager's keyboard will be routed to an expander module and the voyager will be played from another keyboard. In the next song, the Voyager will be connected to itself plus a layer of strings from a different instrument and so on.
So this is why local control is very important for my setup.
I hope I did make some sense in this explanation
