Noel Borthwick [Cakewalk]
Its not an oversight. We were fully aware of this and plan to improve on it.

This is the sort of communication I like... Thanks.

joeb1cannoli
A bit of a work-around. Put all tracks and the Aux track that they are routed to in a folder. Hit the folder solo button.
I just did it on 5 backing vocal tracks sent to an Aux track. Works fine.

Nice!!  I like that.
 
 

That's a good solution - not a workaround really.
I'm not sure that auto handling of soloing of tracks feeding an aux is necessarily always what one wants. If you have tracks that send to other destinations or buses it might be unexpected if soloing one aux track magically solos all contributing sources. I think rather than auto soloing we will provide some way to quickly select all contributing tracks/buses. Then using quick grouping you can solo or mute them all in one go.
 
The folder solution sounds like the cleanest and easiest to understand. Automatic soloing or muting is always going to have cases where you don't want it. Smart solo for synths is a good example...
 

Noel, do you plan to implement nested folders somewhen? It could help a lot, if one should use folder to mute/unmute groups, it would very useful to have upper folders level to keep project more structured.

Noel Borthwick [Cakewalk]
That's a good solution - not a workaround really.
The folder solution sounds like the cleanest and easiest to understand. Automatic soloing or muting is always going to have cases where you don't want it. Smart solo for synths is a good example...

What a great opportunity to re-introduce a concept suggested in the Feature Requests forum:
http://forum.cakewalk.com/Expand-Collapse-Track-Folders-in-Console-View-m3099311.aspx
 
That said, Noel and all the baker team, I'm a huge fan of what you've accomplished in the Jamaica Plain release, and well, Sonar Platinum overall.  Just suggesting i see connection between this Folder solo concept and an improvement potentially in the Console View if that would be possible some day.

From Noel Borthwick "There is no special logic for mute and solo with patchpoints at this time, so if you want to solo just a patchpoint track you will need to manually solo all components or set up grouping of the solo buttons. We may improve upon this in the future.
Your step 4 doesnt seem right btw. If solo track that has a patchpoint input on its own you will get silence since the other sources are not soloed."
 
Hi Noel, if you look into Pro Tools there is a Solo Safe function that when set, it Solos the track that you select Solo on as well as any Aux Tracks that you set to Solo safe. Perhaps this would be a good way of implementing a solution for this problem. By the way I think it would be great in the "Borthwick" Release of Sonar! Thats a great name you have!

SONAR calls this function Solo Override, enabled by Shift-clicking Solo. But it's not restricted to Aux track groups so Solo Overriding a track protects it against being muted by soloing any track in the project which probably isn't desirable in most cases. Can PT's Solo Safe be limited to Aux tracks and their input sources?

Brundlefly, the Pro Tools "Solo Safe" can be applied to everything. It avoids the mute on this tracks whenever you hit a solo on another Track. With the Solo Override (shift+solo) function in Sonar, you have something similar. Whenever you solo something, the solo overrided tracks automatically become solo too. Hope my english was understandable...;)

Good read - I started another thread after searching for info like this.   Im wondering if other users could chime in here with specific ways that they found these new routing options to be useful - and perhaps out performed previous track/bus setups?
 
The solo thing I feel needs to be improved upon - to treat an aux track as if it were a bus at this time is simply way more cumbersome.  Also - the ability to pinpoint visually and aurally whats happening in behind the scenes routing - especially now that it CAN be way more complex - is absolutely necessary.  I think it actually may deserve its own dockable window in the skylight view?  If you can bury yourself in invisible routing... yikes....
 
Today I opened a song I tracked way back in sonar 7.  I used it as an experiment to explore these new routing options.
 
Here is something that I tried that I could not get to work.
 
the bottom snare mix had some bass drum info in it that I thought Id try to process with the internal kick mic.
 
So - I created a snare aux with both snare mics going to it via track output,  and I  created a bass drum aux for the internal kick mic, and the yet to be processed bottom snare.  
 
I then created a 2nd aux and labeled it Low Pass Snare, and created a pre fader send from the bottom snare mic to this aux.  I routed this aux's output to the Bass Drum Aux to be mixed in with the internal mic.    The Snare Aux and the BD aux were outputted to an aux titled "All Drums"   If I missed anything above here's an illustration of the routing.
 
Top Snare-------------------------------------------------
                                                                                      >Snare Aux-------
Bttm Snare ---(fx bin EQ- hi pass 900hz)--------------------
                   \
                 (pre fad send)                                                                            > ALL DRUMS AUX
                      \
Low Pass Bass Drum AUX --(FX Bin EQ-- low pass 900 hz)--
                                                                                      > BD Aux-------
Internal BD Mic ------------------------------------------
 
The first issue I ran into was I could not seem to get the bottom snare audio to appear in the Low Pass BD aux pre fx bin?  It always appeared with the high pass?   I thought pre fader meant pre fx bin?  So - I did what I always did in the past and cloned the track - deleted the aux - and used the cloned audio instead of the send.  Im cool with that - im just trying to see whats capable and see where it leads me creatively.  
 
here' s a screenshot of what I wound up with - which is pretty typical - just treating the aux as if it were a bus - the advantage being that its in the same screen not over in bus land---- however not being able to solo say - your overheads -  makes this workflow extremely cumbersome - please note the screenshot here does not illustrate the routing above
http://content.sitezoogle...3479330.jpg?1448308400
 
So - Who Else?
 

thedukewestern
The first issue I ran into was I could not seem to get the bottom snare audio to appear in the Low Pass BD aux pre fx bin?  It always appeared with the high pass?   I thought pre fader meant pre fx bin?

For reference, here's a signal flow diagram showing the Prefader send is after the FX bin:
 
http://www.cakewalk.com/Documentation?product=SONAR&language=3&help=Mixing.07.html