I’m trying to allow the user to control some of the values in my plugin using key presses.
I’m debugging using Reaper.
Apparently Reaper prioritises some keystrokes/commands over others.
f.e. “arrow up” is recognised by the plugin, although it’s reaper’s shortcut for zoom in.
“alt + arrow up” and “alt + cmd + arrow up” are intercepted by reaper, those are the shortcuts for “Scroll view up” and “Go to previous track”
Studio one f.e. intercepts the “up arrow” immediately as long as it can use it and then sends it to the plugin.
I’ve also tested the AudioProcessorValueTreeDemo plugin: In the AudioPluginHost it’s possible to type spaces in the value editors. In Reaper it just plays.
Is there any way to make sense of this?