I'm sure I've heard other people mention these but I can't remember if the question was ever answered. Oftentimes I will see very thin "slivers" of clips on a track, and no matter how far I zoom in, they don't get any wider. However, I can marquee them and see that they're selected, and then delete them. Seems like one of those silly Sonar bugs but I'm genuinely curious how they came to be. I just opened a project with a track that I had dragged a sample from the browser onto the last time I worked on it - I didn't move this clip around, or edit it or split it or anything like that, and yet there was a sliver of something further up the track that I ended up deleting. What the hell are they? 

Sharke, (hey, it that e silent or what? Are you "shark" or "shark-ee"?)
I get those slivers if I use something like geist (don't you use that?) and control it via midi. Every time I press a keyboard key on my controller during record (to, say, change to a different preset), Sonar saves each keypress as a new clip.
 
Have you ever viewed events (event list Alt+8) for a track with all those slivers? Are they tied to actual midi events, or just some sort of ghosts?
 
Jes' saying, those slivers bug me too. The one's I see are legit (as described above), so what I do is lasso them and bounce to clip, so they are one familiar long midi clip.

czyky
Sharke, (hey, it that e silent or what? Are you "shark" or "shark-ee"?)

 
I have no idea. I honestly never thought that far ahead!
 

I get those slivers if I use something like geist (don't you use that?) and control it via midi. Every time I press a keyboard key on my controller during record (to, say, change to a different preset), Sonar saves each keypress as a new clip.
 
Have you ever viewed events (event list Alt+8) for a track with all those slivers? Are they tied to actual midi events, or just some sort of ghosts?
 
Jes' saying, those slivers bug me too. The one's I see are legit (as described above), so what I do is lasso them and bounce to clip, so they are one familiar long midi clip.

 
I use Geist, but I don't control it via MIDI. I do all of the sequencing within Geist and then bounce to audio. Besides, these are slivers on audio tracks. I dare say I have seen them on MIDI tracks at some point as well though. 

For me it happens when a crossfaded clip is nudged. Not every time, mind you, and not in every project either. In our big live album project, this was a major headache, especially since it was a 70 minute long session with a lot of cuts over that 70 minutes...!

Weird. Perhaps that's what it was. Mind you, I rarely use nudge if ever. Can't rule it out though. Another problem I've seen recently is that all MIDI clips in a project have been nudged forward by 8 ticks. Every single one! But not the audio clips. If it was all of my clips I could imagine a scenario wherein I'd selected everything and accidentally nudged it. But just the MIDI clips? Sonar you strange beast lol.....

Came up against that one recently too. It's pretty rare for me to have MIDI timing issues like that (and I get nothing like the craziness you've had - I'd be looking elsewhere too if my workflow was that impacted) but yeah, definitely some anomalies going on for sure.

I looked elsewhere - Reaper and Bitwig - and I'm in DAW heaven! Still have to use Sonar in the transferral of projects across though. Although I guess the issues I have are now less annoying knowing that I no longer have to put up with them going forward. 

Ah yes, the "splinters" and the bane of my editing workflow in take lanes. IME, these "orphan" clips are created when any portion of any concurrent clip in any lane falls outside the swipe selection of a clip in one lane. They block the selective slip editing of other clips (depending when they are created/edited?) which is annoying and are a likely suspect for the only conditions which will consistently crash SONAR for me. 
 
In practice one tends to run with a feature until boundary conditions are encountered. I often generate 10-20 take lanes when tracking free form vox or lead instrument solos and "cross-comp" between the takes. (By "cross-comp", I mean >1 one concurrent clip with differing lengths will be selected/active.) 
 
To be fair, I can see how keeping track of so many edit complications could lead to an unstable project state given both how easy and flexible/free of restrictions it is to edit clips in take lanes in SONAR. 
 
I've tried to do this in SO3 and it does not seem to support the same degree of flexibility which might be a design choice to maintain the integrity of the project. 
 
My workflow practice includes saving constantly, deleting splinters, clearing undo history, eliminating redundant takes and moving "keeper" takes to their own track as soon as possible to cut down on the amount of active edit states that have to be maintained. Even with the additional "housekeeping" I find I am significantly faster and more productive using SONAR than an alternative. 
 
 
 

jackson white
IME, these "orphan" clips are created when any portion of any concurrent clip in any lane falls outside the swipe selection of a clip in one lane.

That sounds like the normally expected result of using the Comping tool. When working near the ends of overlapping takes that weren't done by punching in or loop-recording with identical start/end times, you can end up with small segments of slightly longer takes being split off. But that's different from the zero-length slivers that Sharke's talking about, and not unexpected.

Yeah I rarely use comping and yet they're all over my projects.