Benjamin Klum

No, there's no way to pass such "IDs" when executing REAPER actions. Each user-defined compartment action will automatically become visible in REAPER's action list (as long as that ReaLearn instance...

They will disappear but their key bindings will stay (otherwise it would be a pity). In this regard, they will behave exactly like existing ReaLearn actions (search for "ReaLearn" in...

The indicator is subtle, yes. But I can't say it's barely visible, also on macOS. Also, please note that it doesn't light up on mappings with virtual targets at the...

Thanks for the reply. Yes, I'm aware of these downsides. It was intended as a quick solution that improves one particular issue, without going "all in" ;) But of course,...

@glowcoil I would like to work on the "defer" approach. Or are you already at it? If not, I think this `defer` mechanism can be something purely internal. I would...

Oh man, that sounds aweful, happening before a concert. I never had such an issue and I don't see any way in which ReaLearn could ever break MIDI ... except...

Another thing: Don't enable the MIDI input device "+ control", just enable it normally. Also, make sure your MIDI device isn't used elsewhere, e.g. in the "Control surface" section of...

Okay. Just a note: You don't need to use ``. Setting "Control input" to a particular device *is* good and the normal way of doing things, you just need to...

> But even when I restarted Reaper and started a new project to test MIDI (without any instance of ReaLearn) it was still silent. It's also curious why it was...

> I never even used any ReaLearn instance, but MIDI input from my controller was broken straight away (or well, silent). Not sure I understand. How could you tell that...