Cubase 12 released

[sqigls]

ALSO, after installation Cubase would crash every time i tried to open it. Both native and Rosetta mode. The crash report was telling me that somehow Groove Agent SE 5 was responsible, even though it wasn't installed. So, i went and installed the thing and Cubase finally opened. deeeeeeeerp


macbook pro 2021, monterey 12.2.1

[Rommelaar]

Does anyone know if you still can run Cubase versions (pre 12), once you have converted your license to the new system?

[pixel85]

From what I see at Steinberg forum, I'm not sure if I want to risk an update. It looks like a disaster. Not only to get an update but to run C12 without any issues.
Remove videoengine, remove preferences, trash C11, remove plugins, make Mayan style sacrifice... and then it will eventually work.
Next tip: to use C12, don't use audio, midi and video. All other functions will work

[dellboy]

Does anyone know if you still can run Cubase versions (pre 12), once you have converted your license to the new system?

I am running Cubase 12 and Cubase 11 with no problems, so yes, previous versions still work. If I pull out the dongle, version 11 stops working, but version 12 is ok as its on the new system. But if the dongle breaks in the future and they switch off the e-licencer servers then previous versions are gone forever. The old licence is now NFR. (non upgrade-able).

[wangeroge]

Does anyone know if you still can run Cubase versions (pre 12), once you have converted your license to the new system?

Yes, you can. Cubase 11 isn't deinstalled and the license stays on the dongle.

[AdvancedFollower]

Does anyone know if you still can run Cubase versions (pre 12), once you have converted your license to the new system?

Yes, you can. Cubase 11 isn't deinstalled and the license stays on the dongle.

The update procedure initially nuked my Cubase 11 license on the dongle, and since Steinberg's servers were constantly unavailable, I wasn't able to get it back immediately. However after running the Maintenance Task multiple times (tons of error messages about servers being unreachable etc.), it managed to put the license back as a "Non-upgradable" license.

I think the procedure goes like this:
1. Check the current license
2. Nuke Cubase 11 upgradable license on dongle
3. Deposit Cubase 12 license in the new system
4. Deposit Cubase 11 non-upgradable license on dongle

Probably their servers went *poof* during Step 4 in my case.

[fese]

From what I see at Steinberg forum, I'm not sure if I want to risk an update. It looks like a disaster. Not only to get an update but to run C12 without any issues.
Remove videoengine, remove preferences, trash C11, remove plugins, make Mayan style sacrifice... and then it will eventually work.
Next tip: to use C12, don't use audio, midi and video. All other functions will work

Well, of course you only see the problem cases in the forums, all the other users that have no problems don’t write about that.
The grace period/migration process was a convoluted mess, but so far I didn’t encounter any problems in C12. And as you can, as always, install the new version in parallel, there’s really no danger in trying it. If it doesn’t work on your system, just to back to 11 for the time being.

[fese]

This is very encouraging to know. Are you using the new license management?

Of course. c12 only works with that.

[4damind]

Wow, is the update really that complicated? I would have thought it would be enough to enter the activation code somewhere in the Steinberg Download Manager and then eLicenser will automatically open or the (previous) licence there will be marked as "non-transferable" and the activation via the Steinberg account will take place at the same time.

Btw. are the servers still so overloaded at the moment?

[morelia]

Wow, is the update really that complicated? I would have thought it would be enough to enter the activation code somewhere in the Steinberg Download Manager and then eLicenser will automatically open or the (previous) licence there will be marked as "non-transferable" and the activation via the Steinberg account will take place at the same time.

Btw. are the servers still so overloaded at the moment?

I'd never done the grace period thing before but I wouldn't say it was overly difficult. Just that every step of the process failed to work at all. Until, without any apparent reason, I could install it, and it was registered.

[noiseboyuk]

Well, of course you only see the problem cases in the forums, all the other users that have no problems don’t write about that.
The grace period/migration process was a convoluted mess, but so far I didn’t encounter any problems in C12. And as you can, as always, install the new version in parallel, there’s really no danger in trying it. If it doesn’t work on your system, just to back to 11 for the time being.

Yup. The installation wasn't exactly a breeze for me, but I got it all working in half an hour or so. C12 has been very well behaved so far. Love the free warp thing and the new fade editor.

[pixel85]

From what I see at Steinberg forum, I'm not sure if I want to risk an update. It looks like a disaster. Not only to get an update but to run C12 without any issues.
Remove videoengine, remove preferences, trash C11, remove plugins, make Mayan style sacrifice... and then it will eventually work.
Next tip: to use C12, don't use audio, midi and video. All other functions will work

Well, of course you only see the problem cases in the forums, all the other users that have no problems don’t write about that.
The grace period/migration process was a convoluted mess, but so far I didn’t encounter any problems in C12. And as you can, as always, install the new version in parallel, there’s really no danger in trying it. If it doesn’t work on your system, just to back to 11 for the time being.

I know but can I predict that I'll not be 'the lucky one'?
If you didn't hear, there are cases where both licenses don't work and then you have no access to C12 and C11. You are at the mercy of Steinberg servers to let you update eLicenser again. I can't even get their new license app to work for 3 days in a row, it hangs on initialization. Will it work on Monday when I'll need Cubase ready for action (in case sh*t hits the fan)? Nobody can't guarantee that.
Then even if I get C12 and I'll have issues, is trashing C11 preferences really a solution? I have a lot of my own settings that I need for comfortable work so it's not a solution for me. And yes, it's one of the official "solutions".
I need Cubase for my work and risking such a mess isn't worth it in my case. Especially if I have to pay $99 just to see if I'm lucky or not.

[EnGee]

This is very encouraging to know. Are you using the new license management?

Of course. c12 only works with that.

Great thanks!
So maybe the absence of e-licenser has improved the performance! Just a guess though!

I might upgrade next month as I don't have a grace period and I'm busy now with learning (well) Live 11 that I just upgraded to from v10 today.

[Atlatnesiti]

Great update, thanks heaps Steinberg for Apple M1 support- didn’t expect it so soon
Btw; Who ever said that Cubase pro 12 runs under Rosetta after installing on M1 by default is wrong.
It defaults to “universal”
PS: my DAWs that I have that currently natively support M1 are:
- Logic (of course)
- Ableton Live Suite 11
- Cubase Pro 12
The only one left on my Mac that is still running under Rosetta is Reasonstudios Reason:(
Also it is the only one NOT capable of hosting Vst 3
WTF

[fmr]

Does anyone know if you still can run Cubase versions (pre 12), once you have converted your license to the new system?

You can, as long as you have the dongle inserted.