Having had the worst upgrade experience of my long relationship with Cubase since 6.5 I am capitulating. It’s back to 11 for me. I just can’t get a single session where something funky or buggy does not occur. From hard abends to random white noise to controllers not working to licensing failures to random sound dropouts when I hit the record enable button on some VSTIs its just not ready for production. I will now chime off of the forum and stop posting bugs as this is not what I signed up for. I don’t mind paying $150.00 for an upgrade if its good (devs gotta eat too) but not for something so unbaked.
I generally upgrade early when new releases happen and I have never been bricked but this one absolutely killed me to the point where I’ll wait for a couple of updates before I fire it up again.
Good luck to those of you continuing to struggle through the bugs and willing to help Steinberg fix them. This user appreciates your efforts and will come back at a later date to see what if anything has changed.
Sitting this one out for at least a while longer as well. I’m happy enough on C11 Pro, disappointed I can’t upgrade to C12 with confidence quite yet, but that’s OK.
Yeah I’ve moved back to 11 Pro as well for time being- leaving 12 set up for further testing as and when it gets patched up.
I’m just watching until the mess is cleared up before jumping from 11 onto 12. There are a few features I would like but I can wait.
Sorry to hear that you guys have such problems. Luckily I didn’t, some very minor niggles, but no big issues, and with the improved performance in some projects, this update has been quite good to me.
But it sucks if you are on the receiving end of the big bugs. I think I had that with C4 or C4.5 which was a major crashfest in the beginning.
Im back to C11 Pro too. Those bugs and issues creeps me out in C12 Pro even with 12.0.20 update… To be honest I am quite disappointed with C12 so far.
I think c pro 12 isn,t good as i need. I,l stay on c pro 11 .
A bit prepubescent at times, but overall a well behaved child
I just thought I should add, as a user who had lots of issues with both Cubase 10.5 and 11, I’ve found 12 to be far more stable in comparison.
I just say due to wondering why each release is fine with a certain sector of people, but a nightmare for others… Strange.
We use different DAWs and third party plugins and hardware interfaces in our studio.
No developer is immune to creating problems for a sizable portion of their users when computer operating systems, DAW updates, plugins and/or interface drivers are released it seems. Cubase is far from alone.
Unfortunately, the combined complexity all the various parts of digital audio recording systems have become so great that it’s virtually impossible for the developers of any one of the pieces to prevent bugs of various types from being included in new releases. Then, it’s a crap shoot as to who is going to be affected by the bugs and who isn’t. Each user has a unique combination of parts than everyone else, especially PC users, and that causes this problem.
I don’t have any idea how to fix this conundrum. I think we will all be in a state of being “beta testers” from now on until someone finds a way to make everything compatible with everything and limit choices of components.
I understand that perfectly. This time around I’ve been one of the more fortunate ones, the reverse of what happened with the C11.
However, not all DAWs show such extensive instability for so many people. Part of the problem will be the age of Cubase compared to other Draws, as new features do seem to also introduce new bugs, and a number of those bugs are basic types that should’ve been detected by internal beta testing. For example the plugin window issue that has suddenly appeared.
But if Steinberg since their scrapping of the old eLicenser system can show a better turnaround of updates and bug-fixing, it will clearly put them on top of almost all the competition. I hope people’s current issues have a solution soon.
And just to add from my selfish perspective, C12 has restored my faith after the problems I had with 11.
Unfortunately, if you read the various forums, just about every DAW, hardware driver, computer platform, software add-on and plugin developer is releasing new versions of their products that have more bugs than normal for a sizable portion of their user base. And this trend seems to be escalating as complexity is increasing.
We have seen some of those hit-or-miss bugs here from time to time, but we try to only update any part of our studio after the proposed update has been live user beta-tested by brave pioneers! lol
We would be overjoyed if the feature sets of every piece of our audio studio hardware, software and plugins were to remain static for a solid year and have every manufacturer devote that year to fixing incompatibility and bugs. This bug fix might actually be possible if every other piece of studio gear and software was not changing at the same time.
garethk what are you using for a computer and what audio interface are you using?
The studio equipment and major DAWs we use here are as follows:
Luna 1.2.7, Logic Pro 10.7.4, Cubase Pro 11.0.41, Studio One 5.5.2, Pro Tools Studio, UAD-2 software 10.0, PreSonus Quantum 2, UA Apollo 8, UA Apollo Twin Mk 2 (2), UAD-2 Thunderbolt Satellite Quad (2), Studio A: Apple iMac 2020, i7 8-core 3.8 GHz, 64 GB RAM, 1 TB SSD, RP5700XT GPU, 10 Gb/s Ethernet, MacOS Monterey 12.3.1. Studio B: Apple iMac 2015, i7 4-core 4 GHz, 64 GB RAM, 1 TB SSD, RP395X GPU, 1 Gb/s Ethernet, MacOS Monterey 12.3.1.
It’s always to see what studio equipment and software another studio uses, especially when they are having good luck with recent upgrades.
I guess Mac users will have less problems as macs are all similar in their hardware specs. Windows of course is a different story with a myriad of different processors, video hardware, etc…
I’m using 12 on a Huawei laptop with core i7 ang 16gb ram… I do have the occasional unexplainable event but on the whole I’m most content so far. Cubase 11 was good for a while then all sorts of weirdness occurred with the control room and my steinberg interface this was the same with 12 but I bought a Focusrite and all is now stable. Having a set up that is unreliable and unpredictable is worse than having an incontinent cat on your duvet and my sympathies lie with people who are in this position either with Cubase or for that matter with a broken cat…
The thing is you don’t have problems on a or if you buy one design and tested for audio and it still won’t cost as much as a Mac. I’ve seen lots of Mac problems lately especially with the new m1, plus native mode isn’t vst2 compatible. Lots of driver problems as well as I have seen on the RME forum.
Streaming multichannel audio with all the other bells and whistles is not an easy task so specialist equipment is required for good results. A Mac is specialised so make sure you get a specialised pc if going that route.
I will be moving to C12 after the first big bug fix update as I have started doing after C10. Why be an early adopter and go through the headache. Yes I know you can use both versions but I prefer to just wait.
We have used both custom built PCs and Macs at various times over the past 25 years. Our experience is that the cost of equally capable custom built audio centric PCs and Macs are essentially the same. However, over time, the Macs have always remained more stable as the units became older…the Macs have fewer component/new OS incompatibility issues as time goes on. There was a period when the Macs moved from Power PC to Intel processors where there were challenges for a short time…the same challenges are being experienced with the change from Intel processors to M1 processors. This change is going well overall and I feel confident that any issues will be short-lived as they were during the PowerPC to Intel transition.