I contacted Steinberg support already week ago but I got no answer back, so I decided to post here.
Ever since upgrading to Cubase 15.0.20 I’ve been dealing with an bothersome malfunction involving the Write Automation for Track function on my hardware controller.
Prior to the update everything operated flawlessly as a switch — press to enable automation writing, press again to disarm. Straightforward. Now, under certain circumstances, Write mode simply refuses to disengage when I press command on my MIDI Controller. It keeps recording automation movements as if it’s stuck, despite me clearly sending the deactivation signal.
This is an obvious step backward from earlier releases — everything functioned correctly before 15.0.20.
Maybe easier to understand with video I attached, you can see it there directly.
Starting from 15.0.20 (if I recall correctly) there is a new state in the Write Automation, which is in orange color and gives feedback on whether we currently write automation, i.e. turning our knobs as you perfectly demonstrate in your video.
When in “Touch” mode, when we release the automation knob, the write automation button restores to the Red color. If you then click, it gets turned off as expected. At least so I see here. So maybe you’re turning the automation off while still we’re in the orange (now writing) state?
That being said, yeah, I agree, I would expect since we toggle the write automation, to go straight to the off state even if we’re currently in the “now-writing” state.
Thank you for the explanation m.c, this is helpful to understand the new states better.
But what I see in my case is a little different – the button does not always return to red color even when I am not touching the controller at all see 0:29 in the attached video. I assumed that when I stop moving knobs the orange state would disappear, but this is not what happens.
I am sorry but my video might be hard to understand since its on Deutsch I switched language and I mapped this Write Automation for All Tracks On/Off
And clearly shows it is simple On/Off toggle. Despite this, after I stop moving parameters the orange state stays active indefinitely – it does not go away until the next playback cycle starts or until I press the controller button two times as i did on the video.
This should not happen in my opinion, because if nothing is being moved there is no reason for the orange state to remain active. I prefer to work without mouse and keyboard as much as possible, so this new behaviour is a little confusing for my workflow.
Yes, this is what I cannot replicate here. Not in touch mode. In latch mode, it’s there, because in latch mode Cubase stays in this “now writing” state.
Here’s a video of how things work here. Whenever I stop using my controller, orange turns to red (with a very short but existing delay), and then if I send the write toggle, it gets off as expected.
Hello mc
That is indeed how it used to be before 15.0.20. It might be something wrong with Serum2.
Edit: Actually not. Can you try with Padshop assign grain pitch with the same controller?
Here when i press Write All Automation On/Off on my controler and move knob for this parameter after I release it and do not touch controller it stays orange.
Hi, there is indeed a bug with stepped (discrete) parameters, which behave as in some kind of “latch” mode, keeping the state to orange write. I’m sure it’s been reported to Steinberg, but can’t recall right now the thread originally introduced.
Hello, I use a keyboard shortcut to toggle on / off write state on selected tracks. Since ages. This new “orange” state forces me to use my shortcut twice after having modified the values… Annoying.
Gut to know, thank you mc for being able to check that out for me, I realized this with many more plugins acting the same. I had to go back to 15.0.10.
