Steinberg has released Cubase 14

[tekknovator]

Yeah, thanks. I am primarily a "beatmaker" so thinking of going with Studio One. Using REAPER but want a changeup sometimes for a different experience as a secondary DAW. I think it's pretty cheap even with the version 7 Sub changes.

If making beats (presumably wanting fewer channels but better workflow), I'd definitely suggest trialling Bitwig.

Like reaper you can group and beat channels pretty easily, you can also have local FX sends inside groups which is extremely powerful.

The drum machine is very cool with an FX channel per pad. But using drum machine software also works very nicely. E.g. triaz

Definitely worth trialling it.

The CB14 drum machine has individual out per pad as well. Once assigned, it will have a track in the cubase mixer. There you can use whatever plugin you want, in addition to the built in fx of the drum machine. I use that feature also with halion and groove agent. With the latter two, I even use the same workflow in reaper or ardour, but drum machine only works in cubase.

[Trancit]

I wonder why nobody is mentioning the drum synths they offer for the new drum machine...

I am really impressed so far how good they sound... (haven´t dived in too much though)
Everything 3rd party I tried or implementations into i.e. Bitwig and Ableton are 1. very basic and/or 2. sound very artificial while the new Cubase modules sound immediately like using my favourite samples but with tons of control...
There are of course many much more advanced Kick synths... but for Hihats, Snares, Claps etc... this is by a ton the best I heard so far...

Did I got the wrong impression here??

The same goes for the new Shimmer reverb... this is easily on par with my favourite which is Valhalla Shimmer but it seems with more control...
What do you think about this???

[ralfrobert]

I wonder why nobody is mentioning the drum synths they offer for the new drum machine...

I am really impressed so far how good they sound... (haven´t dived in too much though)
Everything 3rd party I tried or implementations into i.e. Bitwig and Ableton are 1. very basic and/or 2. sound very artificial while the new Cubase modules sound immediately like using my favourite samples but with tons of control...
There are of course many much more advanced Kick synths... but for Hihats, Snares, Claps etc... this is by a ton the best I heard so far...

Did I got the wrong impression here??

The same goes for the new Shimmer reverb... this is easily on par with my favourite which is Valhalla Shimmer but it seems with more control...
What do you think about this???

I think you are right. I've switched to Cubase some weeks ago because of a lot of frustration with Studio One and like it very much so far. As I updated to V13 a week ago, I got the grace period update to version 14, and my impression is the (a) delivered quality, and (b) they delivered a lot. The drum synths are really good, and so are the new plugins (also the delay which is very usable). Cubase is an environment that is very complete and that delivers tons of funcionality out of the box, and they improved on that. I can finish 95% of my rhythm sections with GA5SE and the new drum stuff.

And: No subscription charade, no update policy which is hostile to pros or long-term users, you get something for your money. And no stability problems for me until now. Bottom line: Happy user.

[Trancit]

I think you are right. I've switched to Cubase some weeks ago because of a lot of frustration with Studio One and like it very much so far. As I updated to V13 a week ago, I got the grace period update to version 14, and my impression is the (a) delivered quality, and (b) they delivered a lot. The drum synths are really good, and so are the new plugins (also the delay which is very usable). Cubase is an environment that is very complete and that delivers tons of funcionality out of the box, and they improved on that. I can finish 95% of my rhythm sections with GA5SE and the new drum stuff.

And: No subscription charade, no update policy which is hostile to pros or long-term users, you get something for your money. And no stability problems for me until now. Bottom line: Happy user.

Thx for the infos!

[Caine123]

i sold my unused cubase license in the past, shit maybe i shouldnt have done it. but when i demoed Cubase (admittedly not long enough!) i felt the Steinberg workflow and feel i dont like much. it was v11 or 10 i think but seems since then a lot changed. im still into learning ableton and bitwig, cannot decide which more to go but maybe Cubase would be a good choice between FL Studio and ableton/bitwig... i dunno yet. at the same time i dont like their VST2 philosophy and dont want to support Steinberg.

[Serhii Kot]

As far as I can see, new drum track does not copy samples into cubase project directory. As sampler track does.

[DevonB]

November 6th when they announced 14, I applied the code to my account, and was in the grace period and got 14 for free.

That actually has nothing to do with the grace period, which is only for people that have already activated their license within the time period.

If you sit on the code and don't activate it, the grace period doesnt matter at all, you technically don't have a Cubase license at that point. You get whatever version is the current one when you activate the code. If you would have done it two days before, THEN you would need the grace period to upgrade and you would have to update the license in the Manager again. Since you waited until 14 was released, the system just gives you 14.

