-
-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Issue
If a macro is triggered by a scene it does not fire out the OSC like the button does. A current workaround is to trigger reaper directly at the listen port with /action 1013.
Reproduce
The macro triggered by the scene cannot fire out valid osc to mimic the macro on the surface becasue you cannot add multiple arguments so in ./consoles/digico.py DigicoConsole._macro_name_handler line will not pass the conditional there.
Potential Solution
So I think there should just be a custom console that is essentially just an exposed OSC api for transport and markers.
Something like.
/reaper-link/v1/transport/play/reaper-link/v1/transport/stop/reaper-link/v1/transport/record/reaper-link/v1/marker marker-name/reaper-link/v1/mode <recording | playback-tracking | playback-no-track>
As an aside, I have been trying to write my OSC apis to be very specific and with a version tag. The opposite example is reaper which is like /action 1013 which does not tell you at all what the message is supposed to do at first glance nor is it unique in the industry.