Steinberg has released Cubase 14

[Weasel-Boy]

Cryophonik wrote:

Yeah, that pretty much sums up the threads I saw. I don't see that being a deal breaker for me, and I went ahead and bought the upgrade a little while ago.

Wasn’t a dealbreaker for me either, particularly when I don’t need polyphonic pitch correction, as Cubase’s built in Varipitch editor is a killer. I find it’s algorithm infinitely superior and so much easier to use than Celemony’s when editing pitches monophonically. And it doesn’t care if you change the tempo or pitch beforehand.

[Resonant- Serpent]

Starting Cubase 14, loading projects, and moving about the interface is much snappier here than it was in 13. Noticeable difference right out the gate. On Windows 10.

[dionenoid]

- automation parameter selection - some vst3 plugins you can right click and assign to a new automation lane but at least half of them if not more then half you cant.

Yep. It's not a Cubase issue tho, it's just that many devs are lazy and/or incompetent and didn't update their plugins to the latest VST3 specs. I'm sure it will eventually work for much more plugins.

[4damind]

I have seen that VST2 is now also disabled under Windows (even if you can still activate it). I wouldn't be surprised if support ends completely with Cubase 15.
On the Mac there is only VST3 in the native version for Apple Silicon. However, there are for me only very few plugins that currently no longer run under Cubase, e.g. Sonalksis or ArtsAcoustic.

[chagzuki]

When you purchase the download code, you don't have to activate it right away. I am on Cubase 12. I bought Cubase 13 upgrade in March 2024, but just sat on the code. November 6th when they announced 14, I applied the code to my account, and was in the grace period and got 14 for free. I've been doing this since at least Cubase 6. I'm fine being patient for 2 years and getting every other version of Cubase for a heavy discount and just live with the older version for 2 years.

Thanks for clearing that up, I was wondering if that strategy worked. Looks like that'll be my approach going forward.

[SLiC]

I switched from Cubase 8 to Studio One some time ago, but I have to say this looks like a great update, may even demo again! Well done Steinberg!

[xbitz]

fyi, splice was updated https://splice.com/plugins/search?category=daw to C14

[xphen0m]

Anyone else getting crashing when trying to load STL Tones plugins?

[mothra]

November 6th when they announced 14, I applied the code to my account, and was in the grace period and got 14 for free.

That actually has nothing to do with the grace period, which is only for people that have already activated their license within the time period.

If you sit on the code and don't activate it, the grace period doesnt matter at all, you technically don't have a Cubase license at that point. You get whatever version is the current one when you activate the code. If you would have done it two days before, THEN you would need the grace period to upgrade and you would have to update the license in the Manager again. Since you waited until 14 was released, the system just gives you 14.

[beltrom]

Looks quite nice! A little bit worried about it not officially supporting VST2. I'll probably wait a week or two and keep an eye on how it's received, but I will probably upgrade.

Updated from 13 pro to 14 pro today. I'm weak...
Played around with it a couple of hours, no problems what so ever.

[chagzuki]

If you sit on the code and don't activate it, the grace period doesnt matter at all, you technically don't have a Cubase license at that point. You get whatever version is the current one when you activate the code. If you would have done it two days before, THEN you would need the grace period to upgrade and you would have to update the license in the Manager again. Since you waited until 14 was released, the system just gives you 14.

Is there a period in which you're required to activate, use it or lose it?

[felis]

Is there a period in which you're required to activate, use it or lose it?

I don't think there is now. But of course, that could change. They'd probably have to give some kind of notice though. It's a gamble.

[mothra]

Is there a period in which you're required to activate, use it or lose it?

Not that I've seen. People used to hang on to codes bought during sales for a version or two, sometimes three before they used them. If the update doesn't have what you want, grab the license cheap on sale and hang on to it until the next one that does.. I almost gave in and bought Absolute for 70% off a couple months back but figured GA6 is probably around the corner and was going to hold the license until it got released. But I decided I didn't want to be stuck with the Absolute license (you have to wait until IT gets updated after the individual components do).

It's kind of funny, all the crap people talk about Steinberg this and that, they're actually pretty damn generous with their stuff.

[DaveClark]

I clicked the upgrade pretty quickly.

I’ll probably go see what they’re saying on the Cubase forums but has anyone noticed the modulation isn’t ‘fast’? It’s like they all have a slew rate adding a ramp time to the change. When I want a saw shape mod, I want that vertical edge to hit immediately. I couldn’t find a slew control.
Still… lots of cool ideas in 14.

For anyone seeing the potential problem, please ensure that this is tested and reported for plugins that have per-sample updates, i.e. not per-block of audio being processed at a time by the plugin. Plugins that process per block are going to necessarily have delays that will depend upon the block size.

[qtheerearranger]

I clicked the upgrade pretty quickly.

I’ll probably go see what they’re saying on the Cubase forums but has anyone noticed the modulation isn’t ‘fast’? It’s like they all have a slew rate adding a ramp time to the change. When I want a saw shape mod, I want that vertical edge to hit immediately. I couldn’t find a slew control.
Still… lots of cool ideas in 14.

For anyone seeing the potential problem, please ensure that this is tested and reported for plugins that have per-sample updates, i.e. not per-block of audio being processed at a time by the plugin. Plugins that process per block are going to necessarily have delays that will depend upon the block size.

and is it being considered a bug? i haven't personally noticed this. seems like something like pdc that they can eventually fix?