Patch Point Solo? Did I miss something?

I may have missed another way to do this, but in playing with patch points I ran into this issue:

1. Create output from audio track to either an aux track or patch point.
2. New track can be armed, and echoes, and mutes inputs by default to prevent feedback.
3. With numerous audio tracks, I just want to hear the echoed aux track/patch point input track... so I solo it.
4. Now I only hear the rest of the project... both the input track and aux track/patch point track are muted.

Did I miss something handy to isolate the rest of the project if I want to listen to only this one armed and echoed aux/patch point track? (Muting all other tracks is the only way I can see to do this... very painful, and three months from now isn't going to be remembered what is feeding where.)

Another option is to use Prefader sends to the Patchpoint that won't be muted by soloing the destination track. The main disadvantage of this workaround is that you'll have to use send levels to mix those signals. But it does let you solo the Patchpoint signal without also hearing the contributing tracks, which grouping won't.

Noel Borthwick [Cakewalk]
There is no special logic for mute and solo with patchpoints at this time

This feature is really cool, but I feel this is a huge oversight.

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

OK thanks for confirming you have plans to improve this Noel! :) Your earlier quote did not sound like a definite plan, but only a possibility
 

Noel Borthwick [Cakewalk]
We may improve upon this in the future.

 
Being able to solo the patch points/aux is very important. Especially if we want to use them to replace buses.
 
 

brundlefly
Should work for audio tracks, but there will be complications if the tracks are soft synths because the MIDI will get muted. Also make sure you have the default LinkPFSendMute=0 in AUD.INI (or no entry because 0 is the default).

Ah yes, it's working for audio tracks. Thanks for pointing that out. Unfortunately, I work almost exclusively with VSTis.

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.

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 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.

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?

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?