90% of the time that tool works fine. 9% of the time it does something weird but manageable (like moving some of the adjacent clips but not others). And on that particular set of clips, it shifts the audio entirely. Who knows why? All I know is that it's unreliable and I sincerely hope they rip the logic out and completely replace it, for the sake of you guys who will be using this software in the future.

kevinwal
As for the issues I do experience, I elect to read the release notes and check to see if the most impactful issues are still there. I don't want to tell you how to manage that process, but if you do that, you don't need to post questions like the one you posed here.

To be fair, I don't think the fixes list in the E-zine is detailed enough to be clear when specific bugs have been fixed.

3) Unnecessary snap offsets being added in to clips
 
This bug came with Sonar 6 when SlipStretch editing (part of AudioSnap) was introduced.
(SnapOffset exists in Sonar 4 and probably earlier versions). The buggy interaction between the two evidently was never noticed.
 
It happens whenever a clip and it's audio content do not start at the same place and you then SlipStretch.
Usually this happens when you split a clip. All clips except the first will show this bug.
 
But for testing purposes, you can just go to any audio clip and move the audio around a bit by pressing Shift+Alt and then moving the contents of the clip with the mouse.
 
In the Inspector open the Clip properties and look at Snap Offset. It should be 0.
Now go to your clip, do a SlipStretch edit, and you will see that Snap Offset is at some non-zero value.
Sometimes the flag ends up outside of the clip. so it's best to look at the actual value.
 
Last year, brundlefly kindly gave of his time to help me track this down and I reported it under CWBRN-40003 and the Bakers pretty soon after that set the status to SUBMITTED TO DEVELOPMENT and there the matter rests.
 
My preferred workaround, non-destructive, is to select all affected clips and manually put their collective Snap Offset values back to 0. Annoying, but there you are.
 
If we can make it clear that several of us suffer under this bug (and, I suspect many more who cannot understand why Snap To Grid is not working as expected), then perhaps this bug will come to the attention of The Bakers.

Sadly, I think you guys are wasting your time right now. If you look at the planned improvements, Cakewalk has these huge umbrella fixes planned that will address a ton of reported bugs. Ripple editing is a prime example. This is supposed to fix all the woes related to clip management and all things related to the timeline. I don't think Cakewalk will lift a finger to address editing bugs until this gets rolled out.

Well, of the 14 bugs I reported over the past 4 years, 6 have indeed been resolved.
Admittedly, the last one was some time back. And this particular bug is still my biggest bugbear.
 
I'm still hopeful.
 
Squeaky wheels, oil and all that.