Yes saved. All my other assignments remain , the rotary encoders.
except for the 4 buttons. They “remain” but somehow all jump onto the last button, so they are all layered into one button and therefore don’t work
Yes saved. All my other assignments remain , the rotary encoders.
except for the 4 buttons. They “remain” but somehow all jump onto the last button, so they are all layered into one button and therefore don’t work
this has been fixed, Thanks @Tim_Chandler
This too had been fixed! Thanks @Tim_Chandler
There are very few functions of the CS12, which do not seem to work (at least for me). Unfortunately, there are two topic threads on this forum, and I posted my input there already:
https://forums.steinberg.net/t/interesting-development-from-nektar-cc121-part-ii/895883/62?u=northunder
Since I do not want to double-post / cross-post, I at least link the post here.
@Tim_Chandler - three small points on the CS12:
Thanks for the great work, which you & Nektar do here.
@Tim_Chandler - Thank you so much for demoing this to us at NAMM. The integration is absolutely fantastic and you guys really thought about the workflow. Absolutely loving it. Ordered for two desks!
What confuses me: The note enclosed in the box states that the CS12 requires a USB connection with “high power” to be fully supplied. It also states that an optional power supply requires 5V / 1A. And with that, a USB 3.2 connection is NOT sufficient according to this table.
This is also my experience. When I connected the CS12 to a USB-A 3.2 port directly to the DAW, the power symbol did not appear in green on the display.
I then connected it to a USB-C port (3.2 G2x2). So USB-C to USB-C.
Why then include a USB-C to USB-A cable?!
Furthermore, there is no description of what the consequences are if the CS12 is not fully supplied and the power symbol is not green. Incidentally, this is described in the manual. The linked troubleshooting from the manual doesn’t really help either.
There are three ways to access the plug-in assignment on the CS12 and to open/close the plug-in GUI:
If you first press and hold the [Plug-In] button and then press the [Slot]
a. Plugin GUI opens/closes
b. no assignment to the CS12 takes place (but the display continues to show the overview of the inserts)
If you first press the button for the [Slot] and then the [Plugin] button
a. Plugin GUI opens/closes
b. the CS12 display shows the CS12 assignment and distributes it to the pots
You just press the corresponding [Slot] button
a. the CS12 display shows the CS12 assignment and distributes it to the pots
b. the plugin GUI remains closed
I think it would be great if there was some way to customize what happens when you simply press the [Slot] key (i.e. variants 1-3). I think I need the visual feedback of the plugin GUI rather than blindly turning the knobs as in variant 3… So I would like it if, when you just press the [Slot], the CS12 assignment and the plugin GUI are called up.
Thanks for the User guide update suggestions. Some answers to your questions below:
Unfortunately it’s a green LED not RGB. Something for a mk2 version.
Category | Color |
---|---|
EQ | Blue |
Reverb | Orange |
Delay | Amber |
Filter | Blue2 |
Compressors | Red |
Dynamics | Red2 |
Distortion | Purple |
Modulation | Yellow |
Pitch | teal |
Green is reserved for Instruments (coming in an update)
So the plugin mapping, and colors are all handled by controlCore. Many editing features are available directly on the CS12.
At the moment, Nektarine is providing a bridge for more detailed editing outside of controlCore such as creating and naming new pages and renaming parameters.
My advice is to edit on the device as far as possible. When you open the plugin in Netkarine, be sure to use the VST3 version as that is what Cubase is seeing.
USB power is decidedly unpredictable. We found for example particularly with some Macs USB-A type ports report as low power, when the powers perfectly adequate.
There isn’t really a drastic consequence of using the device low power. If power is not sufficient, you will notice obvious powering issues such as button LEDs dimming as the motor on the fader is engaged.
yes, that’s how I did it too. First I mapped all the plugins with the cs12 and if necessary then renamed the pots in nectarine or added pages. I use 90% vst3
Thanks a lot, @Tim_Chandler - appreciated.
Regarding the green LED: but it’s illuminated in white when no Cubase project is opened?!?
We use dual LEDs apart from the section right of the display which are RGBs.
Ok, understood. Thanks for the clarification, @Tim_Chandler
@Tim_Chandler
Hi Tim, (I don’t know if I’ve asked it elsewhere or if the question hasn’t been posted, but I’ll ask it again here) The active inserts are shown in Blue on the CS12 screen. Would it be possible to put them in another color? (until Cubase 12 my insertions were in blue, for easy reading) since 13, they are Orange. Is it possible, or will it be in the future?
Another question,
would it be possible, for example, to change the behavior of some buttons (undo and redo, for example) Thank you, and keep up your great work!!! I’m looking forward to my Cs12
for me the inserts are also blue in cubase 13 and 14. maybe have a look in the settings
I was referring to Cs12, yes it is possible, or the color can be changed.
Just to avoid misunderstandings:
@Pablin_Drummer2 : you wrote that your Cubase 13 displays in orange, not the CS12. But Cubase 13 and Cubase 14 display those in blue per default, so the question is whether you changed something in Cubase preferences?!?
I attach an image so that it is better understood (English is not my first language, sorry for the confusion) My cubase looks like this (see image) my question was, if in the CS12 you can change the color of the inserts that by default is blue, orange (in my case)
It’s not that it’s a problem for me, I can use blue in Cubase, but I think it would be a good option for CS12 to be able to set the color of the inserts to the user’s taste (to maintain consistency), right?