No, that can’t be the reason. Then it should be the same for me too. If you continue watching the video you can see that it is not the same for other plugins and yes for others. It is also somewhere different in the menu every time. But I couldn’t recreate it.
Hi @Tim_Chandler,
I’ve taken this controller and I love it. I was wondering when you will release the integration with VST instruments?
thanks!
Alex
VST instrument integration is in progress, but I can’t provide a date I’m afraid.
For the time being use the SELECT button to map the fader to automatable parameters on the instrument and you can use Quick controls in channel mode.
CS12 does also have Nektarine integration and Nektarine can host a VST instrument and you get control that way. This of course means loading Nektarine on an instrument track first to host an instrument - which is not ideal, but it’s a good bridge for the time being given that the Nektarine instrument maps and your user edits will apply to controlCore too once we move the instrument integration fully into controlCore.
2 Likes
I keep asking myself what nice functions I could assign to user 1 and user 2 and wanted to ask you what you have added? So far I have added the gain of the selected track and the pre filter so that I can access it faster than in the EQ section in CS12.
I also read in another forum that some VSTi have been mapped to it. But that was under Logic. This doesn’t seem to be possible in Cubase or am I missing something? I can’t get it to work.
It sounds to me like you are using the USER pages as intended - parking controls that suit your particular workflow so that they are more immediately accessible.
To answer the question regarding VSTi mappings - with Logic, user mappings are stored against the plugin (in Logic’s preferences) so you can assign different layouts per plugin on the user pages.
Unfortunately with Cubase they are not per plugin and whilst you can assign a plugin parameter, it will be applied to all plugins as ‘param id ‘x’’ - so the user pages are not great for mapping plugins unless there’s a particular plugin you use on almost every track.
1 Like
Since NektarTech in general is in contact with Steinberg about MIDI Remote: do you know about mid-term plans of Steinberg to add Cubase features here similar to Logic’s approach, @Tim_Chandler ?
1 Like
No, but even if I did I couldn’t say 
We are working towards getting a solution for VSTi’s into controlCore later this year so you then won’t need that feature anyway.
2 Likes
i always map Tempo to clip gain, but I wish it was permanent!
4 Likes
yes. I almost thought that cubase was the culprit again
1 Like
yes that would be great
Well, all of the possible modes are kinda nice. At best, it should remember the last setting.
I think it’s so great that the CS12 remembers the last channel mode you were in. If you had the Cubase EQ open, for example, and then exited the channel mode and went back, you’re back in EQ mode straight away. That’s so great. It’s just a small thing but so important.
2 Likes
I have one improvement request.
If you have loaded more than 8 insert plugins and call up a plugin from the first 8 and then want to go back, you only get to inserts 9-16. You have to press twice to see the first 8 insert plugins.
Somehow it doesn’t make sense.
1 Like
I agree. That point was also mentioned in one review on Youtube btw
A new Cubase update is out. The release notes, however, don’t mention any improvements to MIDI Remote.
What? ? ? ? !
1 Like
That doesn’t necessarily mean that they didn’t fix it as they don’t list every improvement. You got to check it out yourself 
I’d be surprised if this were fixed but not mentioned
Well, basically, Nektar fixed the problem with the unavailable plugins in some projects with the last update. But I don’t know what other bugs Steinberg had.
I wonder if the VSTi’s were added to the CS12 … is this update the one they were waiting for to do that?