Updated to Kingston.  When I'm comping and splitting audio clips, I seem to be getting very small slices of clip at the joints. Not on all splits but enough to make comping a real pain.  When I try to grab a clip end to drag it, I'll get the tiny clip sliver instead of the clip I want.  It makes everything a mess.
 
Some of these tiny clip slivers you can see, others are so small that you have to zoom way in and drag the edge to find it.  I know they are there because when I "delete empty lanes", the lanes don't delete!. Is this a known Kingston issue or am I doing something wrong? I have zero crossings shut off.  I've now rolled back to JP.
 
This issue was split from a previous post, (that is now locked).  There were several other folks who have had this problem.  Their posts can be see here:  http://forum.cakewalk.com/FindPost/3330625
 
Has anyone else seen this one?  Any suggestions, help or ideas are welcome.  Thank you.

Well, since this is a new thread I can only repeat what I said in the other thread:
I have this and I still use Hopkinton.
 
It starts to happen sometimes, but I don't know what triggers it.
I have begun using Auto crossfade so probably that is why I only notice it now.
Normally there is no reason to overlap clips, but with Auto crossfade you do it a lot.

jpetersen
Well, since this is a new thread I can only repeat what I said in the other thread:
I have this and I still use Hopkinton.

It starts to happen sometimes, but I don't know what triggers it.
I have begun using Auto crossfade so probably that is why I only notice it now.
Normally there is no reason to overlap clips, but with Auto crossfade you do it a lot.

Interesting.  Next time I'm comping I'll disengage 'Auto Crossfade' and see what happens.
 
Thanks Jan.
 

Didn't someone (perhaps even a Baker) say in another thread this issue was occurring in some of the previous versions as well?
 
Also I've had "sliver" issues since X2 but they were due to some other wackiness/poor editing technique.
 
It almost sounds like these new reports might be being caused by the splits being double triggered and just the natural finite mouse/cursor movement is occuring in between the first and second split/comp tool action.
 
I wonder if those experiencing this can check their Edit History and see if maybe two splits occurred when these slivers get created. That would almost semi confirm that theory.
 
However I have no freaking clue and am STILL on Foxboro (just been too busy/preoccupied to update).
 
Just some thoughts but would like to know what's up/what to expect.
 
Cheers.
 
Edit: ah yeah... I recall reading about the X-Fade factor. That kind of goes against my theory BUT might still be worth checking the edit history to see if that reveals any clues.
 
Like do whatever it is that's causing the slivers, make sure the sliver has presented itself, then check your History.

Beepster
Didn't someone (perhaps even a Baker) say in another thread this issue was occurring in some of the previous versions as well?
 
Also I've had "sliver" issues since X2 but they were due to some other wackiness/poor editing technique.
 
It almost sounds like these new reports might be being caused by the splits being double triggered and just the natural finite mouse/cursor movement is occuring in between the first and second split/comp tool action.
 
I wonder if those experiencing this can check their Edit History and see if maybe two splits occurred when these slivers get created. That would almost semi confirm that theory.
 
However I have no freaking clue and am STILL on Foxboro (just been too busy/preoccupied to update).
 
Just some thoughts but would like to know what's up/what to expect.
 
Cheers.
 
Edit: ah yeah... I recall reading about the X-Fade factor. That kind of goes against my theory BUT might still be worth checking the edit history to see if that reveals any clues.
 
Like do whatever it is that's causing the slivers, make sure the sliver has presented itself, then check your History.

Thanks Beep.  I'll check that out.  When I'm comping I am moving pretty fast so you might well be onto something here.
 
Paul

I have these issues too, in every version of Platinum so far. Auto-crossfade is disabled, but have had the same results when enabled. I think it may have to do with the comping feature. I've noticed that some clips/lanes will become disjoined from the split-point that is the same across all lanes even though they're all in the exact same place. This can be from manually editing one clip separately... even in an entirely different location or applying a separate fade. This is typically when I'm seeing the sliver waves. One has to be extremely diligent and double check every point when editing in Sonar, as things can go very wrong, especially when working across multi-tracked grouped clips.
 
Although a bit unrelated, I've had a problem with multi-tracked grouped clips and all layers in any track not following the rest of the group if the track layer view isn't selected for that particular track. Another error, is when selecting multiple grouped clips and splitting them, instead of each group maintaining itself and creating new separate new groups before and after the split point (as it did in previous versions of Sonar), each clip selected (every separate group/take) before and after the split point becomes all one group. Oops... fail. Overall, I really like the potential of the new comping system, but it has many quirks that can be a huge waist of time and very frustrating to work with...

theheliosequence
Although a bit unrelated, I've had a problem with multi-tracked grouped clips and all layers in any track not following the rest of the group if the track layer view isn't selected for that particular track. Another error, is when selecting multiple grouped clips and splitting them, instead of each group maintaining itself and creating new separate new groups before and after the split point (as it did in previous versions of Sonar), each clip selected (every separate group/take) before and after the split point becomes all one group. Oops... fail. Overall, I really like the potential of the new comping system, but it has many quirks that can be a huge waist of time and very frustrating to work with...

Just checking: When you say multi-tracked and multiple grouped clips, are you talking about take lanes?

I have seen this as well. Are you editing the active main track or one of the take lanes?
I thought it happened to me when I edited the "main" track.

i've had clip slivers for years now, since at least X2.  also sometimes when clips overlap, part of one clip will become permamently attached to the other one if i try to re-separate the two overlapped clips, which is weird & annoying

Yes, I seem to remember slivers appearing during an album project I did with X3.
I think this is really another one of those old ones.
 

wetdentist
...also sometimes when clips overlap, part of one clip will become permamently attached to the other one if i try to re-separate the two overlapped clips, which is weird & annoying

 
I can confirm this flakey behavior happening with Auto crossfade, too. The crossfaded region behaves like this.