The Solo Override feature is explained in this page. It's actually a very convenient feature, but there's one thing that I don't understand. Why does disabling the global Solo button have to unsolo Solo Override-enabled tracks as well?
 
Let's say you have one or two tracks in the project that you NEVER want muted (in my case, this would be a track that contains all automation data for the same multi-timbral soft synth, since Sonar doesn't allow multiple tracks to automate the same synth, as pointed out in this request). What you do is hold down the Shift key and click the Solo button on that track (WITHOUT enabling the Exclusive Solo button on the CB) and freely solo other tracks as usual. But if you disable the global Solo button on the CB wanting to only unsolo non Solo Override-enabled tracks, it unsolos ALL soloed tracks.
 
Bakers, I need at least either of these features to be implemented to efficiently work in the mixing stage.
 
Thanks

Agreed, I would like the setting with a track to stick, if override thingy.
Maybe separate from Solo that illuminate too much - just a checkbox "Solo Exempt" like some call it.
 
When creating a bus, you pretty much know what you will use it for - and check that from start, kind of, and never have to think about it again.
 
Now there are a lot of undocumented properties of Master track to mention one - it overrides unless you start to solo and stuff.
 
I'd like to be top dog of my daw, thank you.

Sounds like a useful addition.