Delete ONE track - X1 is deleting 2 or 3... WTF?

Anyone has similar situation?
 
I'm in the middle of project. I want to delete unused track. I HIGHLIGHT this track without pressing any CTRL, SHIFT or other button.
OK, now I'm deleting it (rightclick, delete track)...
 
And what I see? Sonar "additionally" deletes one or two other tracks - is it a bonus from company or what?
 
It's not a single case. This strange behaviour repeats frequently.

I have this problem as well.  There is no rhyme nor reason why it happens.  I am not a new user, been with Sonar since Sonar 1.  Basically, you highlite one track, right click, hit delete and Sonar then additionally deletes 2 tracks ABOVE or BELOW the one that you wanted to delete.  Been happening since X1 first release.

FTR- I have just installed Studio One on my dad's computer...and I can tell you this with no amount of uncertainty......IT IS NICE.  I have the entire VS700 series (audio unit and controller) and I am STILL considering the move.  Hopefully, Cakewalk will get X1b right.  Otherwise....it's "peace out" for me.  I work with a few high profile artists (rappers) in Atlanta, so my system gives Cakewalk some much needed publicity.....but lately I have had the hardest time just getting the basics done.

I love Brandon and Willy though....have to say that those guys are incredible when it comes to customer service....had to throw that in the be fair.

Having the tracks grouped or maybe even linked clips (????) might cause such, too?

HumbleNoise gives a very logical sounding explanation.

HumbleNoise


Here's what I've had happen before. If I have a couple of tracks highlighted by the little track number in the upper left hand corner, then I highlight a different track by just clicking on the track header, hit delete, they all go.

The problem here is that highlighting a track by clicking the track header (and not the track number box) does NOT deselect the other tracks that have the track number highlighted. Hope that made sense.

If you select any single track by the number, that deselects all the other tracks and ONLY that single track will be deleted.

BTW I think this is some pretty bad behavior and IMO selecting ANY track by ANY method should deselect other tracks and delete that single track.

I've never seen X1 just delete a couple extra tracks that weren't selected by some means.

makes perfect sence...when ever i delete a track i double click the track to see them all highlited then i click again to deselect all then click on the selected track to be deleted...you should try a test and watch to see if those tracks are highlighted or not when there bein deleted

Another possible point of confusion here is that if you do manage to delete too many tracks as Humblenoise describes, realize it and hit undo, all the tracks are now NOT selected. So it looks like you didn't make a mistake and X1 is just playing up.

Cheers, Peter.

adrian4u


For make it mor clear:
- I select only one track
- no groups and no the same sends on any tracks
- no "highlighting" by numbers or so
- just choosing ONE track on my PCF's SELECT button, or doing the same using mouse. 

I think that the suggestion from VROOM will ensure that this never happens again. I've always done this and never had extra tracks deleted like that. (His suggestion was -make sure you click away from everything before you select a track for deletion). Just click on an empty area in track view. Hopefully this will work for you. The good thing is that Sonar will restore the deleted tracks and their contents if you "Undo".

As Humblenoise correctly noticed, sometimes there is confusion due to the fact that Sonar has two "levels" of interfacing with tracks.

1.focus: click on a track (not its header number), the track is "focused", and changes its color (according to what's set in color preferences).
2.selected: click on a track's header number, the track is "selected" - is put on "focus" PLUS its content is selected (clips, etc etc) for the corresponding timeline selection.
A track is also selected, when you click on any part of its content (clips) BUT then it is not put on focus, and the timeline selection changes to reflect the content selection.

Now, it IS possible that maybe one track is "selected" and then another one is on "focus" and this is the part where most mistakes are made.

real life example: you edit a clip on midi track  A. Like it or not, the minute you clicked on that midi clip, its track was "selected" (header number different color). Then you click on another track (but not its header number), you right-click to delete it, and poof the midi track A whose midi clip you previously edited gets deleted too. If you had clicked the second track's header number, this wouldnt have happened.

 I recently asked why is it any better for these two levels of interfacing and apparently many users think this is better because it allows them to edit a track in piano roll (thus have it selected), while they are "focused" on another track. For me, the logical way to go about, especially now that the piano roll can reside in multidock, would be to automatically select a track as soon as you focus on it. For example, you have piano roll in multidock, click a track, the piano roll switches to that track - no double clicking. But thats just me.

PS to Adrian: actually my suggestion to avoid the situation, might be quite the opposite of what others have said, dont avoid selecting the tracks by their header numbers - on the contrary insist on selecting them that way, so that you make sure that when you select a track, that and only that is selcted. If you click anywhere on a track, you do put focus to it, it will be deleted but together with that any other track that was previously selected (header number or content-clip clicked) will be deleted too.

The simplest way is to just click on the track number on the far left (white, as default).
By doing this you deselect everything but the track you want to delete.

Clicking anywhere else on the track will select the track but won't deselect anything else.