Steinberg has released Cubase 14

[VHSandCassette]

Im tempted , every time you guys release something they really tempt me to go for it . I started on cubase on the atari but I’ve been a long time logic user . I might start using both for variety cause I believe the daw is not necessarily importan, its what comes out is

[EnGee]

.... cause I believe the daw is not necessarily importan, its what comes out is

Yes, like what Jesus said:"It is not what enters your DAW, but the final mix what it counts".

[qtheerearranger]

Im tempted , every time you guys release something they really tempt me to go for it . I started on cubase on the atari but I’ve been a long time logic user . I might start using both for variety cause I believe the daw is not necessarily importan, its what comes out is

I mean Logic Pros audio editing is so trash. can't reverse a region half the time unless you bounce it to a new track. no ara. no solid warping algorithms. Flex Pitch is also trash and when it can actually work on something it just takes sooo much time to focus on.

the only thing Logic Pro does that cubase doesn't do that even most advanced logic users know about btw is dual mono plugins in logic. look up a video on dual mono plugins if your a logic user its brilliant.

Switching to cubase from logic will be anything but intuitive. I only recommend switching if you can suffer for a month. Your going to have times where no sound comes out of your track and your going to be confused. its just a lot more of a complicated daw to learn in 2025. that being said as someone who did suffer to learn it im so glad I did. its by far a bigger brother to logic.

also the modeled plugins in cubase are a lot better then logics. not saying logic doesn't have plugins that are better then cubase (looking at the auto filter where cubase has a great filter in Nuendo called post filter and they just keep it from cubase for what reason??).

the sampler is a bit more intuitive in logic as well. some of the features you won't have on cubases sampler track like pitch detection (they have in halion and backbone though)

if your switching to cubase I recommend googling how to do this in cubase and if that doesn't come up search the same question with the additional phrase logical editor because that thing can do so much.

also cubases piano roll is so much better.

I just think logic is slowly losing its reputation as a professional daw. don't get me wrong a lot of professionals still use it. but its not competitive in the daw market anymore imo. I know that's a controversial statement. but what a chord track, session player, and a reverb has been logic 11? lol im an Ableton hater but at least use Ableton over this junk. Bitwig is a solid choice if you're not looking at cubase.

I mean logic broke ara and it's been years.. they make no public statements. idk if its this video - but he says he meets the team and they don't have the support of apple essentially - and I don't want to single him out as I've heard it from a few channels that have gotten to meet the apple team - they all quickly change daws - doesn't anybody find that strange??? they meet the creators and lose faith lol

[keyman_sam]

DAWs are at a point where there’s no point in DAW wars anymore. They’re all superbly good, well featured and have everything under the sun.

I’m really tempted by the upgrade but I’ll wait for the 50% off summer discount. Stability is my most important concern, not features.
I moved from logic to Ableton for now. I might get back to cubase for acoustic projects just because the time stretch is better vs logic, mediabay, and better ara integration. I can get the same work done in logic, but I might be 10% slower.

[Hanz Meyzer]

Hi, currently retrying Cubase, and I have some questions. Maybe you experts have an answer here Also, the daw project support currently seems to be a buggy mess, did they test this at all...? A.k.a. export, import to Bitwig/S1, export again, etc. Or even import the just exported project...

1. Is there a way in Cubase to have a "parallel container" within a single track? So dsps route in parallel, without using additional tracks?

2. How would you export a song to Ableton, so keeping data intact in the most possible way?

3. Is there a way to scale down the GUI, like to 90%?

4. Any idea how to add pinch-to-zoom support?

5. Is there a way to disable specific MIDI inputs? So it will not be used at all?

6. The status bar visibility setting seems to be lost on every restart, is there a way to save the visibility settings?

[Serhii Kot]

Hi, currently retrying Cubase, and I have some questions. Maybe you experts have an answer here Also, the daw project support currently seems to be a buggy mess, did they test this at all...? A.k.a. export, import to Bitwig/S1, export again, etc. Or even import the just exported project...

