Automation Gets Stuck in Write Position

I’m experiencing the bug in the latest Cubase 12 after I did a complete system reset. 100% reset, system drive cleaned out, very careful what to install, most installers downloaded freshly from the internet.

So it wasn’t some unique exotic thing on my old system apparently. Always remarkable when bugs survive a reset.
Luckily it’s rare for me… about 1-2 times a month on average haha…

Win 10 Home.
I just use a Oxygen61 keyboard (some cheap version with MK5 or MKV in the title), nothing else, except the Steinberg Ur22C audio interface. Really doubt it has anything to do with hardware.

It’s persisted here from an iMac Pro, to a Mac Mini, to a new PC Build. It’s the bug that keeps on giving. No matter where I am, it’s there waiting for me.

Also weird is how random it is. There was a time where it happened about 2-3 times every day for a few days. Then nothing for a month. Now it’s really rare, 1-2 times a month.
I didn’t change anything in my setup in that time, even the project/album was the same for the period where nothing happened and the one with daily occurrences.

It only appears to me when a session gets the fatal “an error occurred” message.

When I see this I shut down Cubase by the task manager and DO NOT save the session after the error message.

As such I hardly,if ever, get this issue,

I read in some other post in the forum that it is related to not closing Cubase/Nuendo between sessions, since I’ve been doing this I never had the problem again, it doesn’t fix it but if one can avoid it hoping that one day Steinberg will solve it…

Macbook pro m1 Max - Novation Launchkey 61, MonogramCC, Nuendo 12.0.52 (Native)

Yea indeed, I’ve also read that. It happens very rarely now for me so I’m not too concerned about it.
Maybe the reason it happens very rarely is that I always force quit Cubase when closing a project haha. Takes too long for me for it to close naturally. So I almost never go from session to session without closing Cubase.

1 Like

STILL A BUG!! AHHHHHHHHHHH!!! Damn it. Wasted soo much time.

2 Likes

Today I’ve had it again and after closing Cubase I got this screen with an extremely weird error.
aigy

I don’t know if it could be related. Just dropping the dump file anyway. Dropbox - Cubase 12.0.52.393 64bit 2023.3.24 7.21.05.316.dmp - Simplify your life

I also noticed that the issue resolved itself several times during the session. Redo came back randomly ocassionally. Not sure if the stuck automation also resolved itself. I’ll keep observing.

Hi,

Reported to Steinberg. Thank you.

1 Like

Hi,

Could you please try to add a MIDI Monitor (in the best case some MIDI Monitor out of Cubase – like MIDI Monitor on Mac or MIDI-OX on Windows)…

Please double-check if your MIDI hardware controller doesn’t send any MIDI data continuously. The position of the slider/encoder could be at some “in-between” state (between 2 values), so it could send both (or one) values continuously. Just check, if there is any MIDI traffic by any chance.

Thank you!

I installed Midi View. Not sure how/if it works but it did show some midi activity.
Those entries appeared one by one with about 5-10 seconds between each entry.
Then they stopped and never resumed for several minutes, but the automation track remained frozen.

By the way, I only use one simple midi keyboard which I disabled and unplugged. No change. No other gear, except a Babyface Pro FS Interface without any midi features being used to my knowledge.

Hi,

This SysEx message is the Identity Request (Send to Device) and the device is waiting for a response. Some of your device is asking: How are you?

It happens very frequently after importing tracks into a project.

I work on fairly large tracks with 100-200 active instrument and audio tracks and have a disabled-tracks template with about 2000 tracks.

Sometimes I update my template a lot and want to merge it with projects I started before that, so hit “remove empty tracks” so it takes out all of the empty and disabled tempate tracks and import the updated template. Fairly messy indeed.

After doing that I fairly often get this frozen automation issue. It doesn’t just affect the tracks I imported. Just as I’m typing this I have an audio track with frozen automation which was not part of the template I imported.

I’m on Cubase 12.0.70 and it just happens to me right now. Lovely. When was this reported the first time? Must be some months ago now and still no fix…

Hi,

Any hardware controller involved, please?

Not quite. I have a Streamdeck connected that actually was in standby when this glitch happened.
What got stuck in write mode was the automation lane for the track HPF-Freq. Wiggling the track’s level fader (on which automation worked fine, btw) and such things, while playing with write enable/disable made it brake free eventually. But everytime I used that specific lane, it got stuck again… Closing and reopening the session didn’t help at all.

Later on, Cubase crashed completely during an attempt to import tracks from another project. I accidently selected the very project I was working on as a source, which Cubase didn’t like at all. I’ve got a crash dump, if you’re interested…

Cubase 12.0.70.464 64bit 2024.1.11 21.21.34.335.dmp (1.6 MB)

For me, removing Komplete Kontrol from devices fixed this issue (so far).

Hello Steinberg, someone there?!

I wouldn’t call this a fix unless you bought this device with the intention to not use it with Cubug.

Actually, removing Komplete Kontrol didn’t fix the issue, now I’ve removed Mackie Control and that seems to have helped.