Cubase 12 leaked on Steinberg's site

[T-CM11]

I'd really recommend a bit less selective reading, quoting, and, generally, understanding. Then you might stand a better chance to see things objectively, and realizing the needs of both sides. Then maybe you'll be able to judge things more fair. Although I highly doubt it.

But YOU do see things objectively, right? Must be nice!

[EnGee]

Not sure I understood the second para well here.

When you update to the new system any previous licenses that were eLicenser based become NFR. But you can sell the current license thats based on the Steinberg Licensing system.

If I buy Groove Agent 5 and activate it right now and let's say in future, after the new licensing is introduced and I have to obviously move to it, they release Groove Agent 6.

Can I update from GA5 to GA6? Can GA6 be resold then?

Of course it may be too early to ask this, but since I am planning to buy GA5 soon, I don't want to end up in a situation where I can't update to GA6. Reselling point is not a big deal right now.

Good point!

I think it depends if we can register (say) GA5 with the new system or not. If we can't update or upgrade our licenses then what? The new system only applied on buying new software?! It doesn't make sense!

But if they are sane people, then what they mean is "once you update/upgrade GA5 license to GA6 license in the new system, then you can only sell or update GA6 license and your GA5 license is worthless as you can't separate it from the updated/upgraded version.

Anyway, as companies seem lost the logic in thinking! I suggest you wait and don't buy anything till you see the things are settled and things seem logical!

Yes, I am hoping what you said is true and it indeed logical. But as fmr said it is a bit tricky for USB dongle cases. I believe migrating from soft e-licenser to new system is effectively the same thing (there is no hardware involved), so we should be able to update and resell (the latest version, not previous).

That's a good suggestion and I am indeed not buying it right away. I will only buy it if it goes on 50% discount.

In the meantime, I have dropped an email to support. Got a response already, but trying to reconfirm my understanding. Will post here once done.

Got the confirmation from Steinberg that updates/upgrades will be possible after migrating an existing license from existing licenser to new licensing system. Kinda no-brainer, but wanted to clarify it for myself.

Reselling might be a bit tricky, especially with USB e-licenser. It should be clearer once we get more information on this in future.

Great Thanks for the info
So now just remained the 50% discount (although I would buy it with 40% as well if I were you It's a great drums tools with nice various kits, I'm using it inside S1 these days and it runs very well).

[PAK]

That seems equally theoretical. Has this ever happened before?

That companies have taken activation servers offline? Of course. The example which immediately comes to mind, in the music world, is TC Electronic. Many people were left holding some very expensive plugin purchases when they removed all possible activation and transfer methods for their Powercore platform. Ironically, many years after doing so, just the other month someone finally cracked their code and essentially unlocked all plugins for all of its long suffering users.

