Problem with Submix...

[Robert Randolph]

From the basic philosophy, to me the submix paradigm has very very low priority. Same opinion here like AGreen.
Though I may have 80 tracks or something, I use a track as a bus of ten others, and this is my submix anyway, and I can group all of that into a folder. The bus may be inside or outside below, and I may have an empty 0dB dummy track for the folder.

I create a drum bus directly below my drum tracks, and assign the red color to all bus tracks of that kind. So far, easy to scroll.

The point might be, that macros and modifiers in the UI (parameter listings...) get organized in a way they reflect folder and nested bus structure.

It may be that quite a number of experienced and highly professional folks prefer to use a paradigm known from the more expensive DAWs.

Even with your setup, once you have nested busses, things go awry with solo-isolate.

The same situation occurs once again... You can't easily solo tracks in children of submix children.

[dRowAudio]

Ok, I've spent a long time on this trying to figure out what the problem originally was. The issue seems to be that it was difficult to determine why a track should be 'audible' (we term tracks that need to effectively solo but without having the solo button pressed 'indirect solo', this is shown by a flashing solo light).

The trouble is that setting solo for a folder/submix track also needs to indirectly solo the children. This was resulting in a circular loop that made it impossible to only solo a single track within a submix. (If you follow the logic, the sub-track is soloed because the submix track is soloed which in turn is soloed because the sub-track is soloed etc.).

I've now reworked this logic so that the following invariants should hold:
• Tracks should be indirectly soloed if any parent track is soloed (this should have the effect of cascading up multi-nested folders/submixes)
• Tracks should be indirectly solo isolate if any parent track is solo isolate
• Folder/submix tracks should be indirectly solo isolate if any sub-track is solo isolate
• If a track is solo isolate, it acts as-if soloed if any other track is soloed, normal otherwise
• Muting a track excludes it from the mix no matter what solo state is set
• Soloing a folder/submix track should indirectly solo all sub-tracks
• Solo isolating a folder/submix track should indirectly solo isolate all sub-tracks
• Directly soloed/isolated tracks should appear solid
• Indirectly solo/isolated tracks should flash
• Non-audible tracks should appear crossed-out

I'm preparing a new build now (v9.0.39). Please check that the above logic is sound and behaves accordingly.
Thanks everyone!

[Trancit]

I am sorry, if this causes trouble for you, but this is now as it should be ... otherwise the Submix would really make no sense as it would be better to use tracks as busses and foldertracks...

But anyway, thx very much for your effort ...

[Kang]

I'm really curious if this has been improved on since this thread?

I noticed that you can solo in submixes just fine as long as it's going to the default output.

If you have the submix being sent to another track, then it's still "broken". Unfortunately that's the case for me 100% of the time.

There's no mention of this routing caveat in this thread though. Makes me think it was fixed, but perhaps this was just overlooked? Maybe it's a side effect of the way things work? I dunno, but it would great to be able to properly solo in submixes that are being routed to a different track. Anyone got any insight on this?