orchetect:
Larioso:
lukasbrooklyn:
Re disabling (the ‘disable track’ function to be precise): this only works fo audio tracks for me, not instruments, groups, fx. Is Elements actually more featured in this regard?
You are right - thanks for noticing.
“For audio tracks, the track context menu contains an item named “Disable Track””
I read too much into this when I read it. Sloppy reading…
Maybe you can make a freeze of synths, just have midi on to create some audio.
Checked - it works. When you unfreeze it loads the full lot.
I’ve put in a request a while back to enable Freeze on Instrument Tracks without any MIDI for this exact purpose but I think it fell on deaf ears. (Why for the life of me you can’t freeze an empty instrument track, I don’t know. It seems obvious in this context that it would be a great feature.)
But - all you have to do is create an empty MIDI region on the track and boom, Freeze works. The issue with that is that it creates a bunch of empty freeze .wav files on disk. Which is annoying and accumulate quickly if you have hundreds or thousands of session files (ie: one session per cue, like I usually do). I don’t always want to delete the frozen tracks because I might need them later and it’s hand to just have them already in the session with their Reverb send routing etc.
You also have to remember to port these freeze files around with your sessions. If you forget the freeze files, oops - all the instruments load up into RAM instead of staying frozen, defeating the purpose.
Another issue is - you can’t delete frozen tracks. You have to unfreeze them one at a time, wait for the instrument to load, then delete them. So if you have a template with 50 frozen instruments and you only use a few, look forward to a lot of tedious unfreezing to remove the unused instruments.
I also discovered if you create a template file with frozen tracks, then use Cubase’s New Project from template, it unfreezes the frozen tracks when you create a new project feeding you the error that the “cache file for can’t be found.”
i reckon a more systemic approach would be to simply implement and allow for disabling any track type. (yes this would get tricky when for instance disabling a midi track routed to an instrument track; ie. does it disable the instrument itself as well? and so forth… but it’s a needed feature i think.)