OK, I spent most of Sunday trying to find the cause of this. I tested ram, cpu and created various Cubase templates. Although some smaller projects seemed to be better, I couldn’t completely get rid of the issue. I’m pretty sure this is a memory leak issue in Cubase because closing and restarting Cubase seems to fix the issue (on first time load only), closing and restarting every time is a PITA!
@beatpete Can you list steps to reproduce, or is it like me where every second session has the issue?
Maybe you’ve already done this before but can you list every external midi controller you’re using, as well as if LoopMidi is in the mix? I’ll do the same when I get back to my system.
GPnicolett:
Yes I use Loopbe30 to add 24 midi ports and I have Komplete Kontrol, Alphatrak, Tranzport, and 2 Generic Midi controllers.
However, On Sunday uninstalled Loppbe30 and I trashed my preferences (and made sure there weren’t any others to draw from, Cubase 12 for example) and with no controllers (except KK which, without completely uninstalling I can’t get rid of) I had the same issue. One thing I did notice is that when I created a smaller template from scratch, it would take maybe 15 to 20 sessions to happen where as a large template (like the one I use most of the time) would take from 2-4 sessions to occur. I also tested my ram, tried taking out a few cores with cpu affinity and even changed Cubase 13 priority from “high” to “realtime”, none of which made any difference. This leads me to believe it’s a memory leak in Cubase, especially with what another user said he found it happening after working on a project for a few hours. Otherwise, why would it be OK after quitting and reloading Cubase?
Martin:
Do me a favor and create a reasonably big template with say 8 vstis, 10 fx , 10 groups, and 32 audio channels with some inserts. Then, after saving, reload the session a few times and see what happens.
1 Like
I am trying to re-create this issue in Cubase 12 but am unsuccessful.
Do you have a project file you can share that I can try with? I followed your above suggestions. Created all the tracks, recorded some automation, saved it, closed it, re-opened it again. Rinse and repeat…
1 Like
Did you have several vstis and lots of groups and FX installed? Sometimes it takes a few times for it to show up.
How many are several? How many are lots?
I did this roughly.
All of this seems a little vague which is why I asked if you had a project you could share that I could try with, but I understand if that is not feasible.
1 Like
I didn’t want to share because it’s very doubtful anyone will have the same VsTi/FX as me. Anyway, here it is via Dropbox:
I use LoopMidi with the following midi ports (for an Ultraleap Controller and for Metagrid), and also have a Komplete Kontrol MK 1.
Maybe it’s that Komplete Kontrol eh? They use a custom midi driver.
Can’t imagine. I use KK as well.
What do you mean by that?
I’m finding that smaller projects work much better than large ones. In particular, my old main template had about 40 disabled vstis which made for quite a large project and hence automation issues after 2-3 project loads. Take the disabled “disabled” tracks out and it was MUCH better. Again, this seems like memory leak issue with Cubase so I did this test (just with Windows task Manager):
Some Windows 11 ram findings with 64gb ram installed
Ram on start: 36.8 gb
Ram on Cubase start: 37.4
Ram on project load: 43.4
Ram on project close: 38.6
Ram on project restart: 43.5
Ram on 2nd project close: 38.8
Ram on 3rd project restart: 43.6
Ram on 3rd project close: 38.9
Ram on 4th project restart: 43.8
Ram on 4th project close: 39.1
I’m finding that smaller projects work much better than large ones.
Are you still seeing the pattern though that when the problem does arise its the second session?
No, I can’t get it to stick even after about 12-15 loads.
Take the disabled “disabled” tracks out and it was MUCH better.
I’m trying to figure out what the difference is. Are you saying that having disabled tracks in a session might cause the issue, or is it just sheer number of tracks?
My templates are huge, with dozens of disabled tracks.
It seems the smaller the project the less issues. So, yes larger templates show the issue more than smaller ones. Again, this leads me to believe it’s a memory leak issue. Have you tried deleting all of your disabled (VST) tracks and comparing?
I think it may have something to do with lots of “disabled” tracks. My original project (the one I uploaded here) had about 30+ spitfire BBCO disabled tracks and another 10 or more disabled synth tracks. I’ve started using Vienna Ensemble Pro for the orchestral and Kontakt stuff and my projects are a lot smaller and I can’t get the automation to stick. I wonder if Cubase handles “disabled” tracks in a different way?
Unfortunately, the new 13.0.30 update made no difference to this.
Just happened to me for the first time - probably not coincidental that I’ve just incorporated a cc121 and StreamDeck (using a LoopMidi virtual port) into my setup. This happens for me on a tiny project with no disabled tracks. Can’t reproduce it reliably, it just happens every now and again. Disabling and enabling the track does get it out of that state, but then it’ll happen every single time until Nuendo is completely restarted.
The best workaround I can see is to move to another DAW and don’t give Steinberg anymore money until they address the plethora of bugs that have been reported on this forum for well over a decade.
It happened to me for the first time.
I don’t save, I turn off Cubase to avoid bugs to be written on my session.
I looked into leaving Cubase, sadly, it’s impossible for me.
Hi,
Any new hardware DAW controller, please?