Cubase 9 coming in December according to Guitar Center

[Robert Randolph]

What is the normal X.5 to X.0 upgrade cost?

[sfd]

Two questions:

1. Will one still be forced to use a certain Windows theme to use C9 ( as the case is with C8 and 8.5 ) ?

2. I've Cubase Pro 8.5. Not yet registered. If I register now. will I've some, so called, "Grace" time and be able to have C9 for free?

[chk071]

1. Will one still be forced to use a certain Windows theme to use C9 ( as the case is with C8 and 8.5 ) ?

Ugh. AFAIK, you need to use a theme which makes use of Windows Aero, on Windows 7 (for a good reason actually, if you take a look at the why that is), but, apart from that, i don't see a limitation on a certain Windows theme, surely not on Windows 8 and Windows 10...

[Googly Smythe]

1) Probably, on Win 7, not Win 10 (no Aero scheme), not sure about Win 8.x.
2) This has been done to death, here and in other threads. Try page 5 of this thread. Also, there is a hell of a difference between "registering" and "activating".

[sfd]

1) Probably, on Win 7, not Win 10 (no Aero scheme), not sure about Win 8.x.
2) This has been done to death, here and in other threads. Try page 5 of this thread. Also, there is a hell of a difference between "registering" and "activating".

Well, I'll see. I'm using a high contrast theme on Win 10

I've activated my license. But not registered. So I guess there'll be no Grace time for me...

[seamoss]

The one thing that is oddly the STRANGEST(ly) annoying aspect is the VST handling. The scanning takes SOOOOO long. And God forbid that daylight savings time hits and you have some inspiration. This past Monday it took over 45 minutes, with a crash or two and a computer restart to get Cubase to bootup. Granted I have TONS of plugins, but I truly use them all. There is nothing that goes unused during the course of a year. And I also have fantastic computer specs so I REALLY hope something gives on this.

a big +10 on this one

I think, as a poster earlier mentioned, it really needs to load faster in general too. This has always been something that is annoying with Cubase.

I think if the plugin scan could be disabled, this wouldn't be an issue.

[sin night]

What is the normal X.5 to X.0 upgrade cost?

Looking at my past invoices, X.0 to X.5 is 49€ while X.5 to [X+1].0 is 99€. I'm talking about Pro, the smaller versions are cheaper usually if I remember correctly.
I think that skipping a minor release (going from X.0 to [x+1].0 or from X.5 to [X+1].5) gives you a price of 149€, but I'm not sure because I bought each minor release starting from 7.0.

I don't know about US prices, but I think the same policy as EU prices applies.

I don't know how much the next version will cost, but I'd expect it to be about the previous versions; in the past few years Steinberg has been quite regular about upgrade time and prices, so I think they won't change.

Lately, for me it's almost a given that each December I have to pay Steinberg, one year 99€ and the next one 49€. At least I can plan for that, it's not an upgrade out coming of the blue.

[edit: swapped prices between .0 and .5 upgrade ]

[Robert Randolph]

What is the normal X.5 to X.0 upgrade cost?

Looking at my past invoices, X.0 to X.5 is 49€ while X.5 to [X+1].0 is 99€. I'm talking about Pro, the smaller versions are cheaper usually if I remember correctly.
I think that skipping a minor release (going from X.0 to [x+1].0 or from X.5 to [X+1].5) gives you a price of 149€, but I'm not sure because I bought each minor release starting from 7.0.

I don't know about US prices, but I think the same policy as EU prices applies.

I don't know how much the next version will cost, but I'd expect it to be about the previous versions; in the past few years Steinberg has been quite regular about upgrade time and prices, so I think they won't change.

Lately, for me it's almost a given that each December I have to pay Steinberg, one year 99€ and the next one 49€. At least I can plan for that, it's not an upgrade out coming of the blue.

[edit: swapped prices between .0 and .5 upgrade ]

Thank you!

[Googly Smythe]

1) Probably, on Win 7, not Win 10 (no Aero scheme), not sure about Win 8.x.
2) This has been done to death, here and in other threads. Try page 5 of this thread. Also, there is a hell of a difference between "registering" and "activating".

Well, I'll see. I'm using a high contrast theme on Win 10

I've activated my license. But not registered. So I guess there'll be no Grace time for me...

My bet is that you'll be ok. Previous experience has shown that the updates come out in the 1st week of December-ish, and the grace period starts around the middle of October.
Fingers crossed!

[Terrafractyl]

The one thing that is oddly the STRANGEST(ly) annoying aspect is the VST handling. The scanning takes SOOOOO long. And God forbid that daylight savings time hits and you have some inspiration. This past Monday it took over 45 minutes, with a crash or two and a computer restart to get Cubase to bootup. Granted I have TONS of plugins, but I truly use them all. There is nothing that goes unused during the course of a year. And I also have fantastic computer specs so I REALLY hope something gives on this.

a big +10 on this one

I think, as a poster earlier mentioned, it really needs to load faster in general too. This has always been something that is annoying with Cubase.

