yeah - I think the update is fine. Variaudio3 is great.
Is anyone else getting more crashes unloading projects? Cubase basically gets stuck unloading forcing a reboot (can’t kill task), or it crashes and names seemingly random plugins in the crash log (kontakt, elephant - totally different plugins and footprints). I’ve gone from hardly ever having to re-boot to re-booting 2-3 times a day. Not a killer, just a pain. Also I’ve noticed Arturia synths cause a memory leak. If I leave a project with their plugs open, I come back and the cubase task has gobbled up all my memory (16gb). Anyone else get this? I’ve googled and not seen it raised elsewhere. Again, not a killer. Just a pain!
What would be really nice is for the autosave to also save current settings. So export settings, paths, recent projects etc. When I crash out and come back, I often get caught out with export settings reverting to previous lives and paths being reset to previous days workflow. Would be good for my workflow anyway…
I also had very few problems…apart from a specific plugin that crashes on startup it has been as stable as 9.5. i think its goint to the right direction personally
as a new customer im shocked at the incompetency of the v10 release. thkful i didnt upgrade to pro. steinberg will you issue apology & fix this asap? iif not you lose my business for life. i expect competency
“Worst update till now” is a very hotly contested title. So far my only problems with Cubase 10 are the workflow killers (right click menu and so on). In terms of performance it’s been very solid and dependable.
If you’re a newer user who came into Cubase in the last few years then yeah, you’re going to be disappointed in how Steinberg handles things and how each Cubase version is sketchy until x.5.2 comes out (two paid updates later…) But for us who’ve been with Cubase for 10 or 15 or more years, it’s just another form of nostalgia.
While there is true stuff in this topic, some of it is so much emotional venting, plus newcomers to Cubase joining the mob, especially as the thread grows longer. This is perfectly normal on the interwebs and I’m not complaining. But I do want to say that I’ve been using C10 since it came out and aside from the missing features- for me the most annoying being the missing right-click menus– my personal experience has been pretty good, I like the flatter look very much, now that I have been working with it for a while.
If I hated it, I would certainly just go back to the previous version and wait. This is a bi-annual event, and, as a few seasoned users in the thread have pointed out, the stuff will probably get fixed. But to actually call the company incompetent, and demand apologies is muckraking, and imo is the effluvium of a consumerist ethos that’s developed over the last few generations- people actually think the customer is always right, but they’re forgetting that that’s just an advertising slogan.
So far, Cubase 10 has been solid on my Macbook Pro. In fact, so good I took 9.5 off the system drive. One thing I found is the projects and templates do not port very well, in either direction. You couldn’t open a 9.5 template in 10 and you can’t open a Cubase 10 project in 9.5 and not expect trouble. Over all, Cubase 10 loads faster and I just get used to what I have to work with. I’m not jumping ship.
The way I look at it is by filtering what Steinberg puts out through the lens of political campaigning. If you see the bearded guy with the Australian accent, you’re watching a campaign ad for beta testers. He’ll use words like “exciting” and “new” and “revolutionary” which are all code words for “unstable”.
Once you start watching the Greg Ondo vids, that’s how you know you’re listening to your local representative trying his best to do something about the pot holes in your town. He’ll show you workarounds and real world application of new features that aren’t as perfectly controlled as the big reveal videos. It’s the same as back in the 90s when a new synth would come out, ads promising it replacing your entire recording studio with its 16 track sequencer, but to get a real down to earth view of what it actually did you had to go to a clinic or trade show and see the company rep actually using it.
I only installed Cubase 10 on my secondary computers that I can mess around with, my main rig will have 9.5 on it until I finish all my current jobs and have a week or two downtime to do a proper full system overhaul.
I just upgraded, added a waves soundgrid rack… was really happy it all worked; and then I went and saved the file, and closed Cubase. Imagine my surprise when I attempted to load the file again - and it crashes repeatedly. In this case it seems very much a Waves problem! Who would’a thought.
My point is that several of my issues now appear to be ‘mea culpa’d’ by other plugin vendors. Given Steinberg’s involvement in defining the plugin formats - I’m now leaning towards that they tightened up other spec compliance requirements in the switch to 64-bit only support. Hopefully there will be a slew of updates from the many plugins I’ve used in 9.x projects - and the number of crashes will diminish. Until then - alas - I’m back on Studio One and Pro Tools.
Naw, just keep logging the bugs in the Issues form, they’ll fix it, I’m sure the Stienberg developers and programmers are going for it in the lab and taking care of business. They really brought some cool things to Cubase 10 and it might take a while to congeal. We as customers are part of the Cubase family and helping them find the bugs (-; If we had to wait until Cubase was 100% stellar before they release it, we might of never get to use it. Stienberg is probably pretty happy we bought the upgrade and it gives them hope to keep building Cubase. So let’s go for it and help make Cubase the DAW that is second to none!
1.too many unnecessary changes to tried and tested workflow. nobody who professionally works with ANY software wants to re-learn something that was working perfectly before UNLESS there is a significant improvement!
2.unnecessary changes of GUI purely visual and esthetic with no actual improvement of function. it is detrimental to workflow!
(why change a tool symbol just for the heck of it? DAW’s are not a fashion statement! stop trying to please kids and geeks who gawk at “shiny NEW looks”! (Protools is steadfast!)
3.unstable when working with C9.5 projects
4.unstable with some 3rd party plugins
5.lots of bugs already present in C9.5 not fixed.
6. hitpoint detection broken!!
7. Audio Alignment not working properly.
… etc. more bugs in the forum…
8. really looking forward to ARA2 and hope they get it right!
Bottom line: C10 is not useable to me as a professional tool and i am still working with 9.5 and resent the price of this sloppy and misguided update.
that is a very optimistic viewpoint. however, the past has shown that bugs can take a very long time to be dealt with by Steinberg. and frankly, I’d rather wait for an update that does work then getting lured into a shoddy update like this one. but that is of course up to me how eager i am to jump on the bandwagon…
Instead of correcting errors and introducing functions that users have been asking for over the years, they give thin scrollbars, spoil the transport bar, spoil other functioning functions and degrade stability. Senselessness. I do not buy Cubase 10.
As a matter of fact, the first 2 weeks after installing Cubase 10 were a little special.
Projects could not be opened
Crashes all the time
Re-Opening the project was just possible after rebooting
Freezes in the bounce and/or rendering process
etc.
Then I found a Steinberg statement that Cubase 10 is compatible with Windows 10 v1809… but not with other ones. As soon as I updated Windows to v1809 everything works well. All my problems vanished, the software is pretty stable and I can not complain much. Please note that there are other users that got all the above mentioned issues by updating to Windows v1809!
The version compatibility was not so obvious and there is lots Information that could be better communicated to us users. No software is bug-free - especially not if it runs on 10000 different hardware setups - but the lack of communication could be changed easily and is what bothers me most.
The article says that v1809 is the last supported Windows release. The article says also Please make sure that you always use the latest updates available! and Please have a look at the charts below to see which Windows 10 release is compatible with your product.
I am happy for you, that CB10 works on your Windows v1803… but in the Steinberg Win10 compatibility info you’ll not find an official statement that there’s any other compatible Windows Version but v1809.
That doesn’t mean that CB10 crashes under older Win10 releases…no of course not… it indicates that there was no Steinberg test made but with v1809… and therefore v1809 is officially the one to be used.
I am sorry to tell you, that every other interpretation of that document is just guessing.
You can believe what you wish, of course. Note that the “latest update available” when it comes to Windows 10 means either 1803 or 1809- due to the fact that version 1809 is still rolling out.
If you want to confirm this info, check in with Steinberg support via the Steinberg account website.
