View Single Post
Old 01-08-2018, 05:57 PM   #4
goldenarpharazon
Human being with feelings
 
Join Date: Feb 2016
Posts: 134
Default

MIDIACTION and MIDILISTACTION

probably exist to call actions from the

"Midi Editor Actions" and "Midi Event List Editor"
action sections respectively.

Command IDs are not unique between Reaper "action sections"

If 987 "Adjust solo in front dim (MIDI CC/mousewheel only)" is wanted as the call, then call this via ACTION - probably call it via syntax f/action/@/cc ?

But if Command ID 989 is called via MIDIACTION or MIDILISTACTION its function will be different to when called via ACTION. The easiest way to see this difference in Command IDs is to look very closely at the action list in the "Show Action List" window whilst also showing Command IDs. Knowing this difference then leaves you calling the desired action along with appropriate parameter for ACTION where a parameter is allowed.

MIDIACTION and MIDILISTACTION calls will not take more parameters beyond a toggle, inferring from the range of strings already predefined in .ReaperOSC

Good luck using and pushing the Reaper OSC implementation boundaries!

Last edited by goldenarpharazon; 01-08-2018 at 06:29 PM.
goldenarpharazon is offline   Reply With Quote