Steinberg has released Cubase 14

[xbitz]

One question:

I didn´t try this when demoing Cubase 14... can a by the new Modulators modulated parameter still be automated or does Modulation/Automation completely take over like it was in Ableton before?

it's not an AL one (it's like the new M4L modulation in AL12) — linking a control to a macro creates a big macro button and a dial, and the macro adjusts the dial's offset, neighboring modulators (from othere slots) also works on the dial's offset (just from a different slot), but the dial itself(which represents the linked control in modulation framework) remains automatable



so all the modulation plays with different offsets, it doesn't interfere with the automation, the only issue is that it's tied to tracks, so you can't save it as just a device preset, only as a track preset

ps. I think Transit2 is similar with its new modulators, but I've played with it only once

[Trancit]

One question:

I didn´t try this when demoing Cubase 14... can a by the new Modulators modulated parameter still be automated or does Modulation/Automation completely take over like it was in Ableton before?

it's not an AL one (it's like the new M4L modulation in AL12) — linking a control to a macro creates a big macro button and a dial, and the macro adjusts the dial's offset, neighboring modulators (from othere slots) also works on the dial's offset (just from a different slot), but the dial itself(which represents the linked control in modulation framework) remains automatable



so all the modulation plays with different offsets, it doesn't interfere with the automation, the only issue is that it's tied to tracks, so you can't save it as just a device preset, only as a track preset

ps. I think Transit2 is similar with its new modulators, but I've played with it only once

Thx for your time...!

[xbitz]

^^^ np, instant karma "Welcome to the Cubase 15 Beta programme!" I'll expertly analyze whatever brilliant conclusions they came to....

[mothra]

^^^ np, instant karma "Welcome to the Cubase 15 Beta programme!" I'll expertly analyze whatever brilliant conclusions they came to....

Oooh I filled that out awhile back too.. I gotta go check my email haha.

[tappert]

When Steinberg's summer promotions take place usually?

[mothra]

When Steinberg's summer promotions take place usually?

During the summer?

[tappert]

[dionenoid]

Cubase 14.0.30 is available now :

https://www.steinberg.net/cubase/release-notes/14/

[tonymax]

Seems like Nuendo is updated also.. 14.0.30 available as an update as well as Cubase

Cubase 14.0.30 is available now :

https://www.steinberg.net/cubase/release-notes/14/

[Weasel-Boy]

If you run your SDA, you'll find Cubase 14.0.32 waiting.

[mothra]

.32 is the same as .31, it just includes the MIDI Remote scripts they forgot to put in .31..

[jrwaltb]

Some of these fixes are terrifying considering how long Cubase has been around. "Malformed BWF files can now be tagged safely, without the risk of corruption or file size inflation." I heard about this bug, and the fact that it's just now getting fixed is mind-blowing considering it was causing file corruption, which I think was affecting the whole Media Bay if it happened.
I recently purchased WaveLab Pro, and honestly, I should have purchased Audition even though it seems like it is almost completely abandoned. WaveLab cannot audition files of a different sample rate on Mac without a 7-second delay and a physical interface sample rate change, even in the browser. Also, for some reason, it will not allow time stretching on files below 10,000 samples, which completely rules out stretching wavetables to 2,048 samples—something which Audition can do and one of the reasons I even purchased an audio editor. Also, little things like sample key detection report different keys depending on whether it's done in the timestretch menu or sample info menu—it's maddening.

Just one of these would ruin any project I was working on - I only own wavlab and I am venting here but this is dangerous shit. Now I worry batch processing with WL might not be worth the risk. :

"FLAC files imported into 32-bit float projects are now processed without distortion."

"Compressor settings in the Channel Strip now remain intact after reactivating a project." (does this mean opening a saved song !?)

"Audio files retain their integrity when their metadata is edited in the MediaBay."

"Emptying the trash can after removing unused media no longer causes instabilities."

"Projects now remain stable when Drum Machine samples refer to Pool files with different sample rates." (what does "stable" mean?)

"The Project Logical Editor presets “Nudge Parts or Events inside Cycle +/-1 Frame” now work as expected, improving precision during timeline editing."

"Delay compensation now works consistently, regardless of the channel configuration."

"Audio Export processes are now successfully completed when Modulators are used."

[Resonant- Serpent]

