I am used to clicking on the solo button on a track to, well, solo that track to listen to it in isolation, and then clicking solo again to then hear it in context of the full arrangement.
That usually works, but not in this case:
Here, I have a project with a couple of synth (VST instrument) tracks (they happen to be frozen but that doesn’t make a difference). A few of those tracks have mute automation:
When I solo the first track (that does not have mute automation), it will then also solo the two following tracks (that happen to have mute automation) - but I wanted to solo just the first track that I clicked solo on!
To make matters worse, when I click on the solo button on the first track again (to un-solo it), it then mutes(?!) that track, and leaves the other two tracks that Cubase decided to solo (without me touching the solo button on them) on solo:
What a mess!
The only way to get out of this is to click the global solo button, which will allow me to clear all these various unwanted mute and solo states and get back to a sane place.
It’s curious that this happens only with tracks that have mute automation on them, so it must somehow be related to that.
Is this somehow “as designed” behavior and I just don’t understand why it’s acting like this (in which case I would love an explanation), or is this simply a bug?