I think if the plugin scan could be disabled, this wouldn't be an issue.

+100000!

I can't believe how slow it is these days, esp when you have plugins from a few companies that like to make you install every single plug like UAD and Melda, well yeah, after a change to the plugin folder like installing a new plug it can take 20 minutes or so sometimes.... its CRAZY!!!

[JonSolo]

Doing a test according to loading times (not during daylight savings) from fastest to slowest (time based on opening of DAW twice, second time only counted to make sure they were all in cache) from clicking the icon on my desktop to first option available:

FL Studio 12.4 - 3 seconds, 3 seconds (3 track project 4 bars long - 6 seconds)
Maschine 2.5 - 20 seconds, 10 seconds (3 track project 4 bars long - 6 seconds)
Ableton Live 9.7 - 22 seconds, 11 seconds (3 track project 4 bars long - 9 seconds)
Cubase 8.5.30 - 94 seconds, 15 seconds (3 track project 4 bars long - 32 seconds)

On reboot the first times all stand as do the second times. So the initial loading of Cubase is what is really time consuming, as well as opening projects. The 3 track project was loading Synthmaster VST in each slot.

Another thing I forgot to mention here- Shutting down Cubase before loading a project causes a crash. I am one of these guys who, although my system is stripped down for studio use (no internet, bluetooth, or non audio related periphials) it is still a very stock Windows 10. I purposely make only made adjustments directly recommended by the dev, which means hardly any for Windows 10. Of interest this crash does not appear in the CrashDumps folder. This has been reported to Steinberg since 8.5 was released and each patch came out. I did fresh installs for each patch to be certain.

[EnGee]

The crashes I'm experiencing when exiting Cubase, doesn't seem to have a relation to Waves instruments or to iLok related software! The crash continues to happen in spite of them, Waves and iLok, being uninstalled. It seems a bug because it happens about one in three times quitting the software.

[chk071]

Just tried to set up (once again) my MIDI keyboard for "proper" use in Cubase, and, once again, hit the limitation of learning the controls to control my soft synths. I really sincerely hope they did something about the situation in Cubase 9, because, the way it is now, it's really an awful implementation. Not enough that i have to awkwardly have to learn the controls via the Generic Remote device (especially setting up the transport key is pretty much trial and error, because you have to set specific flags for them to work properly), but also, the Generic Remote Editor is only usable for specific hardware, and not with the Generic Remote... so, if you have soft synths which don't feature MIDI learn by their own, you're pretty much f***ed, and have to set up a patch in your MIDI keyboard, to match the static MIDI CC numbers of the soft synth. Or, you can use the VST quick controls. But, guess what, you can only use 8 controls at a time that way, unless you browse to the next page of controls in the VST rack!

Well, that's really tedious, and a major PITA. It's really beyond me what Steinberg thought when they implemented all that useless functionality. The Generic Remote Editor feels like a marketing event to hype the (only a handful) devices by selected manufacturers, the Generic Remote setup is already a pain, but actually setting up soft synths, which don't have MIDI learn is really the high point. About any other DAW has a better implementation, and doesn't feature ten times the same thing, which is unusable though. If i were Steinberg, i'd get rid of all that crap, and feature a setup dialog, when you set up Cubase, to set up the controls on your MIDI keyboard, or, even better, feature pre-made layouts for the most used devices (i could probably do 20 layouts in an hour, it's really not that difficult), and then feature a in-host solution for MIDI learn, if the soft synth, or effect, doesn't have MIDI learn. Here's me hoping that they do improve on that in version 9. Although i have a feeling that there won't be any change regarding that.

So, yeah, that's my rant for tonight. Maybe their actually is someone from Steinberg listening.

[igoramos]

The crashes I'm experiencing when exiting Cubase, doesn't seem to have a relation to Waves instruments or to iLok related software! The crash continues to happen in spite of them, Waves and iLok, being uninstalled. It seems a bug because it happens about one in three times quitting the software.

Having exactly the same experience. It was happening every time I tried to save in Artist and I thought upgrading would fix it. Now, it only happens 1 out of 3 times! Unfortunately, it crashes before saving for me. I googled to see if it was an issue before I upgraded but didn't find it mentioned in any of my searches... At the moment, I save my projects as templates. damned crazy.

[EnGee]

The crashes I'm experiencing when exiting Cubase, doesn't seem to have a relation to Waves instruments or to iLok related software! The crash continues to happen in spite of them, Waves and iLok, being uninstalled. It seems a bug because it happens about one in three times quitting the software.

Having exactly the same experience. It was happening every time I tried to save in Artist and I thought upgrading would fix it. Now, it only happens 1 out of 3 times! Unfortunately, it crashes before saving for me. I googled to see if it was an issue before I upgraded but didn't find it mentioned in any of my searches... At the moment, I save my projects as templates. damned crazy.

I think I found the reason (a tiny possibility!). I have disabled the Steinberg power scheme and also disabled ASIO Guard. I have tested the Save three times, and there was no problem! Try that and see! Who knows!

I will test it again later and see if that solved the crash problem.