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.
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.
Hi all, I have this same thing happening in Cubase Pro 14 and it really needs to be addressed.
For me:
I do have automation on the errant track and turn off automation Read cause this track to no longer SOLO with the other track.
But the automation in the errant track has NO MUTE automation. I has only rotary speaker slow automation
It shouldn’t matter WHAT automation this track has, because none of it has anything to do with SOLO. Granted, mute is related, but it makes no sense given the following additional points.
The errant track goes SOLO when I SOLO the main track at any time (regardless of where any automation occurs on the timeline), and:
When I turn the SOLO off from the main track, it remains on for the errant track.
Last but not least: everyone here seemed satisfied (giving thanks) that turning off the automation for the errant track is the fix, but that’s not a fix at all, it’s avoidance.
It’s a work-around that means you must forget about using automation on this track. How is that an actual ‘fix’ for this issue?
Do I now have to ride the rotary speaker speed select manually during mixdown? This is a mature DAW in 2026!