Big deal! Integration looks amazing, as shown here. Video also shows off the occasional (for most of us, frequent) midi remote disconnection issue that’s still not fixed. Still, it looks like an extremely useful device that replaces the 121 and then some!
Introducing the Waves IDX Intelligent Dynamics Plugin
More info here:
CS12: Cubase & Nuendo - Nektar
Hi,
By any chance, do you know, if Nektar is using its own component, or of they are using MIDI Remote? Just wondering…
This.
Is Nektars midi remote script anywhere available?
Man I’ve been waiting for this since it was announced a year or two ago, and was so bummed it was only for Logic when it finally came out. Might have to grab one now!!!
I think Nektartech always provides the related installation files in the account of a user who purchased whichever product. Reading the manual, I saw that they’re using a combi of midi remote, an external app called ControlCore, and VST mapping files in order to provide the deep DAW integration they usually offer.
Interesting, would have been nice to have a look at how they do their midi remote script for learning/inspirational purposes.
Then perhaps you could try your luck asking Tim Chandler from Nektar Tech.
Thanks for that link, I just asked Tim about it 
Thanks for the post. I just ordered one from Vintage King. I will give it a test drive.
Finally got to testing it out and everything is working great in Cubase! Controlling instruments, writing automation with the rotary and fader plus other basic operations. Great job Nektar/Tim!
How do the encoders feel? Do they have a good resolution?
I’ve got the P1 since years, really love they way to use it, but the encoders feel so cheap, compared to Komplete kontrol for example…
What do you think about them?
Definitely a subjective topic, but I think they are good resolution and you have the option to press a magnifier button to make the resolution even finer as needed. The feel is also good to me - very close to an Ableton Push knob but I do prefer the Komplete mk3 knobs which are metal and have grips for easier control IMHO.
I finally got mine today from vintage king. First impression, I agree with @BlueJava as far as the feel of the encoder. I have the Komplete 61 MK3 as well and the feel is better on the Komplete MK3 61, but it is also double the price of the CS12.
I really like it overall from first impression. Keep in mind this is my first day with it. It feels good, all of cubase plugins are mapped, arturia, etc. I have a few that are not, like my plugins from Apogee. Tried to map those in nektarine but the software is not very intuitive and I could not get my mapping to update outside of using nektarine, not sure if that’s possible.
got mine last week. was insanely frustrated because the mapping for 3rd party plugins was not working, after many hours of trouble shooting, I discovered the cs 12 3rd party plugin mapping doesn’t not work with C14.0.10 but does with C14.0.05
not sure which company needs to know this, but probably both!
the CS12 is a great controller and is fully mapped to work with all stock features and plugins in cubase, but the 3rd party mapping for other companies like Plugin Allience needs to be worked on. FYI
I wouldn’t recommend using v14.0.5 it’s using old api methods of mapping and much slower. But if you’re getting by with it for now that’s ok of course!
3rd party plugin mapping works except for plugin alliance and a few others.
This issue has been fixed already and will be in the next update. We’ll get it out in the next week or so.
Im going to order a CS12 next week.im very excited about this machine!
Thanks for providing feedback Tim. I am having issues with some of Arturia, Apogee, Brainworx, Native Instruments, etc. Hopefully this update allows me to resolve these.
Thank Tim.
another observation, I use +12db as max volume for my faders in my project settings, so when I reset to zero with the controller, it goes to +1.95db instead of zero
Great feedback, thanks! That’s a feature I was unaware of but should be a simple fix.
Regarding specific plugin issues, I can’t guarantee they are fixed without having a better idea o fly what they are. All plugins have certain restrictions - cs12 sees thatched sees, that is automatable parameters. The issue fixed has some further filtering improved as it was blocking parameter ids reported by Plugin Alliance and done others.
This update should address all automatable parameter access issues.