This can be helpful to predictably filter out MIDI and keyboard events.
Normally, using "Let through: [ ] Matched [x] Unmatched" filters out MIDI events if at least one control-enabled mapping source conforms to the event - but only if the mapping is active (= actually triggered). This is a very dynamic behavior, but it can be unwanted in some situations.
With the proposed unit option "Match even inactive mappings" enabled, ReaLearn would filter out MIDI events even if the matching mappings are inactive.
This option would also affect if keyboard input is let through to REAPER or not. If at least one mapping uses a key in a control-enabled mapping, it will be filtered out. Even if it is inactive.
Controller mappings with virtual targets will only match if there's at least one associated main mapping that matches.
This can be helpful to predictably filter out MIDI and keyboard events.
Normally, using "Let through: [ ] Matched [x] Unmatched" filters out MIDI events if at least one control-enabled mapping source conforms to the event - but only if the mapping is active (= actually triggered). This is a very dynamic behavior, but it can be unwanted in some situations.
With the proposed unit option "Match even inactive mappings" enabled, ReaLearn would filter out MIDI events even if the matching mappings are inactive.
This option would also affect if keyboard input is let through to REAPER or not. If at least one mapping uses a key in a control-enabled mapping, it will be filtered out. Even if it is inactive.
Controller mappings with virtual targets will only match if there's at least one associated main mapping that matches.