just been doing some experiments with using my footpedal->MPD32 to send midi auto-channel CC 112-119 to the OT, to mute/unmute a midi track which is sending drum notes to my MD, for fills.
it works really nicely, but these CCs are also used by the A4, which is further down my midi chain, and i’m getting nasty unwanted parameter changes when triggering the OT midi mute/unmutes.
i like to keep the OT and A4 on same auto-channel ,so that i dont’ have to change channel on my controller keyboard when i am composing.
any suggestions on how i can keep both boxes on the same auto-channel, and avoid this issue?
midi solutions make an event processor which i could put into the midi chain to ignore that CC on the auto-channel, but it’s an expensive way to fix one unwanted CC!
i could keep the A4 channel on FX/CV, but that’s not practical for live situations, and it’s another thing to remember which i don’t need.
A cheaper approach in the same line of the MIDI solution (I guess you are talking about the “Event processor”) it would be the iConnectivity MIDI 2+ (89.99usd)
It allows you to filter per CC/per channel, and many other goodies, check it here:
I have an Event Processor Plus, they are very versatile little gadgets.
What you could do in it (if you´d get that) is to have one setting switching another setting ON/OFF, based on a target ID you´d transmit first.
So basically you´d transmit a ‘I´m gonna play’-message of your choice (could be CC, PC or whatever MIDI message). That message turns the second setting ON which won´t pass the Auto Channel message or several messages (even just an specific range) further to your analog four. Or perhaps you want to keep them but reassign them to an different channel.
Turn the first setting OFF and it will function as an ‘I´m gonna compose’-message (inverse of the above), and that in turn will turn the second setting OFF and then let all Auto Channel messages thru again.
You are even able to have one setting turning several other settings ON/OFF, the above example is quite basic but you can do pretty advance stuff with the Event Processor Plus.
Out of curiosity (I seem to recall that you are using an iConnect unit in your setup?).
Had a quick look in the manual of the iConnectMIDI2+. And I could see that it allows remapping CC, but I couldn´t really find anything that either confirm or denies the possibility of remapping the CC value as well. Is that possible, or does it just pass on whatever value coming in exactly the same to the output? Thus no scaling or range remapping?
The USB (and USB-Audio PassThru) are appealing, too bad I don´t have any mac, Ipad or Iphone…
Out of curiosity (I seem to recall that you are using an iConnect unit in your setup?).
Had a quick look in the manual of the iConnectMIDI2+. And I could see that it allows remapping CC, but I couldn´t really find anything that either confirIm or denies the possibility of remapping the CC value as well. Is that possible, or does it just pass on whatever value coming in exactly the same to the output? Thus no scaling or range remapping?
The USB (and USB-Audio PassThru) are appealing, too bad I don´t have any mac, Ipad or Iphone…[/quote]
I´m not using it anymore, but I can test that for you if you want. Just let me find it
Btw now I´m using a MOTU midi interface and Max on Mac for all MIDI related stuff.
I didn’t use the iConnect box too much so may be I´m wrong but I think that MidiSolution stuff is more reliable than iConnectivity ones.
On my own short experience the Audio PassThru wasn’t reliable at all.
thanks gents - i like to keep my set-up as one-for-all as possible, so i reckon i may shell out for the event processor plus, and just filter out the particular CC/s on the autochannel downstream of the OT.
it’s the most compact solution, and i will doubtless find other uses for it in the future.
