Proper MIDI automation of controls across multiple MIDI channels?

[Christoph Hart]

Yes so basically you would need another call MidiAutomationHandler.setUseMidiChannels() and then it will also take into account the channel of the incoming MIDI message when learning is active (or if you pass in a custom JSON object you can just supply the channel you want).

[aaronventure]

@Christoph-Hart that sounds great.Thanks a lot.

Do you think there's a performance difference doing it this way and having a branch in on controller?

[Christoph Hart]

Do you think there's a performance difference doing it this way and having a branch in on controller?

Not relying on the script and doing stuff in C++ is always faster.

[aaronventure]

@Christoph-Hart Nag nag

If C++ is always faster, then it would be paramount to avoid a large branching function in on_controller when multiple MIDI channels are in play, as that by itself means there's a lot of controller data being sent into the plugin, no?

Can you please add the proposed MIDI channel property to the automation object?

[VirtualVirgin]

@aaronventure I would like to see this added to the MIDI learn function. As it is I can't use the built-in MIDI learn because it will respond to all MIDI channels of the learned CC, and with a multi-timbral setup (such as an orchestral template in a DAW) this is a no-no.

[d.healey]

@VirtualVirgin Does this happen also if you filter the MIDI channel using the settings floating tile?

[VirtualVirgin]

@d-healey said in Proper MIDI automation of controls across multiple MIDI channels?:

@VirtualVirgin Does this happen also if you filter the MIDI channel using the settings floating tile?

So I think this is what you are asking about.
The know here has been MIDI learned using CC#1 on Channel 1, and I am moving a knob on my MIDI controller sending CC#1 on Channel 2.

The Channel Filter has no effect here on the MIDI learn input.
Even if it did, it wouldn't be very useful as you would still want other channels to pass though to get to their desired destination,
To work properly, the MIDI learn itself needs channel detection and a "Channel" column needs to be added to the floating tile so the user can change it if need be.

[d.healey]

@VirtualVirgin said in Proper MIDI automation of controls across multiple MIDI channels?:

To work properly, the MIDI learn itself needs channel detection and a "Channel" column needs to be added to the floating tile so the user can change it if need be.

Ah ok, yeah that seems like a better solution. Is there a situation where you would want multiple channels to control the learned control?

[VirtualVirgin]

@d-healey said in Proper MIDI automation of controls across multiple MIDI channels?:

@VirtualVirgin said in Proper MIDI automation of controls across multiple MIDI channels?:

To work properly, the MIDI learn itself needs channel detection and a "Channel" column needs to be added to the floating tile so the user can change it if need be.

Ah ok, yeah that seems like a better solution. Is there a situation where you would want multiple channels to control the learned control?

Not off the top of my head. I'm assuming that if the user wants to control the same set of controls from more than one device, then they will map those knobs/sliders to the same MIDI channel on the different devices. That remapping is not possible on every device however, so it all depends on how many options to add for what may be minimal use cases.

[aaronventure]

@d-healey having a multi instrument or multi layer setup offering a midi channel selection for each, as well as being able to set it to "omni" like in Kontakt where it then responds to all channels

So when passing a midi channel in the object, I guess an implementation would be where we can pass either a channel integer, an away of integers or a string saying "all", or -1 or whatever react to all, the way it is now (in case the implementation requires it to have a defined midiChannel property).