Encountered another longstanding issue... Any way to delete these clip residues at once?

When I record audio, I set a punch region and prepare several empty take lanes in the track and record to each lane in Overwrite mode (I'm not a fan of Comping mode). I've been recording audio heavily this way for the last several weeks and encountered an issue that already existed in Sonar 2 (which I used for many years before upgrading to X1). I must say I'm really sad to see this still present in Sonar and it's as bad as another longstanding issue I posted recently in which the right edge of a MIDI clip gets truncated when the clip is moved and the last event in the clip disappears if it's a controller event.
 
In the screenshot below, you can see there are tiny, spine-like projections on the right edge of most of the clips (I changed the Clips pane background color to white so that you can identify the projections easily). Do you know what they are? They are residues from previous, or overwritten, clips. When you repeatedly record in the same region (with or without loop enabled), you'll start seeing these residues at some point.
 

 
 
As shown in the next screenshot, I can isolate the clips from the residues by changing the clip length or moving the clips to left, then I can lasso-select the residues and delete them.
 

 
 
But changing the length of many audio clips and lasso-selecting all clip residues isn't something I want to do for the rest of my life. Is there an easy and fast way to delete all residues in a project at once? If you're someone who's been frequently recording audio in Sonar, how do you cope with this issue? Do you use the above method or just bounce the clip and the residue? Maybe you've never had this issue?

Hey Tak, I've never seen that, and can't reproduce it deliberately.  If you bounce the "residue" does it actually create a clip and/or is it audible? Or is it maybe just a video artifact?
 
If there's actually audio there, I'm wondering if might be due to some issue with sample position reported by your audio interface or some unhappy confluence of buffer size, tempo, sample rate and punch range. Do you ever select and delete clips manually when recording like that, or do you always let Overwrite take care of it?
 

Make sure you're consistent in the use of Snap to Audio Zero Crossings. I leave that option off because it has tripped me up more than once when creating loop libraries where cuts have to be exactly on the beat. When I went back to correct the cut...instant clip sliver.

Thanks all for the replies. I'm going to explain and show you that this IS a Sonar issue.
 
First, as I said, I record directly to lanes, and these clip residues appear in both the parent track and the lanes (see the screenshots).
 
 

This screenshot is from another project that shows the same issue, and I'm going to drag the left edges of the two residues.
 
 

Look! The top of the three lanes with takes now reveals two previous clips (because I dragged the edge twice), and the middle lane also shows a previous take (I have no idea what that black lines at the bottom of the clips are). And, yes, the "Record 34" clip is audible ("Record 41" and "Record 53" don't show waveforms even when I drag further for some unknown reason and are thus not audible).
 
 
There are a few things I should mention (should have mentioned in the OP...sorry):
 
1. I rarely edit clips while I record (never split, sometimes drag the clip edges to make room for next takes to record), so it's not likely an operational error.
 
2. The issue isn't easily reproducible. You need to be either a perfectionist or a poor singer/performer (or both) to make this happen (I hope I'm not the latter ). As soon as I make a mistake or feel uncomfortable about what I just played, I hit the spacebar or R to stop recording--whether it's in the middle of the punch region or after the punch end point--and then immediately hit R (again) to re-record the take. I do this quite a lot and real fast. Also, sometimes I mistakenly hit Ctrl+Z to undo although I'm recording in overwrite mode and it's not necessary at all to undo. I don't know when exactly during this operation it happens (because I'm too focused on recording), but at one point these projections appear at the right edge of the clip.
 
3. When I was using Sonar 2, I was on a different system (different PC, different OS, different audio interface, etc.), but the issue is EXACTLY the same.
 
 
What do you think? No one else has ever seen this? I'm really surprised.
I hope I'll manage to reproduce it and report to CW.
 
Thanks

Jlien X
I hit the spacebar or R to stop recording--whether it's in the middle of the punch region or after the punch end point--and then immediately hit R (again) to re-record the take.

I think this may be part of the problem if you are recording in a loop. If you stop recording "at" the end point, you may be a few samples too early relative to the end point If you resume recording, it begins from where you stopped it and records a few samples before looping back to the start point. You end up with a clip a few samples long at the end of the prior take.
 

Before you slip-edit the edges of the residual clips, what are their start and end times relative to the loop/punch end point, and how long are they in samples?
 
I just did over a hundred takes of a one-bar auto-punch with Overwrite and On Stop Rewind to Now enabled, recording to take lane two of three created in advance. I randomly stopped and restarted takes everywhere from during count-in to after the punch range and did not generate any residual clips. I did another 50+ using a fractional tempo with an un-snapped Auto-punch range that was a few ticks longer than a measure, and still haven't seen any weirdness.
 
Assuming it's not totally random, what I'm wondering what you might have been done differently to stop recording the takes that left residual clips or to start the next take that should have overwritten them.
 
The only scenario I can think of is that if you shortened the Auto-punch range somehow between takes, the next recording would not overwrite the end of the previous one. But even when I do that deliberately, shortening the punch range by one tick, the residual clip from the previous take doesn't look like what your screen shots show; mine has smooth edges at all zoom levels at which it's visible.

I had this flagged, wondered if you got anywhere with this... Cheers Alex.