The plugins will always be 32-bit btw, but are good enough that many people want to continue to use them (not least because the native alternatives, done under Behringer, aren't quite the 1:1 ports people wanted.. )

the whole notion of just opening anything up from 10 years ago is fanciful.

Well, long after the fact? You're right that'd be difficult. But keeping an archived folder, with all the versions of things used at the time, isn't exactly the hardest thing to do. Just create a new directory with each new DAW, and update the plugins. Literally minutes, with some planning, for the ability to edit in x years time. The main barrier often being activation / copy protection..

[dellboy]

So the good news is that if we upgrade to 12 we get to keep the dongle with Cubase 11 or whatever on it. And we can use the dongle with the old version on it on it on any computer that we choose. So always keep a backup of the old Cubase version and don't lose or break the existing dongle.

[v1o]

So the good news is that if we upgrade to 12 we get to keep the dongle with Cubase 11 or whatever on it. And we can use the dongle with the old version on it on it on any computer that we choose. So always keep a backup of the old Cubase version and don't lose or break the existing dongle.

I think that's correct. But there are certain tasks that require access to the e-licenser server which is being taken offline. You know tasks like transferring activations from one dongle to another.

[PAK]

You're really good at that. I mean leaving out important information, like the post I quoted when I replied. You said that something "mandates continued intervention from a company to allow its use.". Which basically could mean anything. Even having to phone call the company every time you want to use their product.

Except it didn't, because I then used it specifically in the context of the monthly and yearly activation mandate. Perhaps you missed that part?

The whole point is also that this proposed process introduces an additional element of uncertainty due to requiring users to activate every year. And, yes, that basically could mean anything. That's the point! Geez...

I'd really recommend a bit less selective reading, quoting, and, generally, understanding. Then you might stand a better chance to see things objectively, and realizing the needs of both sides. Then maybe you'll be able to judge things more fair. Although I highly doubt it.

I assume (I know it's asking too much sometimes) that people have some common sense and don't need every single possibility, of every single remark, spelled out to them.

You did a similar thing with dblock's post earlier, where you make people have to point out the obvious which, in that case, was that he knew he didn't "own" the software etc. Why? Because your interpretation of the English language appears overly literal at times, and apparently leaves you struggling to "read between the lines" of comments, and instead demanding that all uncertainty be quashed. I seriously hope your native language is not English.

[AcrossTheSky]

....So is there a recycling E-Licenser plan planned ? - or throw in a bin or toilet is the only option ...

[chk071]

You may use it as a suppository, if you dare.

Or you can donate it to PAK. I heard he's still looking for a free Cubase copy which still uses eLicenser.

[Compyfox]

Honestly, the only thing that people don't seem to see with this announcement, is the fact that long-term loyal users are being treated like crap yet again.

Those that didn't activate Cubase 11 "yet", now have have Grace Period
Those that didn't upgrade to Cubase 11 yet, now have a Grace Period

Both of these candidates, effectively saving hundreds of bucks.


Those that are on Cubase 11, will be forced to shell out 150EUR (or whatever the price will be) once Cubase 12 drops... no deals

...plus being stuck with bugs, because you can be damn sure there will be no v.1 or v.2 - Steinberg stopped doing that in early 2000s, with Nuendo being the exception (and a free upgrade on top)



Not only that:

Wavelab 11 is just a couple of months old, but still uses the Elicenser. I am 99,5% certain that 2022 will be huge in terms of income for Steinberg, because users are forced to jump yet another v.0 version, if that is not the straight future for Steinberg (same sh#t that Avid does, really.. pay for every .dot version and/or subscribe... Subscriptions are THE FUTURE!). SpectraLayers and Dorico were also pushed to 2022. Pretty sure Wavelab 12 (already) will drop in 2022 as well.

I swear, if Nuendo gets "free upgrades to the next v.0" once more, I'll flip my damn workstation.


Else I have literally zero expectations for Cubase 12 on "replace audio in video", "Cubase finally being able to do 7.1 at bar minimum" (BECAUSE VR EES ZE FJUTJAH! Spoiler: it isn't!), and proper efficient multi-core support (considering Intel Gen 12, AMD Ryzen and Apple M1).

BUT HEY! Tell your devs to finally wake up and move to VST3 already, because VST2 is dead and deprecated on M1. And VST3 is so much better... and "mostly" bug free <cough>



Footnote:
Maybe I should buy a spare Elicenser key, move my licenses just to be save (backup purposes) and drop my old key (that is... heck I don't know how old at this point). If Steinberg doesn't pull those keys from stores now. (also... the price went up for them? Holy crap!)

[jens]

Well, it is Apple's fault that everyone has to develop for a new architecture now.

Yeah, but Steinberg is making it sound like VST2 plugins CAN'T work on Apple Silicon without Rosetta, and that's just not true.

No they don't. All they say is that they don't support it.

[Compyfox]

Steinberg has been pushing "to move to VST3" for... is it over a decade now (must be, they said during SX3 days already "VST2 can't do side-chaining", which was the reason VST3 was pushed in the first place - to fix something they wou... er... "couldn't fix" in CubEndo)? Man, time flies.

We're currently on VST SDK 3.7.3...

I'm surprised we're not on VST4 yet, which actually plenty of developers I've been in touch with kind of hoped to happen at this point (fixing very, very annoying issues that need "workarounds" -- doesn't help that even Steinberg's own tools all interpret VST3 different! Yet it's always the 3rd party dev to blame)

[AcrossTheSky]

You may use it as a suppository, if you dare.

Or you can donate it to PAK. I heard he's still looking for a free Cubase copy which still uses eLicenser.

.... I should believe Steinberg will come up with a firmware to upgrade the eLicenser for whoever wishes to hold the license on the Key for a few more years to come. Why Not ?...if the license can be transferred to a USB device for an off line activation etc... why not use the existing blue key for that - especially if there are millions circulating around the planet like the stars....

[jancivil]

I'm not panicking, I'm very probably going to stay with 11.0.0, all of the updates were a problem here, I'm not spending on spec they will suddenly change culture from the one that's breaking old features and introducing new ones before they're ready, and making whack decisions all over anyway.

BTW, I have yet to see a need for a VST3 instrument to this day. VERY close to 100% of mine are hosted in VE Pro which doesn't support it.

[chk071]

I'd really recommend a bit less selective reading, quoting, and, generally, understanding. Then you might stand a better chance to see things objectively, and realizing the needs of both sides. Then maybe you'll be able to judge things more fair. Although I highly doubt it.

But YOU do see things objectively, right? Must be nice!

A heck of a lot more objective than many who posted in this thread, yeah. Definitely. And, it is nice. I'd definitely recommend to try it out one day.

[Funkybot's Evil Twin]

No they don't. All they say is that they don't support it.

What they actually said (emphasis mine)....

"Cubase 12 will introduce native Apple silicon support to begin with. Please be aware that VST 2 is not supported on native Apple silicon, except when run in Rosetta 2 mode. So please make sure that you let the plug-in manufacturers still hesitating to release VST 3 versions know that it’s about time!"

What they did NOT say....

Please be aware that Cubase will not support VST2 on native Apple silicon, except when run in Rosetta 2 mode.

Now...maybe that's what they meant to say. It's easy to get a statement out there and have people parse the wording and come away with a different meaning.

But the way I read the original statement is that they're saying VST2 itself is not supported on Apple Silicon...which isn't true. And that's exactly what the statement says when taken at face value. What is true, however, is that Cubase is not supporting VST2 on Apple silicon. Other hosts, like Reaper, already are.

The next thing they do is encourage users to go pester developers who don't already support VST3 to start. As though, that's the only way to get VST plugins running natively. Which again, no such restriction exists with VST2 plugins. The limitation is in Cubase's lack of support for Apple native silicon and VST2 plugins.