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

[Jolaff]

Is there a trial ?

[4damind]

Just out of interest... now that Cubase makes it easier to open the channel EQ "on the fly", is anyone more likely to use the Cubase channel EQ instead of an extra plugin for low cuts, for example?

By the way, Cubase 13 seems to be very stable, I've had it open and composing for many hours... not a single problem... I'm very happy with the update so far!

[pepelogu]

Have used it for a few hours now and man, Steinberg knocked this one out of the ballpark. Love the new stuff, seems stable as a rock, many little tweaks to speed up workflow.

[midi_transmission]

never mind

[Raddler1]

Is there a trial ?

Wondering the same....

[billcarroll]

Just out of interest... now that Cubase makes it easier to open the channel EQ "on the fly", is anyone more likely to use the Cubase channel EQ instead of an extra plugin for low cuts, for example?

By the way, Cubase 13 seems to be very stable, I've had it open and composing for many hours... not a single problem... I'm very happy with the update so far!

I think the Cubase EQs are really good. I've always used the built-in Cubase Pre Gain, Low Cut, High Cut, along with the rest of the built-in EQ.

I usually don't need another EQ, but when I do I usually just go for FabFilter Pro-Q 3 or something like the UAD Pultec. Maybe now I'll try the new Cubase Pultec first.

Now that I think about it, I do use the UAD Neve 1073 Preamp & EQ in just about every project.

[chk071]

Is there a trial ?

Wondering the same....

If it's like on former versions, the trial comes a bit later. Usually a few weeks after release.

[koolkeys]

Ah yes, another extremely minimal update disguised as a major update from the company that motivated CLAP to come into existence because of their decades-long inability to properly support multithreaded multimedia or properly QA hardware platforms for their fully hardware-dependent software. Yes, let me think about spending more $$ on a company whose customer service is among the *worst* in the entire industry, and who handle legitimate customer frustration by trying to hide it.

No, the bliss I have been experiencing using Bitwig for the past 6 months has washed away decades of frustration with this brand, and this brand can kiss my entire $#%@$%#@%#@%.

So why even use your brain power to worry about this? Go use Bitwig. What purpose is there for you to even check a thread about a product you loathe from a company you loathe when you are experiencing such magical bliss from another program?

Trolling? Determined to poop in the cereal of those who DO like the update and Cubase? Your mission in life to pull others away from a program so you feel justified in your hatred? Are you just bored?

Never mind. Don’t answer that. It really is irrelevant.

I guess the positive part is that you weren’t here trying to make it about REAPER like others do. So you got that going for ya…….

[Trensharo]

Can somebody answer this please:

Ableton Link has been kinda industry standard since rewire got flushed down in the toilet. Pro Tools has it. Logic has it. NI Machine has it. EVEN STEINBERG’S OWN CUBASIS APP HAS IT.

Is it even remotely possible that Steinberg would not add this to their flagship product? Please calm me down and tell me I am just missing it.

Ableton Link and ReWire are two completely different things.

Ableton Link is predominantly for multi-device synchronization.

ReWire did this between Master & Slave (Host & Device?), but it also facilitated the piping of Audio and MIDI Data between the two software applications, by exposing the Audio and MIDI Channels of the Slave/Device to look like a hardware device. Ableton Link does not do any of that. Its only concern is synchronization.

There is nothing else on the market that really does what ReWire does.

TL;DR: Ableton Link will allow your DAW and Scoring App to stay in sync (timing, transport, etc.), but it will not allow the Scoring App to pipe MIDI Data to the DAW to trigger virtual instruments hosted in that DAW.

90% of DAWs that had "ReWire Support" omitted ReWire MIDI. 75% of those that supported ReWire at all only allowed you to pipe the Stereo Master from the Device to the Host.

Unless you stayed within a pretty exclusive corridor of choices, you couldn't really get a proper ReWire workflow. That's why the lost of ReWire was such a PITA to so many people. They had already gone the extra mile to limit themselves to specific Host/Device applications to establish that workflow, and there was (and is) nothing on the market that really steps in to fill the voice left by the sunsetting of ReWire. You basically have to just reinvent how you do your work and move on (or stay on older versions of software to maintain it - hoping operating systems do not obsolete it (move to, or stay on Windows, basically )).

[dionenoid]

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

Anyway, everything's very snappy and stable. Some nice workflow improvements. Some nice new plugins, some pretty bad. Channel Tab huge time-saver. Not immediately a fan of the new look, guess i gotta get used to it (luckily it transferred my old color schemes tho). Midi plugin overhaul was needed.

Oh, and while i didn't think much of it before i did the update, i was pleasantly surprised by the Vocal Chain.

Now, time to check out some more stuff.

[Trensharo]

Ah yes, another extremely minimal update disguised as a major update from the company that motivated CLAP to come into existence because of their decades-long inability to properly support multithreaded multimedia or properly QA hardware platforms for their fully hardware-dependent software. Yes, let me think about spending more $$ on a company whose customer service is among the *worst* in the entire industry, and who handle legitimate customer frustration by trying to hide it.

No, the bliss I have been experiencing using Bitwig for the past 6 months has washed away decades of frustration with this brand, and this brand can kiss my entire $#%@$%#@%#@%.

So why even use your brain power to worry about this? Go use Bitwig. What purpose is there for you to even check a thread about a product you loathe from a company you loathe when you are experiencing such magical bliss from another program?

