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

[jancivil]

There's shit wrong in 12 they haven't fixed since they cropped up in 11, FFS. For example, Global Tracks inside Key Editor.
The project before this one, only a marker track showed in there; this project Tempo track & Time Signature track show, but Marker doesn't. I don't recall it ever working right. And there are things I really like which are entirely broken like they got rid of the feature but didn't tell anybody (eg. setting up a quantize window where I establish all the tuplets, no response, dead as a doorknob).
Any time I've gone to that steinberg dot net site someone tells me off if it's a rant at all; or say it's a thread with the same issue. "Start a new thread" and they've deleted my post. This is the worst forum in the world afaic.

It's been telling me the audio device was removed, and it's been very difficult wasting me half a day here and the next day. I'm using onboard audio, I don't have an interface where I am currently (med respite, not real secure). I updated the OS and reinstalled it and the first launch subsequently it's working. I'm scared to quit out of it. Other than this it's stable, but dayum. Performance is not real good here either.

[jens]

I don't think UI design is entirely subjective. It's not based on the whims of some designer (at least not in big projects like a major DAW), there's actual science involved like usability testing, heuristic evaluation, user research etc.

And? You think Thrensharo did this kind of research before making that statement or what is your point?

[concealed identity]

I think the new inspector UI is kind of a one step forward, one step back situation. I personally really like how it looks, and I think the rows of collapse-able menus look not only cleaner, but also use the space more efficiently and are easier to read at a glance. But I think the top part of it is less readable (although I'm sure this is easy to adjust to). That being said, there are bugs in the Cubase 12 inspector behavior that have been around for multiple versions, and I'm kind of peeved they aren't fixing them before moving on to the next version.

I just recently bought Cubase 12, and I don't really see much here to convince me to upgrade, personally. Cubase 12 pretty much does everything I want it to do, so I'd actually really like to see UI/workflow improvements (last touched parameter automation would be nice!), more robust Sampler Track, more intuitive audio editing and menus, native 32-bit VST and future-proof VST2 wrapper and and high-quality native plugins.

Those last few are because I recently upgraded from a 32-bit VST, and it feels like I'm now being forced to choose to lose access to my old projects or use outdated plugins and software - it's become really hard to manage for me. I imagine that's a pretty rare case these days, but still it would be nice to have a fully-featured sampler included (keep dreaming, I know), and a nice sounding simple LP/HP/BP filter, for example.

[HREQ]

Sorry but the new inspector SUCKS, it's been depersonalized, minimalized and decolorized, dark and bland and plain and flat does not = good design. I miss when things had bevels and light colors.



this looks better IMO

[EnGee]

I'm not in hurry to upgrade! So, I will wait the demo first and test it then I decide.
My priority is a better performance (especially on Windows 11). Other than that, I probably wait for C14.

[AdvancedFollower]

I don't think UI design is entirely subjective. It's not based on the whims of some designer (at least not in big projects like a major DAW), there's actual science involved like usability testing, heuristic evaluation, user research etc.

And? You think Thrensharo did this kind of research before making that statement or what is your point?

No, but I think Steinberg did this kind of research before updating the GUI. The point is that while individual preferences may vary, it's entirely possible for the GUI in the new version to be "objectively" better than the old one, because UI design isn't subjective.

[trtzbass]

From what I can see from the pics, I really like the new UI; much more streamlined and sleek. But to me the feature that screams insta buy is the option to change a track from mono to stereo with just a button. It’s the little things

[dellboy]

because UI design isn't subjective.

It must be true,because UI designers have told us its true. And unlike normal people they are entirely objective in their opinions.

[noiseboyuk]

From what I can see from the pics, I really like the new UI; much more streamlined and sleek. But to me the feature that screams insta buy is the option to change a track from mono to stereo with just a button. It’s the little things

Yup, that looks great. Tap tempo in the transport bar is another thumbs up. Maybe the windows management too in Windows - need to see that in action.

But it is JUST the little things.

(PS to all those who want a lighter interface - you can change it in preferences, right?)

[jens]

I think Steinberg did this kind of research before updating the GUI.

What makes you assume that?

[jens]

But to me the feature that screams insta buy is the option to change a track from mono to stereo with just a button. It’s the little things

I never understood what mono-tracks are for in the first place... Steinberg has them and Studio One has them because it was invented by someone who had been working on the Steinberg DAWs before, but I can't remember having come across any other DAW which has them - to me mono-tracks seem entirely pointless.

[trtzbass]

I never understood what mono-tracks are for in the first place... Steinberg has them and Studio One has them because it was invented by someone who had been working on the Steinberg DAWs before, but I can't remember having come across any other DAW which has them - to me mono-tracks seem entirely pointless.

Logic has them and Pro tools too and pretty much every major DAW.
My process is probably too long to go into here, but mono tracks are a fundamental part of my workflow and for some reason Cubase did lose the option to turn stereo tracks into mono with a single click of the mouse along the way. I’m glad it came back.

[jens]

But what is the exact advantage of mono-tracks over stereo-tracks? You can record mono-signals onto stereo-tracks, but you can't use stereo-inserts on mono-tracks.

If mono-tracka are a fundamental part of your workflow you shouldn't have much difficulties explaining in a sentence or two why that is the case.

Forgive me for saying so, but to me it seems like they either implemented mono-tracks because analog consoles have them, not realizing that they don't really make sense in a DAW or it's a concept that stems from the olden days to preserve precious processing resources, i.e. something that has become obsolete/irrelevant fiveteen years ago.

[Sahul]

Also, mono tracks had a point when using mono or stereo plugins was important CPU wise, say 10-15 years ago. Think of Waves and all that mess with separate mono, mono-stereo and stereo versions of each plugin. Also UAD and TC Powercore needed mono versions of the plugins for the same reason. And processing a stereo track with a mono plugin, at least in Cubase, resulted in only the left channel being processed, so mono tracks fitted well.

[kmonkey]

I never understood what mono-tracks are for in the first place... Steinberg has them and Studio One has them because it was invented by someone who had been working on the Steinberg DAWs before, but I can't remember having come across any other DAW which has them - to me mono-tracks seem entirely pointless.

Pointless? How are mono tracks pointless for a daw or an audio recording software? All of my drum synths have mono-outs. I prefer my drums in mono. All mics on the market are mono. In fact, most of the hardware mixers are (surprise) mono. And that is just at the top of my mind. There are dozens of scenarios where mono is used. Are you friggin serious? How is that reflection in the software environment actually a surprise for you?

Just because your DAW does not offer mono it does not mean that mono channels are pointless. Sheer nonsense coming out of this paradigm is astounding.

Before you say to me "I can load stereo mixer channel in my DAW and then load plugin and convert to mono" is exactly my point. That is pointless. Not the other way around.