If it helps any I rolled back to 2017.05 (the earliest one I have saved)and saw the same behavior.
So we are talking about a minimum of 4 months of this being like this. just curious why its coming to a head now.
 
I respect everyone's opinion. So im not going to be that guy that says "Work a different way"
We all work in different ways so it is impossible to suggest what is good for some and what is good for others.
Im not here to dog, im here to help and if I cant help, I will politely bow out of this thread.
 
We'll see, maybe Cakewalk will take note and make a change. Either way, it really doesnt effect my way of working.
I do a lot of my selection on the clips themselves. that includes; Click+drag multiple clips, Lasso and yes, even timeline selection.
 
Hope it all works out for everyone.

chuckebaby
If it helps any I rolled back to 2017.05 (the earliest one I have saved)and saw the same behavior.
So we are talking about a minimum of 4 months of this being like this. just curious why its coming to a head now.
 

Hi Chuck,
I just "grinned and bared it" (how do you say "grin and bear it" in the past tense?) and finally posted it - just to see what anyone else said.
It seems I'm not alone though...
 
 

I respect everyone's opinion. So im not going to be that guy that says "Work a different way"

Well, I think it's clear that we will have to change a little. There are definitely far bigger things to worry about in the world - but it *is* worth mentioning.
 
We'll see if anything changes (back to how it was...)

kellerpj
Anderton:
 
I appreciate you have your preferences and workflows, but I don't use ripple editing very much in my workflows.  In fact, up until recently, nobody used ripple editing because it didn't exist.
 
Read on to see how this "functional change" to making time span selections on the time line has affected my workflows...

 
Thank you for the detailed explanation, I can definitely see how this affects your way of doing things. I don't have a solution but it seems one option that might help is to select a track, any track, and give it the focus before doing dragging in the timeline or doing a shift+click in the timeline. I realize for you that would be an unnecessary step, but it might save you more unnecessary steps.
 
TBH these changes have not affected what I need to do, and they've actually made it easier in some respects. But the way it was before was fine too, so it wouldn't matter to me if it went back to the way it was. 
 
Probably what needs to be done is to create a document that shows expected result vs. actual result for various operations, and pass that along to the Bakers. Ripple Editing was a major change, and it's very likely to have created some side effects that weren't anticipated. But if those didn't show up in the workflow of the person doing the testing, they wouldn't be noticed.

It seems that much of this boils down to the user driving the software, and not vice versa. Software shouldn't assign/change anything a user didn't specifically choose/change. In the delete hole discussions prior to Ripple Editing, that was also the rub... SONAR deselected tracks without data in them. Now, it seems it is swayed to the other extreme.
 
It can be thought of as simply as an X/Y grid... the user sets values/selections for each which does not alter the other in any way, regardless of order. When a function is called that gets an exception, a warning dialog should ensue.
 
What spins up pretty much everyone is when they take the time to make a selection, that should be how the selection persists, until changed again by the user. No one appreciates that type of surprise, especially if they find out about it 20 operations later.

*dupe*

What spins up pretty much everyone is when they take the time to make a selection, that should be how the selection persists, until changed again by the user.

Except in this case - where we select nothing, choose some measures in the timeline, and want it to continue selecting no tracks - until we tell it which ones we want ;-)
 

No one appreciates that type of surprise, especially if they find out about it 20 operations later.

Precisely...

Anderton

jbraner
I've noticed that since at least 2017.07, that whenever you do something like set loop points, or various things - that all your tracks get selected.
Anyone else notice this?
It's really annoying. If I select a track, then do something - that doesn't mean I now want to select all tracks :-\

This catches me out a lot, especially when I ctrl-drag a clip - and realise that a bunch of other ones are selected too!

If you select loop points dragging across the timeline, it selects all.
If you select loop points dragging across a track, it selects only that track.

I may not be reading correctly but this has been the way for a good while?

I checked Ipswich and if you dragged across the timeline, it selected whichever track had the focus. If a track was selected but a different track had the focus, it would still select the track with the focus. I don't think there was ever a way to drag across the timeline and not have something selected, either track or bus, but it didn't select all.
 

That's the point - it didn't select all 😉