I just recorded some automation data and then stopped. Once I stopped, a few lanes still show up as red, implying that it’s still recording. When I play back, those tracks don’t play the automation.
What is the issue here? How do I resolve this?
Hi,
That is a known issue, which mostly happen, if you use any DAW/MIDI controller where a MIDI loopback happens.
Out of curiosity, how long has this issue been around? For example, is it only an issue in version 13?
Been around since version 9 at least.
I believe Martin is incorrect in saying it’s caused by only by MIDI Loopback, but do us a favor and let us know what kind of external midi controllers you’re using (Lemur, Metagrid, Komplete Kontrol keyboards, etc). Genearlly, for me, the bug occurs on the second project of the day if I don’t close Cubase between projects. When this occurs, my undo and auto save also break (check that next time. If undo is greyed out, it’s broken).
Workaround is to disable and re-enable the track; this will allow automation to be read again for that track, but the only real fix once this happens is to fully close Cubase and re-open.
1 Like
Actually, I am using Loopback MIDI. Interestingly I’ve set up a game controller to send MIDI data to Cubase. Using it control CC params. Works well excluding this bug. Thanks for the workaround advice.
Hi,
How exactly is the Loopback setup, please? It’s easy to make a MIDI loop with it.
-
Max/MSP is sending MIDI data to a virtual port called GameMIDI Port. It is sending on channel 1 and it’s sending on the CC#s 14 through 21.
-
The MIDI Remote receives data from this port. It does not send data out
That’s it. I’m not sure if there’s a loop occuring.
Hi,
If Cubase doesn’t send the data out, your are right, there cannot be a loop.
happening here now too. Using loopmidi and Metagrid.