Quote:
Originally Posted by KevinW
So, am I to understand that when we use the new action to insert Reaeq, that the parameters will automatically be mapped to a specific controller? That would be nice (though not necessarily for Reaeq, but it's a start).
|
Sort of, but not exactly (as far as I understand). Depending on the OSC configuration, it is possible to target the parameters of the first instance of ReaEQ in a track using a fixed set of OSC message patterns, which can in turn be linked to a controller.
(I don't think it matters at all how the plugin has been inserted.)
Quote:
Originally Posted by KevinW
We already have SWS actions to insert a certain number of your favorite plugins (limited to a dozen plus or minus, IIRC). So I'm hoping that I'm understanding you correctly and that this new action does something more than just insert the plugin on the track.
I'll have to test this out later tonight...
|
I don't think the action does anything else than just insert the plugin though.
Fwiw, I'd rather look at control surface protocols and implementations such as Klinke's MCU plugin for comparison instead of those SWS actions.