Steinberg has released Cubase 14

[xbitz]

you can still play around with the pre/post fader extraction point, but then I figured you also need to adjust the send levels with VCA fader moves, otherwise everything goes to the group at the same level.

federe2.gif

it can work

This indeed worked! So basically with that green line I spitted the signal. Everything that is located above that line is being sent to the group channel. Thank you!

just need to group the original track and the effected one into a new group and do the fader riding there, otherwise anything coming from a pre-send will keep going at the original signal level — the mindset is like the FX track inside a group in Bitwig ... you’ll see and hear it anyway.

let's say it’s the same issue in FL too if you use Fruity Send — nothing new here

[xbitz]

btw. The Cubase sale is on
40% off until October 1, 2025

[Igro]

After using it for two weeks, I can say, that while it has amazing built-in effects, it is just nowhere near to Bitwig's routing flexibility and workflow. You cannot route midi from a Instrument or Sample track. To make a midi sidechain, you have to create a "shadow" midi tracks. I hope they will improve that in Cubase 15. And they really need to make their own FX splitters, like those Bitwig's FX Layers and Instrument Layers. They need to look at what other DAWs already can do and make it better.

[xbitz]

After using it for two weeks, I can say, that while it has amazing built-in effects, it is just nowhere near to Bitwig's routing flexibility and workflow. You cannot route midi from a Instrument or Sample track. To make a midi sidechain, you have to create a "shadow" midi tracks. I hope they will improve that in Cubase 15. And they really need to make their own FX splitters, like those Bitwig's FX Layers and Instrument Layers. They need to look at what other DAWs already can do and make it better.

You could have saved yourself two weeks — Dash already compiled this when he dropped Cubase. The two DAWs have different strengths, so you should pick the one that best supports your workflow. If you don’t need to mix 30 tracks of live drums phase correctly with tempo fluctuations or put together a full orchestra (with MIDI orchestration) etc., then obviously you don’t need Cubase.

&

or check hybrid orchestration with zillions different keyswitches expressions maps and articulations also wouldn't pick Bitwig here

[lotus2035]

I just bought the upgrade from Elements 14 to Artist 14 but I'm gonna sit on the download access code until 15 comes out and get the free update.
Had a few years with FL Studio after having used Cubase before that, got the Cubase itch again and I'm loving 14. Curious to see what 15 will bring.
I would like to see Steinberg upgrade the GUI to a modern vector-based type interface similar to FL and Ableton. I have no problem with the latest overall design, but some elements of the underlying interface must date back to the 90's if not the early 2000s. The pool window for example, straight outta Cubase SX3, at least on Windows.

[Igro]

After using it for two weeks, I can say, that while it has amazing built-in effects, it is just nowhere near to Bitwig's routing flexibility and workflow. You cannot route midi from a Instrument or Sample track. To make a midi sidechain, you have to create a "shadow" midi tracks. I hope they will improve that in Cubase 15. And they really need to make their own FX splitters, like those Bitwig's FX Layers and Instrument Layers. They need to look at what other DAWs already can do and make it better.

You could have saved yourself two weeks — Dash already compiled this when he dropped Cubase. The two DAWs have different strengths, so you should pick the one that best supports your workflow. If you don’t need to mix 30 tracks of live drums phase correctly with tempo fluctuations or put together a full orchestra (with MIDI orchestration) etc., then obviously you don’t need Cubase.

&

or check hybrid orchestration with zillions different keyswitches expressions maps and articulations also wouldn't pick Bitwig here

Yeah, you are right. I exaggerated my thoughts. I should have added the opposite too - there many Cubase features that other DAWs can only dream to get. Especially when it comes to mastering.

[Alexander_D]

After using it for two weeks, I can say, that while it has amazing built-in effects, it is just nowhere near to Bitwig's routing flexibility and workflow. You cannot route midi from a Instrument or Sample track. To make a midi sidechain, you have to create a "shadow" midi tracks. I hope they will improve that in Cubase 15. And they really need to make their own FX splitters, like those Bitwig's FX Layers and Instrument Layers. They need to look at what other DAWs already can do and make it better.

You could have saved yourself two weeks — Dash already compiled this when he dropped Cubase. The two DAWs have different strengths, so you should pick the one that best supports your workflow. If you don’t need to mix 30 tracks of live drums phase correctly with tempo fluctuations or put together a full orchestra (with MIDI orchestration) etc., then obviously you don’t need Cubase.

&

or check hybrid orchestration with zillions different keyswitches expressions maps and articulations also wouldn't pick Bitwig here

Yeah, you are right. I exaggerated my thoughts. I should have added the opposite too - there many Cubase features that other DAWs can only dream to get. Especially when it comes to mastering.

Yeah indeed! And also film scoring as well. Really sweet DAW for this!

[lfm]

And also film scoring as well. Really sweet DAW for this!

After Quicktime was deprecated for Windows 2014, I waited until 2018 for the new video engine in Cubase and found that as a serious cpu hog!!!!!

