Every MIDI CCs are forced to merge into MIDI CH1.
-
- KVRist
- 355 posts since 30 Jun, 2009 from moon
deleted
Last edited by replicant X on Tue Mar 26, 2024 1:35 am, edited 1 time in total.
Speedrum 2 is a hidden gem. 
-
- KVRist
- Topic Starter
- 355 posts since 30 Jun, 2009 from moon
deleted
Last edited by replicant X on Tue Mar 26, 2024 1:34 am, edited 1 time in total.
Speedrum 2 is a hidden gem. 
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
The MIDI Focus is all about where the incoming MIDI is sent to. So it's not only a matter of indicating a module aka plugin, but also about which channel. That's what the focused channel is. Imagine 2 tracks, both targetting the same synth X, first track is on channel 1, the other track on channel 2. Now when you select track 1, synth X becomes the focused module and focused channel is 1. If you select track 2 the synth X still is the focused module but focused channel now is 2 so incoming MIDI is playing synth X on the selected = focused channel. Hope that explains it.
NB I double-checked it and it works fine as expected for all events, also controllers. Note that if you map a controller, then that mapping will get priority above the default routing explained above.
NB I double-checked it and it works fine as expected for all events, also controllers. Note that if you map a controller, then that mapping will get priority above the default routing explained above.
-
- KVRist
- Topic Starter
- 355 posts since 30 Jun, 2009 from moon
deleted
Last edited by replicant X on Tue Mar 26, 2024 1:34 am, edited 1 time in total.
Speedrum 2 is a hidden gem. 
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Ok so in the specific case you want to use a different MIDI channel per event, then in the sequence editor right-click -> Editor -> Choose Focused MIDI Channel. That will define the channel for newly drawn notes AND for MIDI input.
Also see: http://www.mutools.com/info/docs/mulab/ ... ditor.html
Also see: http://www.mutools.com/info/docs/mulab/ ... ditor.html
