Quote:
Originally Posted by schwa
It works unless the note channel is not included in the filter channels, right? This was unfortunately necessary. There is a lot of existing logic in the MIDI editor that requires the channel for new events to be included in the filter.
|
Whouldn't simply including the new channel in the filter (if it isn't already) meet that requirement?
And
if only a single channel is included when a change of "channel for new events" is triggered by the function,
then
swap the previously included channel with the new one instead of just adding the new channel.
That way the channel for new events is automatically always included in the filter and it stays a single one if it was single in the first place.
That's how Juliansadders script does it.
For a reasonable workflow with MPE data it is sometimes necessary to have the filter set to exclusively the same channel as the channel for new events. The idea is to have all channels visible ("show only events that pass filter" disabled) and nevertheless keep CC data from other channels from being selected by a marquee selection.
The only way at the moment would be to filter all other channels from view, but then we'd need to constantly switch the filter on and off each time we want to select another note to edit the controller data for. Which is not a good solution at all.
Btw, Julians script also works when selecting a single CC, which is really useful as well, because we can keep the mouse in the CC lane.
here's a licecap of Julian's script plus the midi filter (done with an older Reaper version on my almost abandoned PC, because Licecap seems to be acting up on my MacBook, so please excuse the janky mouse movement)
Again, the swapping is only done when a single channel is set in the filter. If there are multiple channels, the previous channel just stays included.