View Single Post
Old 03-02-2018, 11:20 PM   #56
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,689
Default

Quote:
Originally Posted by pipelineaudio View Post
could we call command ID's instead of CC's as well? Or is that only for scripts?
No.

(As discussed in the other thread) JSFXes resides in the "Midi realm" of the track FX chains, while Actions (via learn) reside in the Midi realm of the Reaper control path, and hence JSFXes know nothing at all about or have any access to Reaper "Actions". (While OTOH ReaScripts reside in the realm of the Control Path and hence can't "directly communicate" with Track plugins such as JSFXes.)

So the only way to access Actions from a JSFX is using MidiToReaControlPath.

This is the way Reaper works, and it does make sense, even if it seems to be hard to fully understand for many.

A reason might be that in the realm of tracks, Midi messages are timed by the audio blocks processed, and use the OS/CPU threads dedicated to audio processing, while in the realm of the Control Path, Midi messages are not timed, but used "on the spot" and supposedly use the OS/CPU thread dedicated for the Reaper GUI.

Of course a built-in MidiToReaControlPath functionality would make sense, but installing MidiToReaControlPath is not hard to do at all.

-Michael

Last edited by mschnell; 03-02-2018 at 11:48 PM.
mschnell is online now   Reply With Quote