• SONAR
  • SONAR likes to "select all" a lot now.
2017/09/08 20:51:39
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!
2017/09/08 21:00:17
gustabo
I think it's been ever since Ripple Edit arrived.
2017/09/08 21:02:47
bitman
It's new feature we're supposed to need / like so get with it.
2017/09/08 21:07:09
joakes
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!


I may be naiive here but i simply solo the track(s) i want to hear once the loop points are set.

That being said, i only use loops to set the eq on, for example, a single track (snare, or kick etc).

YMMV, but to me, no, its business as usual.

Cheers,
Jerry
2017/09/08 21:15:27
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.
2017/09/09 08:54:39
jbraner
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.



Maybe this is it - I'll need to check. I tend to choose a track, then use the timeline to set either loop points, or the part of the clip I want to edit.
(without being able to think of any more examples) it just seems to be selecting all tracks all the time - and that is never what I'm wanting to do.
 
2017/09/09 13:41:52
jbraner
OK - I see what it is...
 
I used to select a range on the timeline, with *nothing* selected - and I could then go select a track (or tracks).
Now when you select a range on the timeline, with *nothing* selected - it auotmatically selects *all* tracks (which is never what I want) ;-)
 
So, all I have to do is select a track first, and *then* select a range on the timeline - and it selects that range, for only the selected track.
 
Problem solved, by clicking in a slightly different order ;-)
 
I *knew* it wouldn't be complicated to figure this out - I just never bothered to do it!
So, now we all know ;-)
2017/09/10 22:11:30
Rob[at]Sound-Rehab
Seriously - I think selecting clips and automation is badly screwed up. SONAR keeps selecting way more than I want and makes me use undo a lot, for example automation gets deleted when I wanted to delete a clip from a take lane. I wonder why not more people have complained about this yet.

Sonar also keeps selecting way more tracks than clicked which is a major headache with quick group edits as you end up adjusting strips which you did not want to.
2017/09/10 23:11:57
kellerpj
I'm certainly glad the OP brought this to light.  This "bites me in the rear" all the time now.  I intended to post something about this myself when I had some time to investigate more thoroughly.
 
This is indeed changed functionality that I don't remember hearing or reading about.  Did I miss something?  Is this really intended or is this a "bug"?
 
Thoughts?
Paul
2017/09/11 05:41:26
Rob[at]Sound-Rehab
I started a problem report over here http://forum.cakewalk.com/FindPost/3654484 and every one of you having issues should go there and leave your comments because this thread is going to be buried soon
 
Just did another quick test and here's what makes working cumbersome:
  • As soon as you got automation and and take lanes, selecting a clip also selects the automation - which would be OK if I want to ripple edit / move stuff but much more often I just simply select clips to delete takes that are not good enough or no longer needed - in this case the automation gets also deleted BUT that applies to all other takes in that track and NOT just that single take that I deleted (!!!!)
  • It is not even consistent what is being selected (clearly a bug!) i.e. when using the smart tool to select a region containing one or several takes from 1 take lane, sometimes automation is selected alongside, sometimes not => again I don't want automation to be touched unless I ripple edit because very often I need to make subtle changes to timing by nudging clips => I don't want the automation to move in that case because that applies to the track and how it fits the song - it is not related to single clips at all (!!!!)
 
I believe that this "new selection magic" has not been properly thought about when introducing ripple edit because
  • There is no reason to do this "select all tracks" unless you are in "Ripple Edit All" mode. You are asking for way more problems compared to what we used to have in terms of selecting clips, tracks, regions, on timeline, etc
  • You could stick to the old and proven selection methods and only in case of ripple edit active AND a drag and drop move action being initiated, the "rest" (i.e. automation, other takes from take lanes, ...) should be added to the selection to be moved along - but unless both conditions are satisfied, no point for this "extra magic" that's happening now
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account