Hi, I have a project in which when I solo a track, another (completely unrelated) track gets solo’d, too. Even when I manually hit the S button to unsolo that errant track, it jumps right back to being solo’d.
This only happens in one particular project and is quite annoying, because it means I can’t actually, well, solo a track because that one other track will always play, too.
Any ideas as to what may be going on here?
Thanks!
That was my first guess as well, so I had checked and didn’t find anything that would connect these two tracks. This is especially puzzling because that errant track seems to be connected to everything (meaning, it gets solo’d as well, no matter which other track I solo).
But - I might not have looked hard enough, so I’ll take another look, and will report back results.
I found the problem. The track that always solos itself even when it should be quiet because I’ve soloed a different track has mute automation on it, like so:
As you can see, most of the time the track is unmuted and the mute kicks in only a few times.
When I disable this mute automation, the track solo behavior is as it should be (i.e. it stays quiet by going on mute when I solo another track).
But when the mute automation is enabled, the automation track tells the track to be unmuted, which, I guess, overrides the solo state.
That makes no sense to me from a usability perspective (even though one can make an argument that it is “technically correct behavior”), so I’m gonna call this one a bug, because when I tell Cubase to solo a track, I mean it.
thanks- just stumbled across the same problem! 
Thanks! Just ran into this issue in an old 8.5 project!