Trolling? Determined to poop in the cereal of those who DO like the update and Cubase? Your mission in life to pull others away from a program so you feel justified in your hatred? Are you just bored?

Never mind. Don’t answer that. It really is irrelevant.

I guess the positive part is that you weren’t here trying to make it about REAPER like others do. So you got that going for ya…….

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).

Even if you go to the Steinberg forums, there are almost no threads there complaining about ASIO or VST that don't ultimately end up in a developer [being reported to have found an] issue that they need to fix on their end to rectify the problem. This is the case with almost all major plug-in developers or device manufacturers.

I still think ASIO is the devil and more DAWs need 1st rate Windows Audio Support, along with more interfaces being Windows Audio Class Compliant (like they are with Core Audio), because I have multiple devices that are practically unusable with multiple other DAWs, but still run well in Cubase... and I still have not figured out why that is the case. I have two interfaces here with drivers that won't even load in Digital Performer, and one that will crash Studio One 100% of the time... but I can use them for hours, days, months... with Cubase and get literally no issues.

Which ultimately amounts to hundreds of dollars wasted, because I cannot use an interface that I can only trust to work with one software product.

P.S. Issues with multi-threading with OpenFX plug-ins has been a common issue in the video world, so those aren't trivialities that one can just expect be magically solved overnight. In many cases, the host poses the larger issues do to how historical many of these products' code bases are.

Yes, a newer product will be able to avoid issues that may require significant reengineering in products that predate it by decades. News at 11.

[careyletendre]

Really liking the update so far. Seems like they are focused on refining and fine-tuning Cubase for those who use it every day. Great job!

[xphen0m]

Great update. Fast and snappy on everything. One of the C12 updates improved performance on my i5-12600k and it carried over to C13, thankfully. New Mix Console I'm getting used to, but I like it so far. I haven't tested the new MIDI editor stuff yet, however.

[Milkman]

Ah yes, another extremely minimal update disguised as a major update from the company that motivated CLAP to come into existence because of their decades-long inability to properly support multithreaded multimedia or properly QA hardware platforms for their fully hardware-dependent software. Yes, let me think about spending more $$ on a company whose customer service is among the *worst* in the entire industry, and who handle legitimate customer frustration by trying to hide it.

No, the bliss I have been experiencing using Bitwig for the past 6 months has washed away decades of frustration with this brand, and this brand can kiss my entire $#%@$%#@%#@%.

So why even use your brain power to worry about this? Go use Bitwig. What purpose is there for you to even check a thread about a product you loathe from a company you loathe when you are experiencing such magical bliss from another program?

Trolling? Determined to poop in the cereal of those who DO like the update and Cubase? Your mission in life to pull others away from a program so you feel justified in your hatred? Are you just bored?

Never mind. Don’t answer that. It really is irrelevant.

I guess the positive part is that you weren’t here trying to make it about REAPER like others do. So you got that going for ya…….

Speaking of wasting brain power, do you know where you are? Perhaps reorient yourself and do a little self-check and let me know what happens. If you make me come back and explain what I mean, it wont be nearly as polite as this comment.

[Milkman]

Ah yes, another extremely minimal update disguised as a major update from the company that motivated CLAP to come into existence because of their decades-long inability to properly support multithreaded multimedia or properly QA hardware platforms for their fully hardware-dependent software. Yes, let me think about spending more $$ on a company whose customer service is among the *worst* in the entire industry, and who handle legitimate customer frustration by trying to hide it.

No, the bliss I have been experiencing using Bitwig for the past 6 months has washed away decades of frustration with this brand, and this brand can kiss my entire $#%@$%#@%#@%.

So why even use your brain power to worry about this? Go use Bitwig. What purpose is there for you to even check a thread about a product you loathe from a company you loathe when you are experiencing such magical bliss from another program?

Trolling? Determined to poop in the cereal of those who DO like the update and Cubase? Your mission in life to pull others away from a program so you feel justified in your hatred? Are you just bored?

Never mind. Don’t answer that. It really is irrelevant.

I guess the positive part is that you weren’t here trying to make it about REAPER like others do. So you got that going for ya…….

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).

Even if you go to the Steinberg forums, there are almost no threads there complaining about ASIO or VST that don't ultimately end up in a developer [being reported to have found an] issue that they need to fix on their end to rectify the problem. This is the case with almost all major plug-in developers or device manufacturers.

I still think ASIO is the devil and more DAWs need 1st rate Windows Audio Support, along with more interfaces being Windows Audio Class Compliant (like they are with Core Audio), because I have multiple devices that are practically unusable with multiple other DAWs, but still run well in Cubase... and I still have not figured out why that is the case. I have two interfaces here with drivers that won't even load in Digital Performer, and one that will crash Studio One 100% of the time... but I can use them for hours, days, months... with Cubase and get literally no issues.

Which ultimately amounts to hundreds of dollars wasted, because I cannot use an interface that I can only trust to work with one software product.

P.S. Issues with multi-threading with OpenFX plug-ins has been a common issue in the video world, so those aren't trivialities that one can just expect be magically solved overnight. In many cases, the host poses the larger issues do to how historical many of these products' code bases are.

Yes, a newer product will be able to avoid issues that may require significant reengineering in products that predate it by decades. News at 11.

I started reading, then stopped reading your nonsense at "CLAP kiddies".

Brand management is certainly a nasty, sniveling business in the year 2023, is it not.