Opening All Insert Slots And/Or Instrument Plugin upon changing (the selected) track

[m.c]

Yes but if you use a real keyboard, the value sent will be the note velocity.
So you’ll have to replace value==1 in the script, with value>0 in order to cover all velocities.

[doriosypos]

Thanks, I did change that and it is working fine.
I noticed that when this function is deactivated, open a new plugin window and then move to another track, still close any plugin window that is open. I assume that this is what we expect from the script.
Is there a way to change this behavior, and keep the windows open?

[m.c]

The way that the script works is to check whether we have BOTH options disabled, and then, yes, it will not move to closing all windows. If one of them is active, it will close everything.
Sure, one can work out more complex solutions but this would need some additional steps: Registering the open Instrument plugin Ids, and then when we execute the command for closing all plugin windows (this doesn’t differentiate instrument from fx plugins) restore them.

[doriosypos]

So, I deleted the second option (instrument open state) and disable the first, but I didn’t see any difference. Same behavior

[doriosypos]

Ok, now I see. I really had to disable and not delete it. It works this way, thanks

[Pressure_Cooker]

@m.c This is incredibly helpful, thanks. I wish Steinberg made this a native option.
They did it with the surround panner, and its amazing.

One question - how do you get around having all the plugins open in different places?

[m.c]

@Pressure_Cooker

One question - how do you get around having all the plugins open in different places?

Hi, I don’t This script was a follow-up to some users’ posts, I don’t personally use it.
If I had to use it, I would most probably create a small app which would tile the plugin windows. Perhaps I give this a try, if that’s what you’re talking about.

[Frederic_Auger]

MIDI Remote API v1.3 !!!

[m.c]

Yes, it’s been out for a while. You can have a look at how I implemented the plugin browsing (new to 1.3) in this example:

An HTML-based MIDI Remote demonstrating additions in MR API 1.3

Here’s an HTML-based MIDI Remote surface, mainly for demonstrating the addition of the Plugin Manager in MIDI Remote API 1.3 (introduced with Cubase 15.0.20) which I was very happy to see! Plugin Manager lets devs have access to all the instrument/fx plugins and insert them to instrument/fx slots, by using their UIDs as provided by the API. The mechanism is straight forward, however, there’s always a place for snippets, so I decided to provide one. At the same time, in this surface I’ve built,…

[Frederic_Auger]

I don’t quite understand what this remote control can offer me that’s different? Will you be integrating these new features into the Novation MK3? And on that subject, because I admit I’m lost in these forums, what is the latest version of your script and where can I find it? That’s a lot of questions, sorry

[m.c]

@Frederic_Auger

I don’t quite understand what this remote control can offer me that’s different?

It has the functionality of browsing through plugins for the instrument and the inserts slots.
Thought you wanted to see how new features are implemented, this is why I linked to it.

@Frederic_Auger

Will you be integrating these new features into the Novation MK3?

Yes, at some point.

@Frederic_Auger

what is the latest version of your script and where can I find it?

Haven’t changed for a while now. It’s always in the first post of the dedicated thread: Novation SL MkIII (MK3) MIDI Remote Script