I have got this fantastic new Controlle from Nektar (the CS12), and when it works it’s a complete game changer. However there is a section (3rd party plugin control) that only works when I create a completely new project, when I load another project it stops working. Likewise if I use my KWM switch to switch the keyboard and mouse (and 2 WHQD screens) over to my streaming PC and then back.
THe DAW computer doesn’t go to sleep during this operation, the CS12 has a dedicated USB port (no it doesn’t go over the KVM). I have been troubleshooting this problem with Nektar support for 20 days now (over 50 emails) and I was told that Cubase 4.0.20 might address the problem. Apparently the MIDI Remote protocol somehow loses the connection with the Nektar - all the other parts of the controlls (transport controls, motorized faer, C hannel strip and sends) all work (also QC would work as well) but the deep plugin integration is probably 75% of the value of the unit.
So has anybody else experienced this and could a steinberg staff member get me an early version of Cubase 14.0.20 for testing? I have tested with the latest versions of Cubase14 Pro and Cubase13 Pro (I have 2 Pro licenses). unfortunately I haven’t seen any error messages in the MIDI Remote Script console, and am wondering whether there is a “Verbose” mode here that could give more insights on the communication between Cubase and the controller.
So far I tried
disconnecting mouse + keyboard from the KVM (I cannot remove the screens as well) and connecting a separate keyboard
removing the previous nektar drivers (panorama P1)
removing my kensington trackball and drivers
getting a separate power supply lead for the CS12
different combinations of tracks etc.
once the CS12 is in a faulty state, I have to restart window and the hardware to make it communicate with the plugins again. Yet I do not believer that it’s a hardware issue because the right hand side controls work in all other modes, and they also work when I create a fresh project. I have put in about mayb 16hours of testing and research so far. WOuld love to see this wokr to get away from mouse / screen centric mixing!
Steinberg, please send me a preview version of 14.0.20! It’s almost 3 weeks!
Hi, for me the same. some deconnection with USB hub !
i’m on Nuendo 13.0.51 with Sonoma 14.7.2
edit: i tried too to connect directly on the mac. and still issue
No, directly into USB, I do not have any USB hubs - I tried different inputs as well. I think there is just some extra HID traffic (communications) that might be caused by the KVM somehow interfering with the MIDI Remote API.
everything works except for the plugin control and DATA/MENU button when this happens. but if I use Quick Controls or Channel control, the right hand side works. It might be interesting to look into the following file:
interesting that it happens on Mac, too. The Nektar support said communcation issues (with the right hand side) only happened on Windows. Or maybe when it is KVM related. Also check the midi remote error console if you can!
I also have the problem under Windows 11 that plugins cannot be controlled in some projects.
Nektar support says that this should be fixed with the next Cubase update.
My problem, same on MAC. Uninstalled all Nektar stuff and scripts deleted.
Re-installed three times and worked on last attempt.
However, left everything running, went back in an hour and its playing up again. VST instrument wont open. Plugin button not changing to white Etc.
Ive had this 2 weeks now and not recorded a single note for trying to get it to work.
Ok good news: Nektar support sent me a new script file, v1.1.11 which makes the controller alot more stable, and also adds a working “reload script” for Cubase 14:
They are still testing this version, but they will officially release a new script by the first week of march.
Installation: Replace the ‘Nektar’ folder in …Documents\Steinberg\Cubase\MIDI RemoteDriver Scripts\Local and …Documents\Steinberg\Nuendo\MIDI RemoteDriver Scripts\Local (no need to install the script in the Nuendo directory if you only have Cubase.
I am using it with a “cheap” hub that I had at home, with the cable provided by nektar and it has not given me the slightest problem. The small errors are from Cubase itself, I understand. (in the few times I’ve used kos in Logic, it has never failed)
yes, I believe it’s a problem with the Steinberg Remote Midi API maybe it is susceptible agains HID messages from things like mouse drivers etc, which can be triggered by KVM switching. I think the less USB devices you have connected to your PC, the less likely you will encounter this error. Let’s get rid of the dongles next!
I can replace the keyboard and mouse, but I cannot add another 2 WHQ displays to service 2 PCs, so it it’s the communication with those confusing Cubase, then I hope that their maintenance release 14.0.20 will finally address this and make the system more stable.
Dont expect any big changes now. And I guess if your KVM causes problem for you it is related to the USB level. You get a interference on the bus that causes enumeration. Try to use a other usb controller for your midi or kvm. (I know that can be hard on laptops).
And I guess if your KVM causes problem for you it is related to the USB level. You get a interference on the bus that causes enumeration. Try to use a other usb controller for your midi or kvm. (I know that can be hard on laptops).
Alright, but I am more worried about the screens - when I tested with the old script I eliminated (KVM) keyboard + mouse on the DAW - just connected a dedicated keyboard and still had the trackball, but it didn’t help. The two 2.5k screens are connected to the KVM via HDMI and DP and of course dedicated graphics cards (GTX 1650 super on the DAW and Geforce GTX1660 on the streaming PC), but I hear they can also do HID stuff according to the nektar support person.
Do you know whether the USB enumeration is something that I can see in the windows event log?
I would suggest to everyone with Nektar problems, do it like me, open a support request with Steinberg and tell them about it. I asked them for a prerelease to test, but their reply speed is glacial - also asked Nektar if they could share their 14.0.20 with me.
By the time I will get a reply from Steinberg, the new version is probably out anyway. Which is a pity because we could have helped with stability testing.
My CS12 works perfectly (versions see my forum profile). I made sure I have no USB hub/splitter in between and that I don’t do any KVM stuff (which would be: other HIDs not directly connected to motherboard USB).
Sorry you’ve not had the best experience with the CS12. It sounds like there may be some connection issues from what you describe - is the lightening bolt symbol top right in the CS12 display green?
Nektar Support will be able to diagnose any power or connection issues and help you out.
Just to say SHIFT+SELECT to select control Room mode will not trigger if SELECT is active. Instead, first de-activate SELECT mode.