As commented before, ATM, Nektar CS12 is not a controller to have, it’s THE controller to have.
Thanks once more for you support and costumer care @Tim_Chandler
The new ability to control VST instruments directly with the CS12 truly makes it the ultimate controller for me.
A new update is out. One improvement is that the learning mode is now working again.
A new Cubase update has been released. The MIDI Remote API has been updated to version 1.3. New in v1.3 | MIDI REMOTE API
Will we benefit from this regarding the CS12? In other words, could an update potentially be coming soon that introduces new features for the CS12? For example: (from the API documentation) Added the ability to browse and assign plugin slots.
when we select an insert slot in CS12,the plugin window it still does not open automatically. This is because people are not convinced, am I missing something or is it impossible or difficult to implement?
Thanks in advance
I’ve asked that question before, too. That’s how it works in Logic, and I’d welcome it here as well, but apparently, it’s down to the Cubase API—it doesn’t support that feature. It’s a real shame.
That would be something for a Cubase update. Might be worth asking about 
It does. In fact one can even go for opening the instrument slot and insert slots at once if desired.
@Pablin_Drummer2 and your FR is simpler.
Oh!And how can I do this with CS12? I have no idea about scripting.
That’s what support told me back then, if I recall correctly. How exactly is that supposed to work? People here are talking about a script that opens *all* the plugin windows, rather than just the one that was loaded or selected on the CS12. But I actually meant something else. Ideally, I’d like the assignment to appear automatically on the CS12 whenever I load a plugin in Cubase. That’s how it works with Quick Controls (QC), but not in “normal” mode.
That would be a great idea too; I wouldn’t mind seeing it covered—in fact, I’d like to see it implemented.
My feature request—or question—remains: whenever I tap the button for the selected insert, I’d like its interface to open automatically.
This is something that Nektar should change/add, I’m not expecting from users to alter their script.
Doable too.
Guys, both your FRs are doable, however I’m no Nektar, so I can’t and won’t comment on whether they find there requests important for a broad users tank in order to get them implemented. What I can say here, is that me in my published scripts, I tend to avoid “hybrid” approaches. My aim is that user does more and more strictly on the controller, without catching a mouse or even watching on the monitor. Perhaps at some point they feel the same way, I really don’t know.
of course, I will write to Nektar with those requests. thanks for the idea.
the idea is if there was a way to combine scripts for certain functions, not modify the original. in fact Nektar does not allow it (and there is no problem with that)
There are things doable using a combi of scripts.
In the case you describe however, and if of course I understand it correctly, the thing is that the insertsViewer object which is used in Nektar’s script, is not exposed to other scripts, i.e. each script has its own insertsViewers. This means, that we cannot “from the outside” tell, “oh now, user selected the 4th slot, so let’s open the plugin for that”.
Yeah, their decision, none of my business 
I understand the point. Thanks M.C!
Really? That would be awesome. As I said, Nektar told me it wasn’t possible because Cubase doesn’t provide the necessary support. I want that!
Well, maybe they are right and perhaps I missed what you actually want to achieve.
The way I understand it, what you want is that when you’re in a slot and change the plugin in that slot (so by default the plugin window opens) your knobs/buttons get assigned to the plugin’s controls, similarly to the Focused Quick Controls. In this case, indeed a workaround is needed, and I presented one here:
In this snippet, I don’t limit to the fx slots, but also handle the instrument slot (and track QC when no plugin window has the focus). The diff from FQC is that we are not limited to the 8 controls, but use the banking functionality for much more.
Oh, cool. I don’t know how to integrate the script, but it’s cool that it’s possible. Do I need to modify it for CS12? And will the parameter names be displayed in CS12? If not, then unfortunately it won’t work for me. The same applies if I have to edit the script itself, since I have absolutely no idea how to do that. Or maybe I’ll just ask the AI for help.
Yes.
I would suggest that you don’t. It’ an obfuscated script for a reason, I would just try to persuade the vendor to implement it.
I understand the aim of this feature request and whilst automatically opening plugins can be achieved in the API, it has knock on effects and user consequences which require careful consideration.
In DAWs where the plugin opens automatically in response the the CS12, there are two significant behaviours not present in Cubase:
- It is an api automatic or enforced behaviour - note that we receive requests from users to be able to STOP this behaviour too.
- These DAWs use a single-window plugin management system, so opening a new plugin window this way automatically replaces an existing one.
I have been resistant to this request in the past, due to the imposing nature of this operation. For every user that would like plugin window to automatically open, there is another who does not.
As far as possible, the CS12 is designed to complement existing workflow and as such we avoid non-default behaviours in DAWs.
That said, since the last ControlCore update, we can save user preferences. You are already using this feature without knowing it - the tempo dial and foot switch assignments are silently stored in the background.
This is a big step forward towards supporting customisable behaviours such as these requests. So please rest assured the requests are in consideration.