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

[Synthman2000]

And there was me thinking Cubase was an incredible drum sequencer in itself, and then some.

The Drum Editor is cool, but there are dedicated vsts that offer more features (IIRC), including:
- probability
- reverse direction (and even random)
- an easier way to add rolls
- lanes with variable length

Not to mention things like Euclidean rhythm generation.

It is difficult to imagine these things are not possible in Cubase, I use Key editor in Cubase for all drums, always have done. I program drums with a sampler, Battery, MIDI or Audio. No need for drum editor or any third party sequencer.

But I am programming basic drums which is hard enough for me to get sounding exceptionally good in terms of a great groove, but I do get there.

If extra complexity is part of your workflow to get the completed albums racked and stacked then that's perfect for you. If very good sounding end results are completed, that's great

[mothra]

Cubase SX (2002) was a total rewrite, and didn't support the old project files (*.all) that went back to 1990.

But, SX up to v3 (I think) can still open and convert .all files to the new format..

[macmuse]

Cubase SX (2002) was a total rewrite, and didn't support the old project files (*.all) that went back to 1990.

But, SX up to v3 (I think) can still open and convert .all files to the new format..

I remember there was a break off point somewhere. I had owned Cubase in the 90s, I think before SX. Now I own Cubase Pro 10 through 12 which cannot open that early stuff (but that’s OK because that small amount of stuff wasn’t anything I’m looking to open these days anyway).

[mothra]

I remember there was a break off point somewhere. I had owned Cubase in the 90s, I think before SX. Now I own Cubase Pro 10 through 12 which cannot open that early stuff (but that’s OK because that small amount of stuff wasn’t anything I’m looking to open these days anyway).

I had to double check the one I saved, its SX3. If you own 10/11, you can open it with your elicenser just fine, as long as SX 3 will work on the system heh. I ran across a couple threads on it when I found a bunch of my old .all files. Grabbed the installer when I found out I could open it with my 11 license, but didn't feel like breaking out the G5 just to open some 20-23 year old file that's probably full of midi tracks for gear and VST instruments that don't exist anymore.

[AdvancedFollower]

It is difficult to imagine these things are not possible in Cubase, I use Key editor in Cubase for all drums, always have done. I program drums with a sampler, Battery, MIDI or Audio. No need for drum editor or any third party sequencer.

I prefer the Drum Editor because it can automatically import the drum names from the VST. It's much easier to work when the kick is called "Kick" and not "C#3" or whatever.

Unfortunately only a minuscule number of drum VST's actually support this feature, even though it doesn't seem to be Cubase-exclusive. Studio One and FL Studio also do this with supported VST's and their built-in drum machines.

[cptgone]

Cubase SX (2002) was a total rewrite, and didn't support the old project files (*.all) that went back to 1990.

But, SX up to v3 (I think) can still open and convert .all files to the new format..

Thanks for correcting me

[egbert]

I think these leaks are intentional, and that the companies know exactly what they're doing. It happens so regularly that it can't be coincidence.

The curse of the conspiracy theory strikes again. What on earth would the motive be for them to leak something in such an awkward and irritating way?

Remember this as a guide to life - conspiracies are hard. Incompetence is easy. Whatever looks like the former is almost invariably the latter.

One of the guys in a local music store in the computers/music area - a keyboard player and session guy, this was his day gig - met old Charlie Steinberg on a business trip to Germany in the 90s and got it straight from the source that Steinberg leaked the crack of Cubase on Atari. That crack was used pretty much everywhere despite some bugs and familiarised a generation of sequencer users with the Cubase interface and workflow and contributed to Steinberg's success in the sequencer market going forward to the Mac and PC versions. This leak was presented to my local guy as a genius marketing move. So, conspiracy theory? Maybe not.

[cptgone]

And there was me thinking Cubase was an incredible drum sequencer in itself, and then some.

The Drum Editor is cool, but there are dedicated vsts that offer more features (IIRC), including:
- probability
- reverse direction (and even random)
- an easier way to add rolls
- lanes with variable length

Not to mention things like Euclidean rhythm generation.

It is difficult to imagine these things are not possible in Cubase, I use Key editor in Cubase for all drums, always have done. I program drums with a sampler, Battery, MIDI or Audio. No need for drum editor or any third party sequencer.

I hope I'm mistaken, but IIRC Cubase's Key/Drum/Score editor doesn't have such features.

