For some reason every project I have now is zoomed out to the max in the mix window. Pain in the buttock to zoom back out.
What seems to be happening is that so many users use such a variety of computers/components. Some work flawlessly, and some don’t. I do wish Steinberg would find a way to address this without ignoring that it is an issue.
If you had a problem with Steinberg UR series interfaces you would know what it is to be completely ignored. The issue there is though, that some mobo’s just don’t like the drivers. Who’s fault is that? Well, the manufacturer likely and the software developer but think for a moment about what it would take to test every combination of PC setup…Every component and their drivers as a variable? Not even a possibility in reality. And as far as relations with Mac, good luck there. That seems to be a brick wall at times. We don’t even have a video engine yet thanks to Apple. I digress…
That being said, my system (knock on wood) has been working mostly flawless since 8.5. I realize that is not the case for all users but take the fact that some of the issues may be on your end. Not Cubase as a program. But without help from Steinberg, I solved my UR824 driver issue by replacing my mobo. Not everyone has that ability. It would be nice if there was at the very least more communication from Steinberg as to what is being done about the issues so many have. Maybe just a ‘Hi we are looking into this’…
Yes there are bugs. But as far as performance and GUI sluggishness, dropouts, and performance… that is likely the system Cubase is running on that is the issue.
Trust that I am in no way defending Steinberg support. In fact I am not satisfied with some of the support I have received.
But I will say that Cubase 9 has so far been flawless for me since it was introduced. I have nothing to complain about and I use it daily. It is individual system performance that seems to be the cause of most issues.
Not blaming anyone, just stating my opinion.
Tempo detection still doesn’t work and crashes the project. I’m back to 8.5 which works perfectly. That’s pretty poor - a previous version that does something the new version cannot? What’s the incentive to buy? I am getting pretty close to going back to Pro Tools which annoys me as I don’t really like it but I’ve not had issues on that which really affect my projects the way i have on Cubase 9.
This whole release feels slapdash and for the sake of it.
I’ve tried all os operating systems from mountain lion forward with C9.2 and found that for my 2011 imac Mavericks offers the smoothest GUI experience. Play head still staggers but super fast and fluid otherwise.
Hi all,
I’ve had some crashes when opening various third party plugs ( Waves guitar fx mainly) and all I did was reinstall the plug ins, hey presto, crashes stop.
Apart from that, no problems here with latest version.
Jim B
I think this is the problem exactly. There are so many different computers and configurations possible that it’s hard to predict how computer A will perform as apposed to B. And when it comes to installed software there’s even more possibilities. I think if you start working with DAW software and in particular with Cubase you must be prepared to put in some (!?) hours optimizing your system and make sure you don’t have any software/plugins installed that could interfere with the performance needed to run Cubase. And literally anything from a minor program in the background to a display card/drive can have it’s negative impact.
I agree with you that Steinberg should put more effort into addressing this. Things like broken installation files like we encountered with some updates recently should not occur with software on this level. But in all fairness you can’t blame Steinberg for all issues occuring at the users end. This type of software needs more attention than others and sometimes people think they can just hook up an audio interface, install the software and that’s it.
Well, maybe in a perfect world…
Okay, I imported the exported file back into the project: it plays fine in Cubase. My project is set to 48k, 24 bit depth. However, in the Audio Engine portion of the export dialog, the bit depth is set to 32K float and I cannot change it. That could be my problem, correct? Thing is, I’ve never seen this before.
Bit rate is not your problem. Sample rate is definitely the problem. Your Windows audio is probably set 44.1
You are correct. I noticed this morning that a youtube video was playing back at a faster speed. Audio in Windows was set to 32/44.1. Fixed. Thank you for your help.
Works fine on my mac under El Capitan.
Worse GUI performance than 9.0.10 on Windows 7. Scrolling isn’t smooth and the playhead stutters a lot. No problem with the audio though.
I’ve gone back to 8.5. Too many blacklisted 32 bit plug ins on 9.
TBH I’m getting pretty fed up with Cubase. Audio drop outs are a continual PITA. Tried all different settings, buffer sizes blah blah. Totally destroys workflow. Even got to the stage where I get the audio drop out box and the mouse pointer disappears! CTRL / ALT / DEL task manager 
Been looking at Reaper. Different animal I know, but Cubase, tell me why I shouldn’t go.
I just purchased Vienna Ensemble Pro, and will never go back to loading plugins inside Cubase.
I’m considering that as my next move, if only for my sanity’s sake. I’ve used Cubase intensively for the better part of the last decade, and it’s steadily gotten worse. It’s the lesser of two evils – the alternative being to use a different DAW. And there’s no way I can bring myself to use a different DAW.
But thats my point; you shouldn’t have to do that. We pay our money (lots!) and it should work. Totally disillusioned here.
FWIW Reaper was up and running in SECONDS
For everyone jumping to Reaper, it’s been a while since I used it but I found it was always a gong show. Buggy and unstable, and lacking some necessary pro features in the film/TV scoring arena. Maybe people are having more success with it now. 
It doesn’t crash and can use all vst’s 
Using VEPro, the setup is as follows:
- Create instances of VST Instruments, assign VST Instrument outputs in VEPro
- Load VEPro (instance(s)) on the VST Rack in Cubase
- Assign VEPro Outputs in Cubase
- Use effects or processing in either application
Workflow:
- Load VEPro and allow VST Instrument instances to populate sample data
- Load Cubase projects containing MIDI and audio files
VEPro loads and unloads much more quickly than any DAW ever will and does this without any of your DAW(s) having to be active so any audio driver issues can be dealt with independently of your loaded Instruments and effects, which means your instruments are there ready for any project or DAW you wish to use.
Since there are few if any VST instances loaded in the DAW, other than VEP itself, project load and unload is quick and less prone to crashing. If you are using only MIDI it is seconds.
Why would anyone use 32 bit plugs in a 64 bit DAW? It doesn’t make sense.
Some software companies have yet to create a 64bit version believe it or not…also some are legacy plug ins that’ we’ve grown to love… the day will come tho 