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.
1 Like
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?
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.
1 Like
So, I deleted the second option (instrument open state) and disable the first, but I didn’t see any difference. Same behavior
Ok, now I see. I really had to disable and not delete it. It works this way, thanks
@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?
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.