It’s very good that you can adjust the clipgian with the potentiometer, but unfortunately the cs12 doesn’t remember this setting and you have to set it again and again after starting 
1 Like
Is that a bug, @Tim_Chandler ?
I prefer Tim’s answer, but could it be a known Cubase bug with the Midi remote? Or is it from Nektar?
You should test the behavior in Logic and then you would know who is at fault 
oh, don’t tell me that, hahaha but I have to check it. I’ll also see if it really helps navigate Logic more fluidly.
Hey Tim.
I already have a ticket open with support [ #113062 ] but haven’t heard anything back.
I’m getting along better with mappings but have been finding some inconsistencies [ perhaps user error ]. And still seeing the # versions of npm files I mentioned in my reports from time to time… 2 this afternoon.
[ Am battling with a ‘dropping audio engine’ issue alongside this, so it’s possible that’s having a part to play… the ‘nkscanner quit unexpectedly’ warning is still happening after every load of Nektarine… Might be good if we could take this to email? ]
Have a good NAMM!
Alan
Blockquote
Not a bug, more a limitation. We are aware of it and will add a user preference to controlCore in a future update.
For Logic I used modes to ensure the tempo control assignment sticks. For Cubase pages are reset whenever. Control surface is loaded so I couldn’t provide a similar solution.
Support is still your best bet. We are all busy with NANM prep now (small company) but they should get back to you today. I myself am not involved with Nektarine development so support is your best option anyway
The CS12 uses controlCore which is reading npm files and is essentially Nektarine ‘off track’. So yes you can create npm maps as you have been for your p6.
Instrument plugin support will then be added to controlCore in a future update.
There’s no mixer mode.
The P-series unfortunately can not support controlCore, but we are still supporting it.
Is this something, where Steinberg could accomodate with?
All the best for NAMM
890 / 5.000
Unfortunately, I noticed something else. You can still create a generic controller in Cubase. That’s the old way of integrating controllers in Cubase. The advantage here is that you can use it to open plugins that are in the control room. Unfortunately, this is not possible via MIDI remote. Shame, Steinberg. I have the Arturia Beatstep for control. I can integrate it via MIDI remote and as a generic controller at the same time. Unfortunately, that doesn’t work with the CS12. I can only integrate it either via MIDI remote OR via generic controller. Both at the same time are not possible. As soon as you have integrated the CS12 via MIDI remote, it no longer sends MIDI data to the generic control panel in Cubase. Why is that? Can this perhaps be fixed with an update? And why does the CS12 have multiple MIDI ports? Cubase shows me 4 MIDI ports.
Thanks for the reply Tim.
I’ll look out for a reply from support. All good Sir!
Hi Tim, I’ve just answered a similar post, here:
If you’re interested in the second approach, let me know.
Hi
How do I get the names of the 4 buttons under the potentiometers to be shown on the display? I have programmed plugins myself with the cs12 but the names of the buttons are not displayed
Press the data/menu button
1 Like
Thanks for all the suggestions.
Regarding generic remote, 7-bit midi and any reliance on mcu we are trying to move things forward away from these technologies with the cs12.
This feedback is great as l can take it forward and discuss with Steinberg how to solve the limitations properly using the remote midi api.
The additional ports on the cs12 are required for future expansion and other daw support, but they are dormant in Cubase and can be ignored.
Best,
Tim
3 Likes
Does this mean, CS12 does not use any of those at all with Cubase?
(that would be a great advance in modern technology; to doubting people: of course with all pros and cons any change would bring in general )
1 Like
The preferences are not stored in CS12? When switching over to another machine all preferences are lost?
Not sure if this was for my previous comment, I have to clarify that I don’t use generic remotes, just the MR API.
I agree 100% 
Correct, we rely on the midi protocol to get data to and from APIs but after that we work with as higher resolution as possible.
When it comes to parameter control, The fine button (magnifier) gives just over 10-bit resolution which we’ve found suitable for most params. The coarse adjustment (magnifier off) is more akin to 7- bit like standard midi to enable full parameter sweeps. Magnifying the motor fader ( hold magnifier when using the fader) give really fine resolution for the linked parameter.
This resolution applies to user made assignments in channel mode too - you still get 10 bit resolution and display feedback.
This is why there’s no midi mode - it takes away from the product.
We’d rather solve mapping limitations through the api.
2 Likes