Where is Cubase 12.5 or 13? [Update: It's here C13 is released!]

[xbitz]

And why did steinberg not include better midi fx plugins?? Just a cheap gui update. Compared to Bitwig for example, the midi plugins are a joke...

There is this feature request on Steinberg forum I started as I ran Cubase back then.
https://forums.steinberg.net/t/vst-midi ... erts/94520

Nobody seems to bother with midi plugins. I tried talk to Waves long ago too.

But to set up a bunch of instruments and various midi handling between them I started using Bluecat Audio Patchwork that works well for that.

Then you can use the full lot of Piz Vst midi plugins. I use the gui-less which is the full series, meaning host creates a generic control for each parameter like knobs or sliders.

Available here:
https://code.google.com/archive/p/pizmidi/downloads

Mulab has its own note tweaking toolset + nice UI can be created with it (but as I see it uses only one CPU core)



although the biggest advantage over Bitwig, that it doesn't end up in endless tweaking instead of making music (trance is the genre) let say this is an advantage

[dionenoid]

Already found a downgrade of features: Double clicking a fader does not bring the fader to 0db any more. Why do you always remove stuff Steinberg?

Fader to 0 is and always has been ctrl+click.

Of course.. just a total brain fart from me.
I have been spending too much time with another mixer.....

Slightly off-topic, but i wished all daw's and plugins used the same system for this. Some use double-click, some use alt+click, some use cntrl+click, some even right-click. I get confused all the time.

[egbert]

Updating went well, fast downloading times. Kudos for improving the whole updating experience.

Yeah - very smooth these days. I remember having a great deal of trouble getting the 20GB archive down for the full download - back around Cubase 10.5 from memory. The archive arrived corrupted again and again.

I talked to Support and suggested the obvious thing - splitting it up - pointing out that many users might just want the application and not even be interested in some of the bulky sample/loop sets. I thought it would save Steiny a fortune in bandwidth costs. The guy I spoke to seemed open to the idea and ever since the download has been broken into subsections and it has never let me down once.

[mothra]

You get the nice quick interface if you use only the mixer versions of the Cubase plugins.

If you want to use both, then for me if I remember correctly, you need all the sections showing much of which is empty space, and you also can't flexibly reorder the combination of built in and third party.

I mean it's fine, and workable, and I think the concept is actually really great.

Its just not quite there for the way I work. The ability to reorder all plug ins on a channel, is more important than a completely consistent mixer to me. An example is I often drop in something to filter out low frequency, but I may place this in different, even multiple places in my FX chain, and also use a few different eqs to do this job, depending on the prominence of the part - so for this a fixed eq position doesn't always work.

If you're going to use the integrated plugins, you have to treat it as an actual console. The Cubase plugins are the console's channel strip. They are in their spot where they would be in a hardware mixer. Your third party plugins are 'inserts', just like they would be in a real console. Luckily they give you the option to go either pre or post channel strip, I don't have that option on any of the three Soundcrafts I have here. You can reorder your plugins all day long and use them how you want to, without even touching Cubase's channel strip, just leave them turned off (which they are by default) and don't open the channel strip editor. Problem solved, now it works just like Logic, Ableton, and everything else.

[bbvv]

Already found a downgrade of features: Double clicking a fader does not bring the fader to 0db any more. Why do you always remove stuff Steinberg?

Fader to 0 is and always has been ctrl+click.

Of course.. just a total brain fart from me.
I have been spending too much time with another mixer.....

Slightly off-topic, but i wished all daw's and plugins used the same system for this. Some use double-click, some use alt+click, some use cntrl+click, some even right-click. I get confused all the time.

I agree with this! Such a little thing that can be so annoying.

[_leras]

If you're going to use the integrated plugins, you have to treat it as an actual console. The Cubase plugins are the console's channel strip. They are in their spot where they would be in a hardware mixer. Your third party plugins are 'inserts', just like they would be in a real console. Luckily they give you the option to go either pre or post channel strip, I don't have that option on any of the three Soundcrafts I have here. You can reorder your plugins all day long and use them how you want to, without even touching Cubase's channel strip, just leave them turned off (which they are by default) and don't open the channel strip editor. Problem solved, now it works just like Logic, Ableton, and everything else.

Well, that's kind of the point. If I use everything as an insert then the updated console just doesn't get used. And it would be nice to use it.

In a perfect world I'd love to be able to hook into third party EQ, compressor, now tape in those built in slots. Most of these only have a few controls that would need mapping.

To be honest this has been a bit of a pain since Steinberg brought out the CC121, which has eq controls that can't map to a third party EQ.

Just saying it would be nice. Maybe one day.

[muzicxs]

In a perfect world I'd love to be able to hook into third party EQ, compressor, now tape in those built in slots. Most of these only have a few controls that would need mapping.

It would be great if CLAP can open the doors to this kind of integration with DAWs in the future. Imagine inserting any EQ plugin and being able to see it integrate automatically in the GUI of the DAW

[noiseboyuk]

FWIW...

I'm warming to C13 for reasons that hardly anyone has spoken about. There's been a bug going back for years that tracks with multi-outs saved in a disabled state open in a total mess. It now appears to be fixed. Finally it seems we can use disabled tracks of all kinds with confidence, which is for me a much bigger deal than anything new in C13.

The other one is Import Tracks from Project. This seems greatly improved and more reliable. If the routing is in place which is the same as the saved track, it will now route correctly. VIs get imported correctly. It seems much more useful and robust, again opening up all kinds of useful workflows - some people have a huge master project that they can import as much or as little of as they need.

Track Presets are still a mess though, I'll continue to avoid them - looks like they didn't get any love on this cycle.

[VitaminD]

I've had more time to use C13 and I'm still not liking these GUI changes.

While I'm happy to see the odd minimize and close behavior converted to standard Windows behavior, Steinberg now broke the Title bar and the Menu bar into two individual bars. In C12 they were combined. This gave more vertical room for more important things.

Further, the Menu bar in C13 is now white. And there isn't currently a means to change the color. Not in the Cubase settings and not in the Windows settings. It doesn't behave to any standard. It's just hard coded to be white it seems.

Which is glaring when you have a dark theme set in Cubase and Windows both. The Title bar and the Menu bar should be recombined again, as it was in C12, and they should obey the current Cubase theme colors.

Even worse, they shrunk the font size down to make it even tinier. Then they vertically shrunk the buttons and controls on the Inspector to match the font sizes. Then they removed the empty Insert nodes and now one must insert a VST to get another empty Insert Node. All of this combined makes it really really hard to use for me. I have 125% DPI scaling on in Windows and it set in Cubase yet the C13 GUI isn't obeying the scaling increases. Everything is just micro sized. I will get a headache squinting at this if I try to use it.

Maybe this looks great on 37" screens but on my 24" it is too small.

Then they made all the graphics themselves more flat. It looks more like Cubasis. But I bought Cubase. If I wanted Cubasis I wouldn't be in Cubase on a big Workstation PC, I'd be on a tablet. Tablet GUI for Tablets, Desktop GUI for Desktops please.

It's too bad they didn't just leave well alone. C12's GUI was really functional for me in that manner. Hopefully they'll add more configuration abilities to font size and Inspector behavior (maybe a 'legacy' C12 mode).

I'm glad if it works for you guys. But it isn't so great for me. I'm back to C12 for the time being until I see what the C13 updates bring.

[Trensharo]

It's almost like the CLAP kiddies (why does that sound so apropos?) are completely ignorant of AAX, MAS, AU, DX, etc.

It's like they think Steinberg VST has existed in a vacuum for all of its existence, and won by default simply for being the only option available...

Also, complaining on a thread full of Cubase users about VST[3] or ASIO [issues] is hilarious, since Cubase generally is as close to flawless as you can get with both of those. You will get the least amount of people nodding in agreement, so you will just end up triggering yourself and engaging in an unwinnable "debate" (due to little to no people experiencing the stuff that you claim you are or have).

Not very nice to joke about disabilities. Please be a better person than that.

Reported.

What disability? "Clap" is a colloquial term for Gonorrhea.

Pretty well known, and pretty much the worst name or acronym they could have chosen for this.

[Trensharo]

Anyone know what this means in practice?

It means Cubase now functions like a normal Windows application on Windows, instead of like a macOS Application.

The one thing you definitely don't want to port over to Windows when redesigning a cross-platform application... is macOS Window Management.

Lol. Steinberg managed to do all of that with Cubase.

They've now fixed this mistake.

[lfm]

FWIW...

I'm warming to C13 for reasons that hardly anyone has spoken about. There's been a bug going back for years that tracks with multi-outs saved in a disabled state open in a total mess. It now appears to be fixed. Finally it seems we can use disabled tracks of all kinds with confidence, which is for me a much bigger deal than anything new in C13.

The other one is Import Tracks from Project. This seems greatly improved and more reliable. If the routing is in place which is the same as the saved track, it will now route correctly. VIs get imported correctly. It seems much more useful and robust, again opening up all kinds of useful workflows - some people have a huge master project that they can import as much or as little of as they need.

That's interesting.

I had a different issue relating to that bug and it was track templates that I use frequently.
- also freaked out order of multi outs and all kinds of things

But if they also do Import From Projects as alternative even better.

One major thing left, did they last 5 years fix video engine enough to correspond to what other daws do cpu-wise?

In CP 9.5 this was extra 20% in Cubase compared to StudioOne or Sonar, same project.

Any improvement with themes or customizing colors in gui?

[noiseboyuk]

Ifm - I haven't A/B'd video, but they do say they're using hardware acceleration now for some popular codecs so it might well have improved.

Lots of opportunities to customise the colours, but some specifics are still limited - you can't just have the old simple white highlight with the font colour inverted to black.

[4damind]

I had a look at the new Vocoder... very interesting plugin. You should definitely try it out. You don't need an additional carrier because the synthesizer is included as a carrier in the plugin.
I got out my micro and made a test song... the whistling in the second part is of course not from the vocoder... that's me )

C13 Vocoder.mp3

[dionenoid]

Been using C13 for a few days now. Everything still rock solid. Was easy to get used to the new gui, and overall the workflow has improved for me.