• SONAR
  • Something has to be done about Delete Track function (p.3)
2016/11/02 11:41:25
icontakt
vladasyn
Some time I want to delete one SELECTED track and it would say, "Delete 3 tracks?" I would say NO and go look for what ever else was selected. But this time it said, "Delete track?"- it definitely did NOT say "Delete 2 tracks?", I know because I paid attention to it. So I said Yes and it deleted a MIDI track, but then the guitar track disappeared.

 
Maybe this is what you did?
 

 
I think the second right-click menu that I opened in the empty space below the tracks should also say "Delete 3 Tracks," instead of just "Delete Track."
I too have mistakenly deleted unintended tracks in the past because of this.
2016/11/02 12:24:46
mettelus
Didn't read this entire thread, but like it or not, get into the habit of making selection, then doing operations... always.

This applies to any program, so is a habit all users need to adopt, or they will suffer from it.
2016/11/02 12:46:41
Sanderxpander
Great vid, icontakt.
And yes, vladasyn, this has happened to me too in the past and is a pet peeve of mine. The CTRL+SHIFT+A shortcut is a good way to avoid it but I agree that I would welcome additional "ergonomics" on Sonar's part here. For me, the issue is that when I'm right-clicking something, I'm assuming I'm selecting it. Why would I right-click it otherwise? Sonar doesn't agree - right-clicking opens the context menu but it has no bearing on the selection you may or may not have already made.
2016/11/02 13:00:25
SquireBum
icontakt
 
I think the second right-click menu that I opened in the empty space below the tracks should also say "Delete 3 Tracks," instead of just "Delete Track."
I too have mistakenly deleted unintended tracks in the past because of this.




@icontakt,
  Great catch on the behavior of the Track context menu!   Agree 100% that the "empty space" Track context menu should display the track count or provide a secondary confirmation dialog.
 
-- Ron
2016/11/02 13:09:47
Beepster
There used to be a serious "Selection" bug in X1/X2 and I think it may still exist to a lesser extent but I don't run into it anymore.
 
Essentially you just could not rely on accurate selections at ALL. I studied this behavior and posted threads about back in the day but it was a nightmare.
 
The solution was to simply use the "Clip Lock (Data/Pos)" on EVERYTHING I wasn't currently editing. PITA but it got me through. Anyone experiencing this issue regularly should get into the habit of locking all clips (both Data and Pos paramaters) unless they plan on editing them.
 
I really haven't had to worry about that crap for years now (X3 seemed to squash that "bug").
2016/11/02 13:47:23
stratman70
Well the ONLY way I can make this delete error is if I select or activate a track and then right click in the project and INSERT track(s). In this case yes the track I selected first is "still selected" so If I delete one they are both deleted. 
 
But I never would do that. But I guess that"s just because of the way I work. For 20+ years. 
I never have run into a delete track issue. Just lucky I guess?
 
2016/11/02 13:54:04
stratman70
mettelus
Didn't read this entire thread, but like it or not, get into the habit of making selection, then doing operations... always.

This applies to any program, so is a habit all users need to adopt, or they will suffer from it.



Guess that is what I have been doing for all these years. 
2016/11/02 14:07:48
brundlefly
vladasyn
In older Sonar versions, the selected track was also turning different color (light gray)- this was very helpful to know for sure what track is selected. Now the only thing changes is the track name background color.

 
Use the Mercury theme (or any modification of it that doesn't change track header background), and uncheck "Show strip colors" in Preferences > Customization > Colors.
 
I don't know when the blue squares on track number was added to Sonar. I have to check older Sonar releases. I only care about track name background turning blue- this is old Sonar way to select track. This is what I am used to.

 
Track number selection and highlighting have been around since the early days of Cakewalk before SONAR or even Pro Audio. The highlight was originally yellow, and the function was called "Sticky Selection" because it allowed you to leave a track(s) selected while moving focus to another track. So far as I know, nothing has changed significantly in the way this works for years.
 
In any case, it is definitely possible to have the context menu show 'Delete Track' when one track is selected, and another is focused, even when using the context menu associated with one of the tracks, not just when right-clicking the empty area as Tak demonstrated. This issue goes back a while.
 
One way:
- Ctrl+Shift+A to de-select all.
- Select a clip in the currently focused track (track number highlights).
- Click the header of another track to move focus there without changing selection.
- Right-click in the header of either the focused or selected track.
- Choose 'Delete Track', and they'll both be gone.
 
+1 to always using Ctrl+Shift+A before selecting anything to be deleted.
2016/11/02 14:11:40
stratman70
@Tak T
Never mind, nice video.........
2016/11/02 18:23:53
soens
+1 for Save As New Copy then close and reopen previous one after realizing a mistake was made.
 
someone did mention that, right?
 
But as was mentioned, deleting tracks does not delete the audio still residing in the Audio folder. Find it and reinsert it in the project.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account