Thanks, that works!
So I’ve had the CS-12 for 3 days now and after installing the “Core Control” in Cubase 14 for a second time, everything works as it should (as far as I can tell as a hobbyist user) and it exceeds all my expectations!
I have to say that I didn’t buy the CS12 primarily because of the hardware, there are comparable devices. I think what makes the device special is the integration that Nektar provides. I have numerous MIDI controllers (Novation in 3 generations, Native Instruments Maschine Mini Mk2, Maschine MK3, Maschineplus, Komplete Kontroll Keykoards in different generations and sizes, Behringer x-Touch, Nektar LX mini (love it, but it doesn’t have endless rotary controls)) and probably more in some corners and basements…
As great as the Cubase Midi Remote API is, I had problems with each of the devices when I wanted to create more complex integrations myself, jumping controllers… indifferent encoder movements depending on the rotation speed… no feedback via displays… no navigation via self-created controller pages etc.
The CS12 does all of this out-of-the-box. There are numerous videos on the internet that describe all of these functions for controlling Cubase and VST effects comprehensively and in detail, and it all works as it should for me!
But I was really excited when I discovered that VST instruments can already be controlled very well, which is what I had hoped for. There are practically no videos or tutorials on the Internet about this and I think that it would be a purchase decision for many users if the relevant information was also the focus here.
The Nektarine software, which is automatically activated on the controller when the VSTi is already mapped and hosted in Nektarine, offers an incredible depth for the operation of VSTi. With shift-Channel you can then switch back to normal Cubase control, I didn’t really understand that at first, but in my opinion it’s an essential shortcut (ok, it says so in the instructions, but I had overlooked it and it cost me a lot of time).
For VST effects you can create mappings in Nektarine, which are then automatically adopted when you load the effect plugin into an insert or send slot in Cubase as normal, yes, you don’t have to host it in Nektarine once you’ve created a mapping! This doesn’t seem to work for VSTi yet, they always have to be loaded in the Nektarine host to have the extended control.
It would be great if nektar came up with a tutorial video on controlling instruments, there were very helpful ones for the LX-Mini.
However, it took me almost 2 hours to completely map a Minimoog-like VSTi with all subpages and colors etc. It is now reaching its full potential and works almost like a hardware device! Is there a website where Nektarine mappings are officially shared by users (like Native Instruments Reaktor User Library)? That would be extremely useful!!!
So that was a lot more than I wanted to write, but I hope it helps some people to decide whether the CS-12 is their device and contains suggestions for optimizing Nektar’s VSTi integration.
Greetings Arik
2 Likes
Great feedback thanks. Controlling instruments via Nektarine is of course deeply supported (always has been!). It’s great to hear You are so happy with this solution.
ControlCore is essentially Nektarine “off track”. I don’t push the Nektarine plugin host for instrument control with Steinberg so much because it’s a currently a bridge to where we want to be.
direct instrument support will be added to ControlCore for Steinberg early this year, much of the work is already done. Any maps you make using Nektarine will then work without requiring Nektarine bc as a plugin just any more, which is the best solution all round.
Best,
Tim
2 Likes
@Tim_Chandler I took some videos and sent it to Nektar’s support and it looks like they also have some issues with Talkback assign
This is what I sent them. I’m happy to help making this a better product as we as a community will benefit from it. Dropbox
Thanks, this is helpful.
I haven’t had the report through from support just yet, but can you please confirm the steps you used to map the talkback function? I haven’t been able to reproduce the ‘double-press requirement’ issue.
The steps I used to map talkback were:
- Open the MIDI Remote tab
- Press CHANNEL on CS12 - the ‘QC controls’ appear on the top 8 knobs on the CS12 graphic in the MIDI Remote tab.
- Double-click the desired button for assignment - the Mapping Assistant opens
- In the functions browser double-click ‘ControlRoom~Talkback~talkback Active’.
- Close the Mapping Assistant. The CS12 resets (the Steinberg API recalls the initialisation method each time the mapping assistant is closed)
- Press CHANNEL on CS12 again. The button is toggling Talkback on/off with a single press as expected.
Regarding Scrub, yes I can see that issue. That function is using the jog left/right shortcuts in Cubase which essentially scrubs a frame but it’s jittery I agree. I’ll talk to Steinberg about this and that resetting issue which also appears to be the API reinitialising each time.
Understood re: Control Room.
Hi, I’ve seen this issue again in the past, and I think that using the direct access object may be more suitable than the commands.
I’ll pm you.
Arik - Just noticed you have NI gear as well as the CS12 - does the CS12 fit on the KK series keyboards? My CC121 just fits on the left side of the buttons on my S61MK3, so was wondering how well the CS12 fits. Yep … I have that “New Year GAS” problem 
Sorry, i got only 49keys on my NI Keyboard and on this one the SC12 doesn‘t fit
I ordered the CS12 and can’t wait for it to arrive, it will replace my very old bcf 2000 and will for sure do a lot more stuff in terms of plugin control
1 Like
Hi Tim,
is it possible to setup controls for Cubase’s control room on the default map page of CS12 ?
at the moment I can only assign control room volume controls etc when I am not on the default map page.
You can’t assign anything on the default page, it’s reserved for controlCore.
Channel gives 8 pages for user assignments, the first 6 automatically populated with the 6 channel strip modules.
I’m looking to add a control room mode to the fader section in the next update accessed using shift+Select as the master channel is now (user would switch to favour control room instead). Sound OK?
1 Like
I see, noted about the default page. Thanks for all you’re doing!
Yes, I did see how Channel’s 8 pages work, It’s insanely cool!
the shift+select to control the master fader is also really awesome. I myself never touch the master fader because of Cubase’s excellent control room. but some do move the master etc.
which leads me to my next point:
Cubase has so many control room functions, i.e. multiple monitor outs, headphone options, click controls, etc., I would argue that the 12 encoders and the 4 buttons on the right would be more useful as a dedicated control room section for the default page, But I understand you’re saying that the default page is reserved for the control core. I am no coder, so I have no idea if such is possible. it would just be cool to have the right side “unlocked” specifically for Control Room.
- I suppose I could create my own “control room page” from one of the user pages
but also your suggestion for the fader section will be much appreciated as well!
Yes it sounds like your best option is to dedicate a user page in CHANNEL mode to the control room. The selected Channel page is remembered so once you’ve set up the control room in that page and selected that page in Channel mode, you can switch between plugins, sends and control room with 3 dedicated buttons. Also controls mapped on those user pages are still high-res (10-bit) and benefit from the fine control button, display names and feedback.