Hi, I installed Cubase 14 and went through the installation etc… Same issues as before! I also tried a new script 1.1.11 again no difference.
Easy to recreate the issue though just open a new empty project install a few audio tracks with no inserts totally bare. Press either the channel button or sends button and simply switch between the audio tracks 5-20 times (slow or fast) with the MAC mouse or via the M1/M2 navigation buttons. You know when it’s broke because the screen on the CS12 freezes but the Cubase project continues to work! Even the transport controls will carry on working that is right until the CS12 reboots itself.
The system log for ControlCore says the communications has timed out!
The retailer (Sounds Easy Australia) have tested the unit with a MAC and LOGIC (I use Windows 11 and Cubase) and found no issue. I have put it to them that the issue is with firmware / compatibility with the systems I am using and not the ones they tested.
Interestingly the guy at Sounds Easy who seemed to know his stuff was adamant the green lightning bolt was lit for him (MAC USB) whereas NOTHING I did could get it lit (multiple PCs, different USB hubs, powered USB hubs etc).
Obviously his testing was not deep enough to prove or disprove the other issues I have had (randomly frantic fader, control room not working, CS12 not recognising Cubase projects are open). So the case is still open with the retailer to see if I get a refund or not.
Anyway I have a pair of sleek black shoulders here unopened from SYNTHS AND WOOD for the CS12. If anyone is interested in buying them (Australia) hit me up.
I used a standard apple USB wall charger 5v 1A but needed make a cable with 2.5mm plug to give +5V on the centre pin. I have subsequently purchased a thunderbolt cable 40GB 100W (DGhumen Thunderbolt 4 cable) about £10 off Amazon which provided enough power to get the green led on.
No difference to the CS12 fault though!
Nektar support have confirmed it should be ok to run in low power mode. Seems there is something system specific going wrong with the remote manager script!
So… Here is what happened next. I returned to the retailer (Sounds Easy in Australia) and none of their testing could find fault. The tester also provided video of the lightning icon lit up and various functions working. It was sent back to me with refund denied but offer of providing warranty to next owner if I sold it on. Logic being that it was something in my system causing the issue.
When it returned, I plugged the CS12 into my Elektron Overhub (USB powered hub) and the green lightning bolt lit up! It had never done that before.
So then I reorganised the cables to where they should be and the lightning bolt wouldn’t light. I fiddled around and moved the Overhub and the lightning icon came on, but there was a definite physical shaking sound from the hub. Short version, the Elektron Overhub innards have become unattached in some way and work SOME but not ALL the time.
So accepting that my PC was not powering the CS12 (old motherboard, possibly not enough mA per output) I had no idea that the Overhub had a mechanical fault doing my prior testing. It had never been an issue.
So I went to a local electronics shop and bought another powered USB hub with a 4A power supply.
And so far all is good… So it seems my issues were LIKELY to be related to the CS12 not being in high power mode. It still doesnt recognise Cubase 14 sessions all the time, but when it does, it seems to work - Control Room Fader Mode works consistently and that hardly ever worked before.
So if you are having issues with the CS12 and you are NOT getting the lightning icon lit green, diagnose that first.
The v1.1.11 release addresses the main issue reported on this thread of plugin buttons not working with some projects after re-initializing.
The underlying API issue that caused this is also fixed in Cubase v14.0.20. However, due to the severity of this issue (API sub pages not working) and the importance of the plugin buttons to the CS12 workflow, we wanted to revisit this area of the code and work around the user of sub pages entirely.
What are your plans after C14.0.20 is released?
a) keep the 1.1.11 workaround, because you consider it the actually better approach?
b) remove the workaround and tell that CS12 is only compatible with C14 from version 14.0.20 on?
c) keep both implementations and have them applied within code execution based on the C14 minor version value?
Thanks mate. I felt a bit silly in the end. But complex problems are complex routes to solve - still - I did get a bit annoyed and should not have. I am testing again today and NEKTAR have been bang up and responding to my ticket and I have sent them my template file to analyse and they are fully engaged.
I have now updated to 1.1.11 and it is fairly easy to get the controller to crash within 60 seconds. I see some improvement regarding QC but it is still not even close to be useful due to firmware stability.
Can you set up a support case please? We haven’t many reports of this but there are a few similar reports and we are having a tough time reproducing the problem. So the more data support can gather the better.
I installed the CS12 two weeks ago and updated to the previous firmware, not the very last one that was pointed out by plectrumboy some posts above and haven’t even loaded the script posted in post 9 above. I still don’t have tested it intensively with Cubase 14, but until now what I tested works flawlessly. I even don’t notice very long delays when changing plugins, like I have watched in some videos, and my computer is a very old i7, although very good 13 years ago. Plug-in control seems to work very well, although I think some day I will reorder some things. I will continue testing, following all features side by side with the manual.
Only thing I noticed so far: if I switch to control master volume with the fader, it controls the Control Room volume, if CR is activated. No problem with that, but if I press shift-touch fader, the volume doesn’t go to 0 dB. Shift-touch fader to go to 0 dB works well with any other track though. Only in CR mode it doesn’t.