Some of these fixes are terrifying considering how long Cubase has been around. "Malformed BWF files can now be tagged safely, without the risk of corruption or file size inflation." I heard about this bug, and the fact that it's just now getting fixed is mind-blowing considering it was causing file corruption, which I think was affecting the whole Media Bay if it happened.
I recently purchased WaveLab Pro, and honestly, I should have purchased Audition even though it seems like it is almost completely abandoned. WaveLab cannot audition files of a different sample rate on Mac without a 7-second delay and a physical interface sample rate change, even in the browser. Also, for some reason, it will not allow time stretching on files below 10,000 samples, which completely rules out stretching wavetables to 2,048 samples—something which Audition can do and one of the reasons I even purchased an audio editor. Also, little things like sample key detection report different keys depending on whether it's done in the timestretch menu or sample info menu—it's maddening.

Just one of these would ruin any project I was working on - I only own wavlab and I am venting here but this is dangerous shit. Now I worry batch processing with WL might not be worth the risk. :

"FLAC files imported into 32-bit float projects are now processed without distortion."

"Compressor settings in the Channel Strip now remain intact after reactivating a project." (does this mean opening a saved song !?)

"Audio files retain their integrity when their metadata is edited in the MediaBay."

"Emptying the trash can after removing unused media no longer causes instabilities."

"Projects now remain stable when Drum Machine samples refer to Pool files with different sample rates." (what does "stable" mean?)

"The Project Logical Editor presets “Nudge Parts or Events inside Cycle +/-1 Frame” now work as expected, improving precision during timeline editing."

"Delay compensation now works consistently, regardless of the channel configuration."

"Audio Export processes are now successfully completed when Modulators are used."

Most of these issues were incredibly niche, effecting a small amount of users, and a majority never had a problem. When there was a large problem, like the recent offline processing bug, it took them just a few days to fix it. After bouncing between Studio One, Ableton Live, and Cubase over the last year; Cubase is far more stable and has less bugs than the other two. I know of at least a dozen serious bugs in Studio One that haven't been fixed in years. Ableton is better than it has been during this release cycle, but MaxforLive is still a crap shoot.

[jrwaltb]

Some of these fixes are terrifying considering how long Cubase has been around. "Malformed BWF files can now be tagged safely, without the risk of corruption or file size inflation." I heard about this bug, and the fact that it's just now getting fixed is mind-blowing considering it was causing file corruption, which I think was affecting the whole Media Bay if it happened.
I recently purchased WaveLab Pro, and honestly, I should have purchased Audition even though it seems like it is almost completely abandoned. WaveLab cannot audition files of a different sample rate on Mac without a 7-second delay and a physical interface sample rate change, even in the browser. Also, for some reason, it will not allow time stretching on files below 10,000 samples, which completely rules out stretching wavetables to 2,048 samples—something which Audition can do and one of the reasons I even purchased an audio editor. Also, little things like sample key detection report different keys depending on whether it's done in the timestretch menu or sample info menu—it's maddening.

Just one of these would ruin any project I was working on - I only own wavlab and I am venting here but this is dangerous shit. Now I worry batch processing with WL might not be worth the risk. :

"FLAC files imported into 32-bit float projects are now processed without distortion."

"Compressor settings in the Channel Strip now remain intact after reactivating a project." (does this mean opening a saved song !?)

"Audio files retain their integrity when their metadata is edited in the MediaBay."

"Emptying the trash can after removing unused media no longer causes instabilities."

"Projects now remain stable when Drum Machine samples refer to Pool files with different sample rates." (what does "stable" mean?)

"The Project Logical Editor presets “Nudge Parts or Events inside Cycle +/-1 Frame” now work as expected, improving precision during timeline editing."

"Delay compensation now works consistently, regardless of the channel configuration."

"Audio Export processes are now successfully completed when Modulators are used."

Most of these issues were incredibly niche, effecting a small amount of users, and a majority never had a problem. When there was a large problem, like the recent offline processing bug, it took them just a few days to fix it. After bouncing between Studio One, Ableton Live, and Cubase over the last year; Cubase is far more stable and has less bugs than the other two. I know of at least a dozen serious bugs in Studio One that haven't been fixed in years. Ableton is better than it has been during this release cycle, but MaxforLive is still a crap shoot.

100% that they all have issues and if the bugs listed are actually very niche that is very good news. So I own Ableton Suite, Studio one Pro 7 ... Actually is does not matter, hopefully the corruption, PDC and sample offset bugs were rare because its a waste of time trying to make music with stuff like that going on. TLDR: Thank God for Ableton

[VitaminD]

I suppose reading the release notes could give pause, but really you're unlikely to hit these bugs. And, even if you somehow did, could work around them until they were resolved.

But this is why you wait for a release to mature before upgrading, if your use of the software is mission critical. Being on the cutting edge means you are giving up safety for features.