I could even run video in a plugin inside Cubase with a fraction of cpu use
https://vidplayvst.com/downloads.htm

Same with StudioOne and Sonar, I don't even notice video is there as well when it comes to handling a project, starting transport or stopping etc.

As new video engine for Cubase came I dropped Cubase because of it. Seriously bothered by poor performance and working around this crap.

What do you find so "sweet" about Cubase for scoring?

[koko8k44]

It's about time you started selling VariAudio as a plugin...

[Alexander_D]

And also film scoring as well. Really sweet DAW for this!

After Quicktime was deprecated for Windows 2014, I waited until 2018 for the new video engine in Cubase and found that as a serious cpu hog!!!!!

I could even run video in a plugin inside Cubase with a fraction of cpu use
https://vidplayvst.com/downloads.htm

Same with StudioOne and Sonar, I don't even notice video is there as well when it comes to handling a project, starting transport or stopping etc.

As new video engine for Cubase came I dropped Cubase because of it. Seriously bothered by poor performance and working around this crap.

What do you find so "sweet" about Cubase for scoring?

I don't know the full answer honestly. I was finished 7 movies in Cubase. And it's really good. Any alternatives? Logic? Don't know. Cubase MIDI is so powerful!

[lfm]

I don't know the full answer honestly. I was finished 7 movies in Cubase. And it's really good. Any alternatives? Logic? Don't know. Cubase MIDI is so powerful!

Thanks.

But did you do this over just a couple of years, or also while Quicktime was used.
- I understand you run Mac, but still

Or is Mac running Quicktime still in Cubase?
- or Cubase own video engine

Out of curiosity to be up to date on state of Cubase if video engine is optimized better now?

This is one major obstacle why I dropped Cubase. If running video you had to start freezing tracks much earlier due to this, maybe reduce project by 30-40 tracks before that happend.

Sadly there is another serious obstacle as well, that indicate Steinberg cannot fully navigate their own projects.
- we were some people reported since 2015 about how multiout VSTi:s were a complete mess where order of outs just smashed and some extra tracks and whatnot
- I had this doing track templates saving some tracks
- others got it if disabling some tracks, and Cubase lost track of things

I know one fellow here as well as at Steinberg forum at the time looked into this in dialog with Steinberg, but not sure if finally fixed after v10 of Cubase or not. It still happend at v10 as I recall.

[jancivil]

I don't know the full answer honestly. I was finished 7 movies in Cubase. And it's really good. Any alternatives? Logic? Don't know. Cubase MIDI is so powerful!

Thanks.

But did you do this over just a couple of years, or also while Quicktime was used.
- I understand you run Mac, but still

Or is Mac running Quicktime still in Cubase?
- or Cubase own video engine

Out of curiosity to be up to date on state of Cubase if video engine is optimized better now?

It begins to appear now you had an issue - a known issue* - with the translation of Quicktime format to another codec. You seem to believe or want to believe there is some issue with Cubase and video universally. This is *a Windows thing. QuickTime being a Mac OS application in the strictest sense will tend to be (virtually certain it will be) very efficient in Mac OS.

I have never had video that isn't either .mp4 or .mov. I can safely assume that, since importing a video (that with my preferences is not creating a copy in the project folder) creates a .csh in the source folder, that the video, a .mov or .mp4 in the Cubendo project is what I see in the source folder. A video in a Cubendo project has the lightest of footprints here.

[lfm]

It begins to appear now you had an issue - a known issue* - with the translation of Quicktime format to another codec.

No, not at all. I also only used MOV files from Canons cameras with H264 inside, and mp4 also H264 inside.

Quicktime installed on Windows was a requirement like for Cubase to run video(any format) before 2014 as Microsoft considered it a security risk that Apple would not fix.

You seem to believe or want to believe there is some issue with Cubase and video universally. This is *a Windows thing. QuickTime being a Mac OS application in the strictest sense will tend to be (virtually certain it will be) very efficient in Mac OS.

I have never had video that isn't either .mp4 or .mov. I can safely assume that, since importing a video (that with my preferences is not creating a copy in the project folder) creates a .csh in the source folder, that the video, a .mov or .mp4 in the Cubendo project is what I see in the source folder. A video in a Cubendo project has the lightest of footprints here.

Interesting to know that Quicktime never was a security risk on Mac, thanks.
- I keep forgetting not everybody are on Windows

Some video editors always consider MOV as quicktime codec and refused to load them, but that is not always the case with MOV on some Canons I have. Timelapse video do for one.

But unclear if Steinberg kept using Quicktime on Mac for video or not?
- or their new video engine they developed
- I think it was ready fall 2018 running CP9.5 and that was horrific, and moved to StudioOne then with a fraction of cpu load. Same gear, same project since StudioOne could import Cubase projects.

[Igro]

What do you think, when we can expect v15? Before the winter?

[qtheerearranger]

besides cubase 12 the releases have been consistently in November since 9.5