We can be pedantic about what a grace period is (I'm not disagreeing with you on what a grace period is), but when I activated the license, the website specifically said I'm in the grace period, and activated 14 for me.

Devon

[PAK]

Having finally installed it, I think this is one of the more significant Cubase updates in a while. 12 to 13 was definitely “skippable” for many..

Something I haven’t seen mentioned, about the Modulators, is they aren’t “built in” to Cubase. They’re “VST Modulators”. They’ve created a new VST category along with Instruments and FX. This means 3rd parties should now be able to produce VST Modulator plugins too. So it's a bigger deal than might've been apparent..

[Gam456]

Something I haven’t seen mentioned, about the Modulators, is they aren’t “built in” to Cubase. They’re “VST Modulators”. They’ve created a new VST category along with Instruments and FX. This means 3rd parties should now be able to produce VST Modulator plugins too. So it's a bigger deal than might've been apparent..

Not sure of what your are talking about

[zvenx]

They seem to be a plugin format.. very much like vst3 effects and instruments which probably means third parties will be able to create them and be used in Cubendo and other DAWS that support them eventually.

This to me is the clue... Where they appear and what they appear as (VST Modulators)

rsp

[Gam456]

They seem to be a plugin format.. very much like vst3 effects and instruments which probably means third parties will be able to create them and be used in Cubendo and other DAWS that support them eventually.

This to me is the clue... Where they appear and what they appear as (VST Modulators)

rsp

Interesting!
Thank You

[DaveClark]

Somewhere I read something that kind of almost explained it.. a limitation in the implementation. I'll see if I can find it.

There almost certainly are things that can be done to improve the implementation, but before reporting a "bug" or submitting a feature or feature improvement request, one should ensure that the plugin itself isn't the limitation because there will be such cases, no matter how much the implementation is improved.

I just have to chime in here. In my case, pitch modulating Legend hz with the new modulators created a quick glide, eventhough i chosed quantized modulation (like a square wave lfo). The solution was to instead modulate the amount knob in the source/destination matrix in legend hz.

If you believe that this is a case of where the implementation can be improved, you should contact Steinberg. Did you do that?

On the other hand, it's possible that the plugin itself is implemented in such a way that editing parameters by the host cannot be forced to follow all imaginable waveforms. If you believe that this might be the case, you should contact the plugin developer and let them know how you'd like the host to be allowed to edit parameters.

My initial impression is that either: 1) There is a bug in the LFO implementation in the modulator (IMO unlikely); 2) There is a big difference between the way that internal edits and external edits of parameters are implemented (IMO much more likely).

[Charlie Firpo]

Somewhere I read something that kind of almost explained it.. a limitation in the implementation. I'll see if I can find it.

There almost certainly are things that can be done to improve the implementation, but before reporting a "bug" or submitting a feature or feature improvement request, one should ensure that the plugin itself isn't the limitation because there will be such cases, no matter how much the implementation is improved.

I just have to chime in here. In my case, pitch modulating Legend hz with the new modulators created a quick glide, eventhough i chosed quantized modulation (like a square wave lfo). The solution was to instead modulate the amount knob in the source/destination matrix in legend hz.

If you believe that this is a case of where the implementation can be improved, you should contact Steinberg. Did you do that?

On the other hand, it's possible that the plugin itself is implemented in such a way that editing parameters by the host cannot be forced to follow all imaginable waveforms. If you believe that this might be the case, you should contact the plugin developer and let them know how you'd like the host to be allowed to edit parameters.

My initial impression is that either: 1) There is a bug in the LFO implementation in the modulator (IMO unlikely); 2) There is a big difference between the way that internal edits and external edits of parameters are implemented (IMO much more likely).

Yes, i've brought this up to Steinberg. The answer was that it's up to the plugin devlopers to handle the way parameters react to modulation. When i modulated the pitch on legend hz the first time, i was using "osc1 semi" as a destination. (And i got these fast zippedy/glides). Then i started to search the net and found a video by a guy that had a similar issue with serum. And that's where i got the tip to use "modulation amount knob" as a destination. Apperently the automation resolution is lower on these knobs. Better for stepped automation. But i guess this can be different from plugin to plugin.

[Danno]

I hadn’t noticed this yet. I was hoping it created a new drum sample folder within the project folder. I wonder if there’s a setting somewhere.

As far as I can see, new drum track does not copy samples into cubase project directory. As sampler track does.

[xbitz]

witchcraft incoming note velocity script ModScripter

Code: Select all

// Declare a variable to hold the current modulation value
var currentModulationValue = 0;

/**
 * processModulation: processes modulation based on input value
 *
 * @param  {number} inputValue - the normalized value of the input modulation [0..1]
 * @param  {number} numSamples - the number of samples to advance the modulation [0..]
 * @return {number} - the output modulation value [0..1]
 */
processModulation = function (inputValue, numSamples) {
    return currentModulationValue;
};

/**
 * onNoteOnEvent: process note-on function
 *
 * @param  {number} channel - the channel of the note-on [0..]
 * @param  {number} pitch - the pitch of the note [0..127]
 * @param  {number} velocity - the velocity of the note-on [0..1]
 * @param  {number} tuning - the tuning of the note-on
 * @param  {number} noteID - the unique note identifier
 * @return {void}
 */
onNoteOnEvent = function (channel, pitch, velocity, tuning, noteID) {
    // Set currentModulationValue based on note velocity
    currentModulationValue = velocity;

    // Log for debugging
    log("Note On - Pitch:", pitch, "Velocity:", velocity, "Modulation Value:", currentModulationValue);
};

/**
 * onNoteOffEvent: process note-off function
 *
 * @param  {number} channel - the channel of the note-off [0..]
 * @param  {number} pitch - the pitch of the note [0..127]
 * @param  {number} velocity - the velocity of the note-off [0..1]
 * @param  {number} tuning - the tuning of the note-off
 * @param  {number} noteID - the unique note identifier
 * @return {void}
 */
onNoteOffEvent = function (channel, pitch, velocity, tuning, noteID) {
    // Reset currentModulationValue to 0 when the note is released
    currentModulationValue = 0;

    // Log for debugging
    log("Note Off - Pitch:", pitch, "Modulation Value Reset to:", currentModulationValue);
};