I'll post the relevant quote:
And a response:Microtonic has two modes for RECEIVING midi. In one mode, note C1 triggers the first pad, usually the kick; C1# triggers the next pad; and so on. All of this occurs on the same midi channel.
The other midi mode allows you to play each pad in various pitches. So on midi channel 1, you can play up and down your keyboard and the first pad, usually kick, will play at various pitches...low if you send C1, the default pitch at C3, and high pitch at C5. If you SEND notes on midi channels 2 through 8, you should be able to trigger each of the other pads in the same manner, where the pitch of the pad is determined by the note you send.
In FL Studio, I tested this and it works fine. As I select different midi channels, Microtonic plays the different pads. In Live 5, no matter what channel I choose, Microtonic only plays the first drum pad in various pitches. This problem does not have to do with multiple outputs. It has to do with Microtonic receiving different midi channels in Live. My guess is that I am not sending the correct midi channel information to Microtonic in Live.
yes: you are right in that its how Live handles the midi routing thats the problem
we have the same problem with fxspansion GURU: GURU has 8 "engines" in the same instance - each engine has its own set of 16 trigger pads and each engine is potentially trigger on a consecutive midi channel.
so for instance: Engine 1 should be triggered by input coming on MIDI ch1, Engine 2 on MIDI 2 ... etc ..
but it doesnt. if i try and use my triggerfinger multichannel and route MIDI ch2 into GURU, it always plays engine 1.
I dont pretend to fully understand why - i figured out how to get full use out of it for my purposes ... but we determined with the help of fxSpansion that it is definitely in how Live routes its MIDI and not in how GURU is handling it. thread here:
http://www.kvraudio.com/forum/viewtopic ... =guru+live
