I find myself quite often having issues with rouge MIDI messages coming in from unintended sources (that creates virtual out channels when used). Logic Pro external instruments, Divisimate, Vienna instruments MIDI, and also patch changes from different controllers that mess with whatever I am working on in MG3. I believe we have adressed this before, but it would be great to have a place where we could decide on which messages we want to use with simple check box system or something similar.
How do you guys solve this, right now? Any suggestions?
Great suggestion. I have on my list to redo the screen with the CC envelopes. I guess you would want filtering based on the CCs number or its midi channel?
Funny how ideas like these all arrive at around the same time.
These days I’m getting heavily into Gig Performer and using scripts for filtering to exert control over the signal flow of MIDI. Scripting is a bit of a headache, but it certainly makes for cleaner use.
Also, the primary audio/MIDI interface I use has pretty extensive MIDI remapping and filtering options, both of which help greatly when unwelcome signals land on your musical doorstep.
I am actually thinking about filtering MIDI controller sources entirely. Like a check box option for the MIDI Patch bay “MIDI Controller List”. I am sure a MIDI message block/filter inside MG3 (somewhere in the chains?) is an interesting option too, but this is more fundamental (or global perhaps?).
Midi filtering controller sources as well as filtering cc and program change messages would definitely be welcome. I personally have quite a few midi devices that would be desirable to filter out sending midi commands to MG3.
