06-17-2022, 03:43 AM
(This post was last modified: 06-21-2022, 11:53 PM by Lizard of Oz.)
(11-10-2021, 02:53 PM)User Wrote: Maybe I shouldn't take care of that, but I have just idea to reduce of "flying" midi commands to output devices. Some of gears use only one, or two input channels. As there is input/output filtering for CC/Note/Clock etc comments, it could be useful (for "cleaning" / optimize reason) to select active midi channel(s) and all different that defined will be ignored.
Now if i allow routing from my sequencer (for example 4 channels CH1-CH4) to all synths, this will send every midi commands to each of them, for all channels. If I define that my synth on OUT1 use only CH1 then all commands sent to CH2, CH3, CH4 will be ignored on OUT1.
+1
I find that most of the routings I make routings actually route one more channels - and not all data from one port - and I have to set up the devices in a way so that the other channels don't get in the way.
So I think channel filtering is also helpful for the routings (pre-modifiers, as the other filters are), and that way port filters and routing filters would remain consistent.
Problem with a channel filter: you need 16 toggles, and one would need to find a way to add that to the interface in a way that it is still manageable. Maybe one tab-stop of 4x4 dots, and if you click ENTER on that, it zooms to a bigger square and you can select each channel via up/down and toggle it on/off via ENTER. Press STANDBY/ESCAPE to zoom out again.
Edit: clarification.