Here's the problem (since Sonar 8):
 
I often split a track into clips and then shrink or stretch the clips (Ctrl+drag edge of clip) and move them to line them up with the grid.
 
Unfortunately, a bug in Sonar causes the Snap Offset to get some random value when I stretch/shrink any clip OTHER THAN THE FIRST CLIP OF A TRACK. This is important. The bug happens whenever the start of the clip and the start of the underlying audio are not the same. So it starts from the second clip onwards.
 
And now snap-to-grid behaves strangely because it is trying to snap to this offset value!
 
I am left with two possibilities: Bounce clips (but that's destructive) or put Snap Offset manually back to 0 every time.
 
This bug has been like a block of lead to my productivity ever since Sonar 8. I reported it but it has been "In Development" for the longest time.
 
And frankly, I don't think it can be fixed. Shrink/Stretch inevitably introduces a fraction which needs rounding, so the Snap Offset will frequently drift by 1. If this is inside a clip - not so serious. But if the start of the clip is off by 1, that is noticeable.
 
So does anyone actually use Snap Offset? Can we petition the Bakers just to disable it (as an option)?

jpetersen
This bug has been like a block of lead to my productivity ever since Sonar 8. I reported it but it has been "In Development" for the longest time.

I have to say your wording here seems more than a bit disingenuous. The implication is that you've been struggling with this since SONAR 8, but the thread in which you reported it just last September suggests you just encountered and reported it then:
 
      http://forum.cakewalk.com/FindPost/3286987
 
That said,  I just played around with this a bit, and found that selecting the track (i.e. all clips) after splitting and executing Apply Trimming eliminates the problem. Hope that helps.

"Apply Trimming" is gray for clips that have been shrunk/stretched and seems to have no effect on shrunk clips if applied to whole selected tracks.
 
Anyway, its just as quick setting "Snap Offset" to 0 manually, the way I do now (also works for a range of selected clips).
 
September was when I asked why little flags appear when a clip is shrunk and you explained they are Snap Offset markers. Once I knew that, it dawned on me why Snap-To-Grid has never worked right. I reported the bug and changed the thread's title to reflect the new-found insight.
 
Before moving on to mixing, I split, shrink/stretch and reposition clips to get the timing in the pocket. I'm sure everybody does this. With the unreliable Snap-To-Grid turned off, I would zoom in for each repositioned clip. No dis-ingenuity intended. It really has wasted a lot of my time over the years.
 
 I just tried Sonar 7. The bug is there, too.
 

mistake
 

@backwoods:
Yes, I also have Studio One v.3, Reaper (who doesn't?) and I have just installed Cubase 8 LE.
 
None have Sonar's easy-to-use clip-wide stretch/shrink feature, but they do have something along the lines of a primitive AudioSnap. In other words, you can set markers inside a clip and move them around and the regions between them get stretched/shrunk. But not an entire clip like Sonar.
 
None have Snap Offset except maybe Cubase, which has Snap Markers, of which it appears you can have many per clip, and when you hit Quantize, it re-positions clips to the nearest Snap Marker or clip start edge. I'm still learning Cubase.
 
Cubase also has a Time Stretch feature which is a complicated dialog box with many sub-boxes pointing at each other. At first glance it looks more like something you'd use to get a commercial jingle to fit exactly to a given time.

jpetersen
@backwoods:
Yes, I also have Studio One v.3, Reaper (who doesn't?) and I have just installed Cubase 8 LE.
 
None have Sonar's easy-to-use clip-wide stretch/shrink feature, but they do have something along the lines of a primitive AudioSnap. In other words, you can set markers inside a clip and move them around and the regions between them get stretched/shrunk. But not an entire clip like Sonar.
 
None have Snap Offset except maybe Cubase, which has Snap Markers, of which it appears you can have many per clip, and when you hit Quantize, it re-positions clips to the nearest Snap Marker or clip start edge. I'm still learning Cubase.
 
Cubase also has a Time Stretch feature which is a complicated dialog box with many sub-boxes pointing at each other. At first glance it looks more like something you'd use to get a commercial jingle to fit exactly to a given time.

@jpetersen,
  I am all in favor of fixing bugs in Sonar and will support any user in that endeavor, but please do not spread misinformation in your posts.  My response is not intended to promote any other DAW on the Sonar forum, but I wish to correct your lack of knowledge of 2 of the DAWs you reference.
 
If you don't know that the DAWs that starts with "R" and "S" have the same clip stretching capabilities as Sonar, then you have never used the software or have never cracked open the help text.  Both DAWs stretch and shrink clips using Alt drag at the end of the clip.
 
In addition, "R" has snap offset markers to provide the same function as they do in Sonar.
 
By providing misinformation, you lose credibility when reporting the issue.
 
-- Ron

jpetersen
"Apply Trimming" is gray for clips that have been shrunk/stretched and seems to have no effect on shrunk clips if applied to whole selected tracks.

I meant apply trimming after splitting, and before slip-stretching. It's the combination of slip-editing and slip-stretching that causes the problem. Splitting creates slip-edited copies of the original clip for each segment. Apply Trimming renders the slip-editing permanent which eliminates the problem. And You can Apply Trimming to all selected clips at once without having to individually reset every Snap Offset - much easier.
 
 

@SquireBum:
 
backwood asked if I also had other DAWs and whether they also had slip-stretch and snap offset functions.
 
I assume backwood's thinking was that, if they do, how do they behave in the same conditions and if so, perhaps they have found a solution. The object was not to compare features and I am happy to admit to my limited knowledge.
 
It seems backwood's question has been deleted in the meantime.
 
Edit: Neither have a snap offset feature so Sonar's problem does not arise with them.
(S definitely does not, I had it confirmed. R may have it under a different name, I do not have access to R's help)

brundlefly
I meant apply trimming after splitting, and before slip-stretching. It's the combination of slip-editing and slip-stretching that causes the problem. Splitting creates slip-edited copies of the original clip for each segment. Apply Trimming renders the slip-editing permanent which eliminates the problem. And You can Apply Trimming to all selected clips at once without having to individually reset every Snap Offset - much easier.

Ah! OK, understood, thanks.
Oh. Unfortunately the result is destructive.
Should I need to extend a clip a bit later - no can do.
There's no audio anymore beyond the clip boundaries.
 
I hope Sonar comes with a solution soon.
I didn't realize I reported it only September last year. It seems so much longer!
 
Thanks for the help!

Take a copy of the original track and work on the copy. If you need to work on previously discarded material it will still be there.