jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
SONAR likes to "select all" a lot now.
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!
post edited by jbraner - 2017/09/11 08:43:45
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/08 21:00:17
(permalink)
I think it's been ever since Ripple Edit arrived.
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3 M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad Adam A7X - Behritone C50A PreSonus Monitor Station v2 (controlling the mons) https://www.facebook.com/groups/sonarusergroup/
|
bitman
Max Output Level: -34 dBFS
- Total Posts : 4105
- Joined: 2003/11/06 14:11:54
- Location: Keystone Colorado
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/08 21:02:47
(permalink)
It's new feature we're supposed to need / like so get with it.
|
joakes
Max Output Level: -72 dBFS
- Total Posts : 905
- Joined: 2006/12/05 15:51:24
- Location: 465 Km South West of Paris
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/08 21:07:09
(permalink)
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
Built by yours truely : I7-2600@3.4GHz, Asus P67Z68, W10x64 Creator Edition, 32GB RAM, 3 HD's, nVidia 760 GT, Focusrite 18i20 2,d Gen + Ti FW, Oxygen 61 iv Gen, and Edirol SD-20 (yes it works), CbB, Teles, Strats, LP's, Epi Riviera, etc
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/08 21:15:27
(permalink)
☄ Helpfulby Zargg 2017/09/09 11:00:12
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.
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/09 08:54:39
(permalink)
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.
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/09 13:41:52
(permalink)
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 ;-)
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/10 22:11:30
(permalink)
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.
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
kellerpj
Max Output Level: -85 dBFS
- Total Posts : 287
- Joined: 2003/12/05 00:25:05
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/10 23:11:57
(permalink)
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
"The thing about quotes from the internet is that it's hard to verify their authenticity." - Abraham Lincoln
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 05:41:26
(permalink)
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
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 05:42:30
(permalink)
@ Jon - maybe remove the [solved] again from the thread???
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 08:44:45
(permalink)
Rob[atSound-Rehab] @ Jon - maybe remove the [solved] again from the thread???
That's weird - I never put it there in the first place! Must've been the forum gremlins. I removed it...
|
kellerpj
Max Output Level: -85 dBFS
- Total Posts : 287
- Joined: 2003/12/05 00:25:05
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 12:56:27
(permalink)
I now believe this is definitely an oversight. I find if I set the selection start and stop points with the Selection Module in the Control Bar on the Time Line to select the time range, tracks don't unexpectedly get selected. However, if I use the mouse to select the time range on the Time Line, ALL tracks get selected. Very inconsistent. Previously, either way would not change the tracks that were selected (which fits my workflow much better). My opinion is that SONAR should not be making the assumption that I want to select ALL tracks if I make a selection using the mouse in the Time Line. The Time Line should be used to select time, not tracks.
"The thing about quotes from the internet is that it's hard to verify their authenticity." - Abraham Lincoln
|
slyman
Max Output Level: -87 dBFS
- Total Posts : 194
- Joined: 2015/08/31 13:55:12
- Location: Montreal, QC
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 14:52:36
(permalink)
kellerpj I now believe this is definitely an oversight. I find if I set the selection start and stop points with the Selection Module in the Control Bar on the Time Line to select the time range, tracks don't unexpectedly get selected. However, if I use the mouse to select the time range on the Time Line, ALL tracks get selected. Very inconsistent. Previously, either way would not change the tracks that were selected (which fits my workflow much better). My opinion is that SONAR should not be making the assumption that I want to select ALL tracks if I make a selection using the mouse in the Time Line. The Time Line should be used to select time, not tracks.
100% agree. Major change for long time Sonar users. I try to time select the clip itself now, but still use the timeline by habit from time to time and end up selecting and deleting data by accident. Don't really like to have to rethink my workflow, but I guess I have to move along with the software changes....
Sonar Platinum, Gigabyte H87-HD3, Intel 4770k, 16Mb Ram, Win 10 Pro, RME Babyface Pro, Roland A-Pro 800, Presonus Studio Channel, Kemper Profiling Amp, Strat/Tele/LesPaul/Taylor 214ce/Dean Cadillac/P-Bass
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 17:42:14
(permalink)
kellerpj Previously, either way would not change the tracks that were selected (which fits my workflow much better).
Exactly! My opinion is that SONAR should not be making the assumption that I want to select ALL tracks if I make a selection using the mouse in the Time Line. The Time Line should be used to select time, not tracks.
I also agree 100%
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 17:56:42
(permalink)
jbraner That's weird - I never put it there in the first place! Must've been the forum gremlins. I removed it...
I put it there after reading post #7, which appeared to indicate the original question was answered. However it seems subsequent posts have uncovered other issues, particularly the difference between using the Select box in the control module vs. selecting directly in the timeline. I suspect it may have occurred with ripple editing updates but don't know if "fallout" from implementing ripple editing, or a bug.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 17:59:44
(permalink)
Rob[atSound-Rehab] 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.
Are you sure "Select track envelopes with clips" isn't checked in the Track View options menu? If unchecked, I can move, slip-edit, delete, etc. clips in take lanes (or the parent if folded) and the automation remains intact.
|
jackson white
Max Output Level: -85 dBFS
- Total Posts : 283
- Joined: 2008/02/19 21:35:13
- Location: BOS
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 18:42:31
(permalink)
kellerpj The Time Line should be used to select time, not tracks.
Exactly. Current implementation is a rather annoying workflow speed bump.
-------------------- Some pieces of wood with wires and bits of metal stuck in them, silicon and plastic
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/11 20:51:29
(permalink)
I'm glad I brought this up - I was thinking it was just me that found it annoying... ;-)
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 04:33:14
(permalink)
Anderton
Rob[atSound-Rehab] 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.
Are you sure "Select track envelopes with clips" isn't checked in the Track View options menu? If unchecked, I can move, slip-edit, delete, etc. clips in take lanes (or the parent if folded) and the automation remains intact.
OK, learned something here because I did not know this option was there and hence has always been checked in any project I did. Still it works differently when time range selecting on take lane T1 and T2. On T1 automation does get selected, on T2 it does not. That's an inconsistency / bug. jbraner
kellerpj Previously, either way would not change the tracks that were selected (which fits my workflow much better).
Exactly!
My opinion is that SONAR should not be making the assumption that I want to select ALL tracks if I make a selection using the mouse in the Time Line. The Time Line should be used to select time, not tracks.
I also agree 100%
couldn't agree more !!!
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
lapasoa
Max Output Level: -87 dBFS
- Total Posts : 193
- Joined: 2010/07/16 11:29:58
- Location: Venice ITALY
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 07:51:36
(permalink)
Regarding this problem, Cakewalk please come back when things were simpler and smoother.
|
amiller
Max Output Level: -73 dBFS
- Total Posts : 876
- Joined: 2006/01/28 19:54:49
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 12:20:53
(permalink)
I've been seeing the same behavior (tracks being selected unintentionally). I've been so busy recording I've simply been deselecting unwanted selections and moving on. In the back of my mind I thought I was probably inadvertently making the selections...busy, busy, busy. Yes, this is new and annoying behavior.
RAWK!!! . SONAR Platinum: 2017.10 System specs: Purrrfect Audio: http://www.studiocat.com/open_cart/ • Case Silent Mid Tower • Power-Supply 600w quiet • Haswell CPU 4790k @ 4.4GHz • RAM 32GB DDR3/1600 • OS drive 1TB HD • Audio drive 2TB HD • Samples drive 1 3TB HD • Burner 24x DVD/RW • Video HD4600 • Add TI chipset Firewire For all others • Operating System Windows 10 x64 Home Edition . MOTU 828 mkII . Lucid 9624 A/D . Millennia HV-3b pre . Dual 24" Widescreen Monitors
|
bitman
Max Output Level: -34 dBFS
- Total Posts : 4105
- Joined: 2003/11/06 14:11:54
- Location: Keystone Colorado
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 13:19:10
(permalink)
When this feature came out it was presented like: "Now when clicking the time line between markers all tracks will be selected" - or some such. I thought, um.......why? Gosh I must be out of some loop somewhere. - But they can't give us a ripple edit alert? I don't know guys.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 13:49:52
(permalink)
Rob[atSound-Rehab]
Anderton Are you sure "Select track envelopes with clips" isn't checked in the Track View options menu? If unchecked, I can move, slip-edit, delete, etc. clips in take lanes (or the parent if folded) and the automation remains intact.
OK, learned something here because I did not know this option was there and hence has always been checked in any project I did. FWIW this has been in SONAR for as long as I can remember, so you've probably been removing automation along with clips for years. I think you'll find this option a very useful feature when doing future projects. I have it on a key binding, that option is currently unassigned in the default Preferences. Still it works differently when time range selecting on take lane T1 and T2. On T1 automation does get selected, on T2 it does not. That's an inconsistency / bug. Yes, but remember automation is applied to a Track, and therefore all Takes...there's no per-take automation. What I'm hearing is that you want to be able to delete one part of a Take, not delete any other parts of any other Takes, but delete the automation that applies to the track for the duration of the selected part of the Take. Yes? If so, you don't need to select the automation separately. Here's how: 1. Drag across the part of the Take you want to delete. 2. Choose Cut Special or Delete Special and check Track/Bus Automation. The selected part of the clip and the accompanying automation will be cut or deleted. As to dragging in the timeline selecting all tracks, it makes life much simpler when doing ripple edits. The tradeoff is if you want to drag in the timeline and select only part of one track, you may have to do an extra click: - If a track is already selected, you can drag in the timeline and only the timeline region will be selected in only that track. No extra click required.
- If no track is selected, when you drag in the timeline all tracks will be selected. If you click on one track to select it, the timeline region will select only that region in only that track. This requires an extra click to select the Track, but at least IMHO, that's a reasonable tradeoff for the added convenience when doing ripple editing.
|
slyman
Max Output Level: -87 dBFS
- Total Posts : 194
- Joined: 2015/08/31 13:55:12
- Location: Montreal, QC
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 14:01:32
(permalink)
Anderton
Rob[atSound-Rehab] Are you sure "Select track envelopes with clips" isn't checked in the Track View options menu? If unchecked, I can move, slip-edit, delete, etc. clips in take lanes (or the parent if folded) and the automation remains intact.
OK, learned something here because I did not know this option was there and hence has always been checked in any project I did. andertonFWIW this has been in SONAR for as long as I can remember, so you've probably been removing automation along with clips for years. I think you'll find this option a very useful feature when doing future project.
Still it works differently when time range selecting on take lane T1 and T2. On T1 automation does get selected, on T2 it does not. That's an inconsistency / bug. Yes, but remember automation is applied to a Track, and therefore all Takes...there's no per-take automation. What I'm hearing is that you want to be able to delete one part of a Take, not delete any other parts of any other Takes, but delete the automation that applies to the track for the duration of the selected part of the Take. Yes? If so, you don't need to select the automation separately. Here's how: 1. Drag across the part of the Take you want to delete. 2. Choose Cut Special or Delete Special and check Track/Bus Automation. The selected part of the clip and the accompanying automation will be cut or deleted. As to dragging in the timeline selecting all tracks, it makes life much simpler when doing ripple edits. The tradeoff is if you want to drag in the timeline and select only part of one track, you may have to do an extra click:
- If a track is already selected, you can drag in the timeline and only the timeline region will be selected in only that track. No extra click required.
- If no track is selected, when you drag in the timeline all tracks will be selected. If you click on one track to select it, the timeline region will select only that region in only that track. This requires an extra click to select the Track, but at least IMHO, that's a reasonable tradeoff for the added convenience when doing ripple editing.
I think we're drifting away from the main topic of discussion here, which is about doing a simple selection in the timeline. It should not be selecting all tracks at once, period. Never mind what happens in the take lanes or automation, as fixing the selection bug would probably cure this as well.
Sonar Platinum, Gigabyte H87-HD3, Intel 4770k, 16Mb Ram, Win 10 Pro, RME Babyface Pro, Roland A-Pro 800, Presonus Studio Channel, Kemper Profiling Amp, Strat/Tele/LesPaul/Taylor 214ce/Dean Cadillac/P-Bass
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 15:23:54
(permalink)
slyman I think we're drifting away from the main topic of discussion here, which is about doing a simple selection in the timeline. It should not be selecting all tracks at once, period. Never mind what happens in the take lanes or automation, as fixing the selection bug would probably cure this as well. Well I was trying to help the person with his issue about envelopes, and summarize a way to do what he wants. But I've thought about this some more, and I think I'm wrong in what I said above: - If no track is selected, when you drag in the timeline all tracks will be selected. If you click on one track to select it, the timeline region will select only that region in only that track. This requires an extra click to select the Track, but at least IMHO, that's a reasonable tradeoff for the added convenience when doing ripple editing.
Actually I'm not sure an extra click is involved. If there are no tracks selected, and your preferred option is that tracks remain unselected after dragging across a range in the timeline, at some point you're going to have to click on the track(s) you want affected by the range selection - otherwise what's the point in defining a range? And if dragging across the timeline selects all tracks, then you click on the track(s) you want selected if you don't want all of them selected. Please let me know if I'm missing something, but it seems like you have the same clickstream regardless of whether all tracks or no tracks are selected after dragging across the timeline: - No tracks selected after dragging across timeline - click on track(s) to select the one(s) you want affected by the range
- All tracks selected after dragging across timeline - click on track(s) to select the one(s) you want affected by the range
Yes?
|
kellerpj
Max Output Level: -85 dBFS
- Total Posts : 287
- Joined: 2003/12/05 00:25:05
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 16:19:24
(permalink)
Anderton: Your points are true. However the behavior is inconsistent with other methods of selecting time ranges using the time line. For example, if you use the Selection Control Module to select start and stop times using the time line (with no tracks selected), ALL tracks are NOT selected. The two time selections methods I typically use in my workflow are: - Selecting between two markers on the timeline
- Using the "Jog" functionality (does anyone else even use this functcionality?) and the Selection Control Module to set start and stop selection points on the time line
These two methods of using the time line to select a time span behave inconsistently now if no tracks are selected when they are invoked. Also, since I typically don't use ripple editing (in fact up until recently, nobody has), from my perspective, this seems to me like an unnecessary change to long established operational functionality. In the end, I guess I'm a curmudgeon, and am of the mindset that selecting on the time line should select time, not tracks. There are several easy ways to "select all tracks" in SONAR. If I want all tracks selected, I'll select them. Change is tough for some of us, Paul
"The thing about quotes from the internet is that it's hard to verify their authenticity." - Abraham Lincoln
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 17:11:06
(permalink)
im confused. - Select a track/multiple tracks then make selection in timeline. what's the issue ? - make a selection in the timeline/ select tracks/multiple tracks Maybe im missing something but isn't that how it should work ? EDIT: I see you want nothing selected in the timeline when you make a timeline selection. Im not sure I remember it ever working that way.
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 20:00:34
(permalink)
chuckebaby EDIT: I see you want nothing selected in the timeline when you make a timeline selection. Im not sure I remember it ever working that way.
Whether nothing is selected or all is selected, the functionality is the same...you click on the track(s) you want the region to affect.
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR likes to "select all" a lot now.
2017/09/12 20:31:28
(permalink)
I'll need to pay more attention to when it happens - but it does select "all tracks" quite a lot now. Anderton - you're probably right about the amount of mouse clicks being the same, but it's much more dangerous to have *everything* selected when you accidentally click the next thing (because you're not used to *everything* being selected - and that's the way you always used to do it...) ;-) The point it - this new behaviour just appeared a couple of months ago, and caught a lot of us by surprise.
|