Just like every release of EVERY piece of software, there’s a handful of folks having issues with it, and a great majority of its owners getting along just fine… Don’t for one minute think the minority of forum users are the be all end all demographic
I’ve been using Cubase for years and have tried it on several different computers, recently put together an extra PC just to run Cubase and I still have the same bugs and problems (eg Cubase always crashes, warp editing doesn’t work correct, etc). I can agree with some here that I don’t have the time to constantly search for solutions. I just accept the bugs and live with them. But with each update I am disappointed anew.
That’s rather odd. I think its been there since DP 1.0 but I’m not exactly positive. They’re up to 2.0 now but almost nobody uses it yet. Each rev adds a little more to it. 1.2 was the first to support a full 4K@60Hz and MST (which Apple still doesn’t implement ), 1.4 gives you all the super high refresh rates gamers want and goes all the way up to ridiculous 8k resolution, etc… I think audio has been there day 1 just like HDMI though. On my Macs at home and my Surface I use at work, the DP audio device shows up as the name of my monitor. At home its a ‘VP3268a-4K’ in the list, at work in Windows there’s two ‘VP2768a’ outputs available…
I’m running cubase pro 12, Midi through is no longer operational thanks to this 12.0.70 ‘upgrade’, every time I go back to Edit/Preferences ‘Midi Thru Active’ is non-activated, event though I previously saved it’s setting in ‘Preference Presets’ (a STUPID idea) and again recalled it.
(mostly) functioning CB without crashes is a joy to work with, and I am reluctant to jump ship after investing 15 years of my life getting the best out of the software, but I will be thinking seriously before investing in 13 considering the countless issues we have suffered with 12.
Just adding my take on this…
Running Win11, Cubase Pro 12.0.70, i8700 cpu, asus 370-a mobo, nvme drives, 32gb ram. Asio-guard, cubase power scheme all checked. Using multi-processing. Running 96,000 x 64 bit. Latency 1024 samples. No real problems until I started using Synthmaster2. The audio meter flies randomly off the scale and Cubase becomes unusable because of dropouts. Changing a voice leads to a spike in audio performance, many of these going into the red. Changing sample rates, latency and so on have no real effect. It happens with the VST2 and 3 versions of this synth.
As suggested in another thread about all this I have tried disabling unused inputs. The only thing that seems to help is to turn off multi-processing. My mobo doesn’t seem to allow me to turn off hyper-threading. This seems to be specific to Synthmaster 2 and I’ll take it up with KVR.