Agreed
Oh yeah! @Tim_Chandler
Great controller price was great.. I wish we had a place we’re we can share preset mappings.. still learning cs12
I’ve posted this in the Cubase category, but thought I would try this thread, as well, as it is specifically dealing with C14 and Nektar CS12.
I’m pulling my hair out troubleshooting in circles, and I desperately need the forum’s wisdom and expertise.
When I try to use the Panorama CS12 in Cubase 14 Pro, it works fine until I click on any track using the Synthogy Ivory II Grand Pianos VSTi. At which point, I receive an error (see screenshot below) stating that Cubase has become unstable, and the CS12 actually reboots itself.
Ivory-II-Grand-Piano-Panorama-CS12-Cubase-Crash-0326261920×1080 356 KB
The Ivory Piano II VSTi works fine in Cubase in every other way. However, when I add the CS12 into the equation and either try to load an Ivory Piano instrument or click on a track that already has an Ivory Piano instrument assigned, I receive the error every time.
What I’ve already done:
-
Updated the Ivory Piano II VSTi to most recent version
-
Uninstalled older version and reinstalled latest version of CS12 Controller
-
Verified I have latest Cubase 14
-
Verified that CS12 is directly connected to USB port of computer with no USB hub
-
Tested that all the other VSTis I use do not cause any problems with the CS12
-
Checked computer with sfc and dism commands (Nothing found)
-
Analyzed the Cubase .dmp files, but I don’t really understand the information or how to fix it (see text below)
-
Searched Steinberg support forum, Synthogy & Nektar sites and online for this issue, or any know resolution, without success
My system specs:
-
Windows 11 Home 64-Bit (Build 26100.6725)
-
64 GB RAM
-
Steinberg UR44 Audio Interface
-
Cubase 14 Pro (14.0.41)
-
Nektar Panorama CS12 (Control Core 1.1.67/Firmware 01.02.02)
-
Synthogy Ivory II Grand Pianos (2.5.2.21)
.dmp file analysis:
STACK_COMMAND: ~0s; .ecxr ; kb
IP_IN_PAGED_CODE:
VSTPlugManager!InitDll+56653
00000000`27b8a4c0 0fbe02 movsx eax,byte ptr [rdx]
SYMBOL_NAME: VSTPlugManager+5a4c0
MODULE_NAME: VSTPlugManager
IMAGE_NAME: VSTPlugManager.dll
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_VSTPlugManager.dll!Unknown
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 3.1.80.32
FAILURE_ID_HASH: {f29c49ad-ebcb-4479-c327-8f5ea1bdd32f}
Followup: MachineOwner
Corresponding Windows Application Error:
Faulting application name: Cubase14.exe, version: 14.0.41.374, time stamp: 0x6928c2a0
Faulting module name: VSTPlugManager.dll, version: 3.1.80.32, time stamp: 0x5f50d5b9
Exception code: 0xc0000005
Fault offset: 0x000000000005a4c0
Faulting process id: 0xDEC
Faulting application start time: 0x1DCBD61E822F318
Faulting application path: C:\Program Files\Steinberg\Cubase 14\Cubase14.exe
Faulting module path: C:\Program Files\Steinberg\Cubase 14\Components\VSTPlugManager.dll
Report Id: 7ebaeca3-864d-4570-8e96-3b8aa283afdd
Faulting package full name:
Faulting package-relative application ID:
Full .dmp file:
Cubase 14.0.41 64bit2026.3.26 16.57.23.138.dmp (1.2 MB)
Ivory Piano II is my primary instrument, so it is crucial that I keep it, but I really want to improve my workflow with the CS12.
What is the .dmp file telling me, and what do I do now? How do I get these three working together? Any help greatly appreciated!
Just bring Synthogy together with Nektar. They should solve the problem (written with a slight touch of sarcasm, as exactly this can be quite challenging with companies, often resulting in “ping-pong-games” played in the yard of the person having the problem 
).
With this very specific combination, I cannot imagine, that Steinberg’s VST PlugIn Manager is the problem.
Sounds like the VST and/or MIDI Remote standards might not be perfectly implemented in every detail somewhere.
Thanks for your reply! I have contacted Nektar, Steinberg and Synthogy, and am awaiting responses. From comments mentioned on the forum, I wasn’t feeling too optimistic about getting much help from them, but hopefully, one of them will step up and help. 
Amen to the sarcasm! That is exactly my fear…an ongoing ping-pong match, and I’m the ball! 
… which unfortunately is quite normal in such scenarios (and I don’t blame any company for that).
Still, some companies stand out by walking the extra mile, and those will earn the trust of (future) customers.
So far, I have a good impression of Nektar.
Your task - as “the ball” - is to explain to both companies (and make them listen), WHY they need to collaborate and solve the problem together.
I am sure that ONCE they can confirm the bug, they are happy you made them read/listen.
Excellent advice…thank you!
Unfortunately, I can’t contribute anything constructive. However, I still wanted to comment.
You made me 
!
Anyone tried the latest update that was released yesterday? I only tried it quickly but I think instrument mapping was working, sadly i’ve not got time to try it fully but interested to see if anyone else has?!
I downloaded ControlCore 1.2.1 last week and I’m very happy that VST-Instrument support is now working. Many VSTs are already pre-mapped, like Arturia Pigments. For new VSTs, the menu structure can be created in Nektarine and assigned directly to CS12 in LEARN mode.
The last setting of the TEMPO control is also saved.
The extended button functionality will be added at a later date, according to Nektar Support.
Many thanks to Nektar for this great addition!
Internal instruments such as Retrologue and HALion are mapped too, which is brilliant as I love Retrologue as it’s such a great lightweight synth which lends itself well to being mapped in a logical way.
For me, these recent updates has transformed the CS12 from a great controller to have, to THE controller to have. The documentation and nektarine mapping is so much better too, it really feels as though everything has come together so well.
With the new update I can’t reMap the plugins using the quick way (shift+moving the parameter+move the knob)
I need to try the conventional way too
Is there anywhere I can read about all the new features in the update? How exactly does it work so I can now use the VSTi without Nectarine?
Addendum: The VSTi is now in slot 1, and all insert plugins move it one slot away. So insert 1 is now in the second slot. This is bad for clarity.
Why not unpack the VSTi from user 1 or user 2 or into insert slot 16?
If it’s pre-mapped or already mapped in Nektarine you just load the instrument, if you’ve not mapped already, you do so in Nektarine and then save it. Then when you next load the instrument it will be mapped directly from Cubase.
Sometimes you need to restart their service to force the change, is the only caveat. But there’s a control panel which makes this really simple to do.
Personally, I find this more logical as I see it as a plugin chain as a whole VSTi → Delay etc., I use different DAWs so the plugin chain including the instrument does seem to follow a general convention - remember this is a universal controller so it acting the same across software is a big selling point for people also.
If you’re only using Cubase, or DAWs where the instrument isn’t part of the plugin chain, I can see why it could be confusing. But then Cubase doesn’t always follow the norms as the integrated channel strip components are separate to the plugin chain too.
Of course, you have the colour coding which represents plugin type on each slot button, and you can see on the screen the plugin order so I wouldn’t say it’s so bad for clarity..
However, if you had the same Channel Strip plugin across all your tracks and wanted them in slot 1, I can see how it would add to the confusion. Personally, I do like how it’s setup and find it quite a logical approach.
Assigning parameters no longer works. Neither in learn mode nor with shift. How do I do it now?
Am I the only one whose two functions don’t work?
what exactly do you mean by: The extended button functionality will be added at a later date, according to Nektar Support.
Statement from Nektar Support
We have an active feature request for allowing momentary switch behavior, as well as a number of other attributes for buttons with more than one state and parameter ranges. I don’t know when those features will be added.