Anyone find mute/solo states aren't functioning the way you expect them to when folders involved?

[awesomeaudio]

edit

Here is a better diagram of one of the problems in this thread:

I suppose if we were to give the problem a name, it would be “Reverse Solo Forwarding Beyond 1 or 2 levels”

(edit: video 3 might be the more important video)

Anyone know what the key is to this? They seem like they can stuck depending on your previous solo/mute state.

In this case, I have a Lead Vocal track, Sent to an FX split Group with forwarded Sends to the FX channels and then those FX channels Output to a Sub Group and then that Sub-Group output to a Main Group.

Is it that Cubase mute/state forwarding only go so many levels deep?

In the above video you can see the final FX group will unmute one section, but not the other.

edit

Okay, I think it’s because the particular folder was already muted before I continued modifying mute/solo states of other tracks.

I think there needs to be a UI indication and method of negation when a track is in a mute-“locked” state - perhaps blinking or something.

edit

Here’s another example of another situation.

Vocal Audio Track → Output → Vocal Post-Processing group.

Solo an FX track which solos the Vocal Audio Track, but not The Vocal Post-Processing Group. ie, there is no solo forwarding. I even tried Linking the Audio Track and Group Track solo/mute states which didn’t work.

but then on the inverse, solo’ing the Vocal Post-Process group will solo everything, even though the group has no sends coming from it (the sends are coming from the vocal audio):

I might just have to do some reconfiguring of my which track my sends are coming from.

edit

please also see: Solo Exclude Sends Modifier - Cubase - Steinberg Forums