Yeah, that one is a real PITA, especially since they got it working in Nuendo.

what's not working? I use touch automation with my Avid controlers and seems to work as I expect.

I tend to just do basic volume rides though so perhaps I'm not seeing the issue.


M

I think I read somewhere that "Touch" specifically acts differently in Cubase compared to Nuendo.

Well, in my book touch means automation is written whenever I TOUCH the fader to move it from the state it is in at that moment AND the fader returning to that state as soon as I let go of it. That's how it works on a desk and in pretty much all DAWs (including Nuendo) except Cubase. Sure, you can draw an automation point at the end of the track and it then works as expected, but having to do that for a high track count production really is annoying.

Yes, exactly this. One of the mods on the Steinberg forums said that this is by design (touch automation behaving differently in cubase vs nuendo), which makes absolutely no sense. It was doubly infuriating because not only are they aware of the issue and how problematic it is, but that they’re doubling down on not fixing it for some inexplicable and highly lame reason.

Edit: when confronted with the fact that the manual entry on automation clearly proves that the touch automation behaviour is wrong and a bug, the mod went further and said that “the manual is not the specification”. Astounding.

Geez. Didn't know about any details other than people have been complaining about this for almost two decades now. I learned to live with it because getting Nuendo isn't worth the price tag for features I'd probably not use - except this one!

The forum mods have nothing to do with development or fixing anything. So no they are not doubling down on not fixing it, they are just giving an opinion....not one that most people would agree makes much sense, but it's just another user opinion....not any kind of official response.

Be annoyed that developers are ignoring it. Not that mods are making poor excuses for it.

Can you elaborate on this a little bit, please?
Do you mean that when you use touch that as soon as you complete your fader move for example, that the volume level should snap back to what it was before you made the moves?

Normal "touch" operation is that touching the fader starts writing automation wherever the fader is when you touch it (and of course where you move it to), and then when you release the fader / stop touching it the fader will resume reading automation.

Imagine that you are at the end of a song and you have a long volume automation fade-out on a track and level is half-way down and you touch the fader, and then you move it around all the way up to unity gain, and then you let go - it is going to drop down to where automation (the fade) is at the time you release it. So lower than where you started.

If on the other hand the automation line was completely flat when you touched the fader then 'yes' it would return to where it was before you touched it, but it's just because that's where you already had automation.

Makes sense?

That's exactly how it should be. In Cubase, if you have no automation point after your fader move yet, the fader will just stay where it is when you release it. So you always have to draw a point after the end of the song first before touch works as expected.

mattiasnyc explained this perfectly.

Thank you for this- super helpful!

Oh, I’m plenty annoyed at SB about it. It’s just rather baffling that they would choose this hill to die on, seeing as it’s not even a contentious issue where some customers prefer it this way and some don’t. Folks unanimously hate the way touch automation works in Cubase whilst working perfectly in Nuendo. So it’s all round just a head scratcher.

Does Cubase have anything similar to Session view in Ableton ?

I’ve been using Cubase Pro 14 for a few weeks now and wow this is mature software.

It is so incredibly stable and slick.

Feels quicker on my systems than 13.

The new features and excellent and completes my personal wish list (only took Steinberg 10 years )

I’m loving the workflow and frankly I cannot imagine what 15 can bring to the table.

I’m thinking if the next stuff is AI mixing and AI composing then 14 might be my last version for a long while.

I’m very happy with where Steinberg have got Cubase too - pretty stunning software imho.

After using it a couple of weeks now, my feelings are rather mixed.

It's much faster than 12 loading and unloading sessions and oerall very stable - but on my PC it performs worse than 12 with larger projects. On our Mac Studio (fresh system reinstall) it performs better, but as 12 still crashes when closing. I'm still adjusting to the new graphics which I'll never like.

It’s a bit buggy on my new M4 Max MBP - I’ve had a few sudden total quit’s …. boom flash instantly gone!

Never ever does that on my studio PC workstation.

Running Cubase on both a new high end PC and Mac system no doubt in my mind for a moment Cubase remains a PC first app.

Logic 11 runs very well on OSX 15 M4 Max …. impressive and fun for writing sessions - Garage Band on steroid's

My feeling, too. Just had three of those quits on the Mac today. As you say, never happened to me on PC.

Hopefully this is not me setting a jinx in motion, but C14 has been exceptionally stable on my M1 Ultra Mac Studio. Don't think I've had more than a couple of crashes since picking it up on release day.

Yeah, apart from the familiar occasional crash on closing the app it has been super stable on our Mac Studio, too. That sudden quits seemed to be related to the Quantize window being open.

Just experienced a real bummer. As I work hybrid I have to do realtime bounces. And it just happened that there was an audible dropout which was let through cause it didn't register on the Asio load screen. Never had this happening with any previous version - if there was a dropout, export would stop. So this doesn't feel reliable. I noticed before that with larger projects, 12 performs better as the Asio load registers pretty constant and with 14 it's moving a lot.

This was on my home PC, on the Mac in the studio this hasn't happened so far, but as it's a more powerful machine, there's more performance headroom anyway

Open a software instrument.

Draw in a MIDI event with the pencil tool

Open the empty event with the new Score editor (Dorico tech)

Press record and start playing your keyboard to record notes onto to the stave in real time .... see how the notes appear on the stave .... for 5 seconds ....

Poof .... Cubase 14 instant quit. Gone.

16 MBP M4 Max .... OSX 15

On my Windows 11 system perfect.

Try it.

It happens every single time.

From the web

----------------------
According to the Steinberg forum, several users are reporting a significant issue with Cubase Pro 14 on macOS 15 where attempting to access the score editor often leads to an immediate crash, particularly when trying to record MIDI directly into the score window; this is widely considered a bug within the current version of the software.

----------------------

In 15 years on Windows I have never has a single Cubase bug that can cause Cubase to "vanish" .... instant quit !!

Damn, that’s not good. Lucky for me I don’t use the score editor at all, but they better release a hotfix for that ASAP.

I hope they fix the score bug issues in mac OS without having to buy cubase 15.

Currently 30% off all updates and upgrades. I’ll jump in! I’m going from 13 pro to 14 pro.

To those already on 14 - are you having fun with the new modulation features?

block blast

What version of Cubase are you using?

14.0.20.
At this point I don't think this will ever be changed, since the claim is that this is by design (although why the manual entry regarding automation is identical for Cubase and Nuendo and yet the behaviour is different and somehow still by design, boggles my mind.)

yes, I'd say modulators are one of the best new features, it's incredible and opens up many new possibilities

Nice! What do you typically (or untypically) do with it?

I want to learn it but it’s not kind of stuff I’m used to.

Can it be used on any track or group track? VST as well as audio?

yes the only limit is your imagination, for example I used it to create a dynamic chorus, where the chorus fx only comes in when I play softly on guitar, I've used it to create ducking fx too with reverb and delay as an alternative to sidechain, and don't forget it can be assigned to any parameter of a synth.