Is the functionality solid with C15? Thinking of upgrading my CC121 to a CS12 but always a bit wary of “controls everything” control surfaces.
–Mike
Yes, CS12 working fine on my side. (Im in Mac)
All good here on Mac as well.
Excellent, Mac here as well so may splash out on one
no, it does not work well for me. certain plugins don’t respond, learn mode doesn’t appear to work. When I switch back to C14, problems go away. Custom mappings I’ve made are hit and miss. For instance, TrackControl by DMG doesn’t respond at all. Nor does H-EQ by Waves. And I only tested like 4 plugins in total, so clearly it’s not just those plugins but a re-writing of the .js underneath, or something that is needed. And it appears that they are working on an update… I think.
What os do you use and where did you hear about the update ? I’m considering if I should wait with the update to c15. I’m running the cs12 on windows, and only read about mac success stories so far.
Mac OS. Sonoma.
I’ve had a support ticket open for something unrelated, and I was just given a fix for it, but it turns out the fix only works in Cubase 14. 15 doesn’t play nice. The support tech said they are working on a newer version of control core, but he did not say specifically that it was to address problems in Cubase 15. I presume though it has something to do with keeping their software up to date with the latest versions of things. You may have more luck with Windows. Plus my issue in Cubase 15 might be a fluke and just need a bit of troubleshooting. All I can report is that it works great in 14 and does not work very well in 15 right now. The answer to whether to update or not, of course, is always NO. 
Wait 3 months, 6 months. That’s what I usually do. I just didn’t have the discipline this time though.
Thanks! Yes, that dicipline to not update on the first day . . .
What was your problem?
Ah, I see it now! I have to try this out sometime. Just to double-check. Even though I already have my plugins mapped, I’ll double-check it.
1 Like
I’d be real interested if you are experiencing the same weirdness as I am in Cubase 15. If so, I could then confirm it with Nektar support. They have apparently been beta testing CS12 with C15 for a while so I wonder if they are expecting people to have problems or not.
If you have a minute, if you wouldn’t mind reporting back:
- What Mac OS are you running?
- Do you experience any oddness with any of your custom maps?
- How about with any of the default maps that just come loaded with controlcore?
- How about when a plugin has no default map and just loads a generic ad hoc list of parameters?
- Lastly, any problems using the learn mode to program parameters?
Thanks!
Hola, I just did a couple of tests; that’s all I had time for.
I’ll try to answer your points:
-
Sonoma 14.8.1
-
My custom maps; I haven’t noticed any anomalies.
-
I tried mapping UltraShaper (C.15), and everything went as expected.
Note: I also tried remapping one of my plugins, and it went well. (I should clarify that when I do this, I prefer the CLEAR ALL option and mapping as I like.)
-
I’m not sure what you mean exactly by this point. Could it be if the plugin is already mapped?
-
Which method are you referring to exactly? As I said before, I usually use the CLEAR ALL option and map as I like. Sometimes it doesn’t work, and Tim Chandler (from Nektar) suggests using the other method, which is holding SHIFT (in CS12), moving the desired parameter, and turning the knob where you want to place it. That should work.
I updated to C15 and everything loaded perfectly. I have Control Core and the firmware updated.
I hope this helps a little.
I’m happy to help with any suggestions.
1 Like
Thanks Pablin, that helps a lot. Clearly it’s not a consistent bug then… which makes my life a little less easy. But glad to know you’re not having issues and it’s fixable.
#4 is just when Nektar hasn’t even created a map for a plugin, like some uncommon plugin, and what it does instead is just show a mapped list of parameters that isn’t all that organized.
#5 is just basically any mode for learning parameters.
I’m having issues with my device communicating with the software, so the learn mode doesn’t work, regardless. But you aren’t experiencing the same things. I’m on Mac OS Sonoma 14.8.2.
Who knows? Maybe I need to uninstall and reinstall. I’ll keep trying things. Thanks so much for your feedback. I’ll relay it to Nektar support.
1 Like
Ah, I see. I don’t think I’ve encountered anything like this since I started using the plugin. It’s also true that I’ve been mapping my favorites from the beginning and I’ve noticed that sometimes, after clearing the default mappings, the plugin could only map one parameter. It was fixed by closing and reopening the project. Back then I wasn’t using “quick mapping”; I’ll try to remember now. Reinstalling the Nectar system, including Control Core, helped me resolve the issue. And make a copy of your maps, just in case.
1 Like
There’s no clear or consistant issues reported regarding CS12 and v15.0.5. Do you have an older Nektar product installed (or have had in the past), or any other controller that is using the older integration bundles instead of MIDI remote?
1 Like
Hi Tim, I’m booting up in Apple Silicon mode with my CS12 connected and an LX25 mk3. I’ve also got a couple of old Steinberg CMC-PD controllers that don’t work correctly anymore but they do pass MIDI events, so I use them as drum pads, but I also have set them up as MIDI remotes with a few functions. They do show up as generic remote devices when I boot into Rosetta mode. (not sure if they also show up as MIDI remotes in Rosetta mode, hmm…) I was working in Rosetta mode for such a long time, I didn’t even use the Midi Remote stuff until recently when I purchased the LX25 and CS12. Anyway, the problem is definitely present in C15 but not in C14, both running in Apple Silicon mode…. But to be more clear, I will have to test things again a bit more… I will report back.
2 Likes
Thanks for your support, means a lot. Really!
1 Like
Well, I love these devices!