Choosing the effects in the channel strip programmatically

i have a Motif ES8 and have been trying to make my surface controller for this device
basically, it can communicate as Mackie but I wanted more
so I have Pages and subpages for example for Mix and EQ …
and have been working a great many of the projects that have been good inspiration for me such as the midiremote-userscripts/icon/platformmplus at rel-3 · woodcockr/midiremote-userscripts · GitHub

but I fail to find a sample where you can choose the effects in the stip channel like the gate or the compressor.
yes
I know how to change the values after you choose the effect
but I can’t seem to find a place where I can choose the effect on the channel strip
I know to get for example for the compressor
I need page.mHostAccess.mTrackSelection.mMixerChannel.mInsertAndStripEffects.mStripEffects.mCompressor
I can bind the parameters to knobs or buttons
but can’t figure how I would choose for example the ‘Vintage Compressor’
can some one pin point me to the correct direction

my code can be found in oussamamk/midiremote-userscripts

Welcome to this forum! Just had a quick look at your script, it looks cool!

The only way that is currently available as far as I know, doesn’t even involve MIDI Remote in reality. One can use MCU commands for step-browsing through plugins either in inserts, strip or sends. You can even browse instruments this way. This involves adding a Mackie device, have a second pair of (virtual) MIDI ports attached to it, and then send from your MIDI Remote the needed commands.
If you want to give this approach a try, you can download and inspect one of my scripts. For example, Arturia Keylab MK2 Custom Midi Remote Script ( MKII ) , Novation SL MkIII (MK3) MIDI Remote Script .
If you search the code, you’ll find areas where I share the ways to execute such actions.

Currently, I’m playing a bit with another approach, which makes the process doable without the MCU implementation, however, we need to create an external utility for properly fetching the available effects. This looks more promising, since for example we can even populate displays with multiple effects to choose from, but as said, it depends on external handling.
I will provide more info on this approach once I’m convinced it’s working as expected in different environments. And of course, it would be very cool if Steinberg implements an alternative as an addition to the MR API.Which is why I suggest that you tag your thread as a feature-request :slight_smile:

Anyway, here’s a small video demonstrating this approach:

1 Like

+1 :slight_smile:

thank you for your quick response
i am sure to explore both approaches.

if i have question hopefully you could help me.
i don’t mind if they would release their legacy API
or maybe in the future they will add the support hopefully soon.
thanks once more