1. Is there a way in Cubase to have a "parallel container" within a single track? So dsps route in parallel, without using additional tracks?

2. How would you export a song to Ableton, so keeping data intact in the most possible way?

3. Is there a way to scale down the GUI, like to 90%?

4. Any idea how to add pinch-to-zoom support?

5. Is there a way to disable specific MIDI inputs? So it will not be used at all?

6. The status bar visibility setting seems to be lost on every restart, is there a way to save the visibility settings?

1. No
2. By hand (recreating project from scratch).
3. No
4. Thru 3d party like keyboard maestro on Mac. But not that easy.
5. Don't know
6. Creating template project

[xbitz]

1. https://www.waves.com/studioverse free one supports VST3s in its parallel/band split containers
4. Any idea how to add pinch-to-zoom support?

https://github.com/pnoqable/PinchBar

By the way, it's worth checking out Dash Glitch's Cubase vs Bitwig videos — the same issues come up as with Ableton Live.

[Hanz Meyzer]

Thx guys, already helped.

For 6)
It will automatically appear as soon something is orange (not properly setup). I missed to seup audio inputs (never using it), now the bar isn't appearing anymore at restart.

[mothra]

5. Is there a way to disable specific MIDI inputs? So it will not be used at all?

Does nobody bother reading the manual when they attempt to use a DAW for the first time or just wing it and hope it works?

There's an entire Studio setup utility in Cubase to configure all of your I/O, whether it's your interface or your MIDI ports.

[Hanz Meyzer]

5. Is there a way to disable specific MIDI inputs? So it will not be used at all?

Does nobody bother reading the manual when they attempt to use a DAW for the first time or just wing it and hope it works?

There's an entire Studio setup utility in Cubase to configure all of your I/O, whether it's your interface or your MIDI ports.

Exactly these kind of comments prevented me to post in the Steinberg forum itself, I mean why are you being a smart ass providing pseudo info instead really helping? steinberg forum often reads like this.

Back to the topic, as far as I see it, you can only hide midi input, but not disable it... But the port will still send then data to Cubase! The manual does not help at all, way to convoluted and search results way too poor. Did I overlook some option, please?

[mothra]

Back to the topic, as far as I see it, you can only hide midi input, but not disable it... But the port will still send then data to Cubase! The manual does not help at all, way to convoluted and search results way too poor. Did I overlook some option, please?

The manual is for reference; it's not a 'how-to' guide or a tutorial on how to use Cubase. When you need to reference a feature, you look it up in the manual. The same goes for any product. The 'reference' manual is not intended to teach you how to use the product.

https://www.steinberg.help/r/cubase-pro ... _up_t.html

[Tj Shredder]

Steinberg manuals are made by technocrats. They are the opposite of being inspiring… If you look into the world of manuals, most get you started, and somewhere at the end, they have a reference. A reference is not a manual, its a reference…

[andi75]

Is there still no way to keep automation data when switching synths? I understand that it's not possible to remap the parameters automatically, but Cubase shouldn't simply delete the automation. This would be my most requested feature.
How do you guys handle this? Simply not change a synth which is heavily automated?

[Trancit]

Is there still no way to keep automation data when switching synths? I understand that it's not possible to remap the parameters automatically, but Cubase shouldn't simply delete the automation. This would be my most requested feature.
How do you guys handle this? Simply not change a synth which is heavily automated?

There is afaik just one DAW which doesn´t automatically delete Automation if you wish so but there is NO WAY a Daw could automatically remap automation parameters between different plugins because they each have different parameters and every developer uses different ID´s for the parameters available ...

This isn´t normed Midi CC´s... automation is completely up to the plugin developer...
As long as plugin automation isn´t normed (which will never happen) this cannot work!

[lfm]

I think you can select and copy automation to another track, at least the daw specific ones volume, pan and send amount.

So replace the synth and copy that back or something.

Not sure what the odds are you are actually using different synths with the same automation in general. Sometimes daws have Delete Special or similar option, and you get a dialog with checkboxes what to delete or paste etc.

There are loads of settings for automation in Cubase too, virgin territory and many things.