And it's not just about features.
Cubase is mostly focused on a linear paradigm, step sequencers typically aren't.
Both paradigms have advantages of their own.

Bitwig tries to offer both; I'm not knowledgeable/experienced enough to judge how well that works.
Steinberg might choose to do the same, preferably in a way that doesn't cause disconvenience/confusion to people who prefer linear sequencing (Steinberg does seem to be running out of major new features to entice people to upgrade to new versions of Cubase, so I wouldn't be surprised if they would consider this, one day).

2 examples of advantages of the pattern-based sequencing paradigm:
- BFD3 allows for probability-based chaining of patterns, which is nice if you like your sequencer to be less predictable.
- Patterns can be triggered over MIDI (which can be useful live, and allows for a more playful way of composing).

[Syngularity]

Bravo! I agree, and I think, with view at modern production workflows: Steinberg should finally wake up in the 21st Century.

[jancivil]

The drum editor is not required to import names of kit pieces from eg., BFD. I've done this for years and years. Until recently, in order to save a drum map for use out of this required it to be opened as an Instrument Track but now, since 11 or 12 it works for regular MIDI tracks. It's a simple right-click move. I haven't looked at it in a long time but my recollection is that in Drum Editor this could be automatic. I'm sure I began to adopt that; but the granular way I work with time means dragging Key Editor’s note bars [as opposed to the diamond shapes in D.E.] - as well as other features - is the thing.

[jancivil]

As long as we're bringing in personal aesthetics as though a type of metric...

When I see "Euclidean rhythm" as something deemed necessary or that, I find irony; as "discovered" by Toussaint the idea is the algorithm "generates traditional rhythms" (the verbatim phrase in the title of his seminal 2005 paper). the wheel constantly needs reinvention, isn't it.

Per '[that doesn't] cause confusion in people who prefer linear sequencing':
It's always struck me that the advantages of pattern-centric - or prefabrication - modes of operation appeal primarily to people that approach all this from a very different place than people who can generate and readily execute ideas in real time.

I remember fairly early in my adoption of the piano roll way of life trying out (Cubase's) groove template feature. I figured it might save time over all the iterations (NB: def. repetitive motif) of the 4 bars I was looking at executing over 3 minutes or that. Soon I realized that a single groove or a couple of them as overarching isn't real, that what I would do warts 'n all was, in being more dynamic and elastic, showed that feel is felt, & programmatic "production workflow" pales in comparison.

[cptgone]

As long as we're bringing in personal aesthetics as though a type of metric...

Linear/pattern-based paradigm, workflow, routing, well designed implementations of features like Freeze and Key Editor... those are the things I talked about, and none of those is a matter of aesthetics.

When I see "Euclidean rhythm" as something deemed necessary

I mentioned that because someone wondered why anyone would use a dedicated vst, instead of Cubase's Drum Editor (seemingly implying that tool has every feature anyone could wish for).

I never said it was "necessary".

It is, however, an alternative to traditional step sequencing.

[skijumptoes]

https://forums.steinberg.net/t/temporar ... ops/870628

Looks like the delay may have been caused by the Steinberg shop operator going into insolvency. Not good news.

Little bit of a backstory has come up on asknet too:
https://www.ftc.gov/news-events/news/pr ... t-scammers

[AdvancedFollower]

https://forums.steinberg.net/t/temporar ... ops/870628

Looks like the delay may have been caused by the Steinberg shop operator going into insolvency. Not good news.

Little bit of a backstory has come up on asknet too:
https://www.ftc.gov/news-events/news/pr ... t-scammers

That's pretty bad but hopefully it should not affect Steinberg/Yamaha too much. I'm sure there are other operators who'd be happy to take over. Hopefully they didn't have too many outstanding payments due to Steinberg. An example of why choosing the lowest bidder isn't always the cheapest option in the long run.

[Scotty]

Although pattern based composition and tools can lead to repetitive results it doesn’t have to be that way. There are people who are not conventional musicians who are very skilled programmers with great ears and imagination. There is more than one way to express musicality, I am sure you’d agree.

I remember fairly early in my adoption of the piano roll way of life trying out (Cubase's) groove template feature. I figured it might save time over all the iterations (NB: def. repetitive motif) of the 4 bars I was looking at executing over 3 minutes or that. Soon I realized that a single groove or a couple of them as overarching isn't real, that what I would do warts 'n all was, in being more dynamic and elastic, showed that feel is felt, & programmatic "production workflow" pales in comparison.