Mute/Solo weirdness

Haven't tried this in Foxboro, and I've only seen it a couple of times (intermittent):
If I have multiple Lanes, one of which is Solo'd, rendering the remaining Lanes Muted, if I delete all but one of them, including deleting the Solo'd Lane, I've seen a couple of cases where you couldn't un-mute the remaining muted track. Have not been able to dupe every time. 
 

I can't reproduce it in Foxboro (tried only in one existing project). Whether the soloed lane is at the top or bottom or somewhere in the middle, deleting lanes including the soloed lane always automatically unmutes all muted lanes (I don't know how to delete multiple lanes at once, so I deleted them one by one). I'll be happy to test it if precise steps using the Normal project template are provided. 

Confirmed. If after comping the takes by Flatten Comp, however, deleting the auto-soloed Comp lane automatically unmutes all muted lanes wherever the Comp lane is positioned.

we'll check it out, thanks.

I'm quite surprised that this minor issue which has a 1-second workaround got the Baker's attention.
 
IMO an issue like CWBRN-24086 should be given higher priority. You might think it too has an easy workaround, but that's just a quick example to demonstrate/prove the bug. The real issue is that you can't drag clips in one track's lanes 1/2/3/4/5 to another track's lanes 6/7/8/9/10, for example. The clips dragged land on wrong tracks, some of them often overlapped. So I have to drag them one by one. I've been waiting MORE THAN A YEAR for the bug to be fixed. There are also other issues of the same impact and wait length. What did I submit those reports for?

The issues sent through problem reporter do go into our bug tracking system and those are evaluated when we budget our time across fixes/features/maintenance/optimizing/etc.  No, we don't put them there to be forgotten about.  Not everything is immediately actionable.
Sometimes a developer will pick off something because it's a stupid/easy bug.  Other cases could require changing how a subsystem works (I think of Apple's sandbox issues that have been in the news).  
 
So good news is that the iteration cycles are shorter so we are able to respond more quickly.  
 
Keith
 
 

@icontakt I suggest you write on that thread the latest version of Sonar you can reproduce the issue on, then get a host to move it into these forums.

icontakt
Well, I trust Keith's words that the iteration cycles are now shorter and all the bugs logged in their tracking system are evaluated equally (whether they are posted in this forum section or not).
 
So, I'll wait a few months before deciding if I should bump those threads. Like you I'm expecting the Bakers to start fixing more issues in the core features (mainly Take lanes, as you know), since Drum Replacer was released and no next big item hast been announced (I hope the new start page won't take too much time and too many resources).

Yup we all put in enough work into documenting a repro'ing those issues didn't we?
I'd definitely get those threads moved into these forums though, that's not bumping them, that's moving them, and stating that they are not working on the latest version of Platinum is useful information to know for the developers..

2 weeks old with no CWBRN.  closing the thread.
 
if someone wants to bring the problem up again, start a new thread, create a problem report and put the CWBRN in the title.
 
http://www.cakewalk.com/Support/ProblemReporter/