I take a 4-bar piece of audio that has been stretched to 86%, ensure Snap is set to 'To' and to 'Whole Note', drag-copy the audio to the right, and it aligns it to about 60% of the way through the 4th bar. Nothing I can do with Snap enabled will get it to line up with a measure. If I switch from whole notes down to something smaller, I can reduce the amount of error - eg. snap to 1/16 means I can get it to about 60% of the way through the 4th beat of a bar.
 
Here's the really weird thing: even manually editing the clip's Start time in the properties doesn't work. If I edit it to 8:01:000, it moves it to the wrong place and the resulting value is 7:04:082.  Nothing works.
 
But if I stretch the audio back to 100%, and then try moving it around with Snap to Grid on... it goes exactly where I'd expect.
 
Known bug? Is there a workaround? I need to be able to stretch audio and move it around for an entire song, so if this is totally broken I'll have to ditch Sonar for this track.
 
Using Sonar X3e build 352, 64bit.

I can't reproduce what I think the issue is so I need to find out more info. Is this the situation...
 
1. You have a clip. Let's say it starts at measure 5.
2. You stretch it to 87% of its length.
3. Now you want a copy of the clip to start at, say, measure 17.
4. You drag-copy the clip, but can't get the clip beginning to start at measure 17.
 
Yes? I can do that here, so I figure this isn't what you're trying to do.
 
I assume if you bounce it to clip, it will then do what you want (which you should do anyway because the real-time stretch uses a preview algorithm...doing an offline render improves the audio a zillion per cent). Is this the case?
 
What you're describing is not expected behavior so I'm sure there's some issue that can be solved.

The situation is exactly as you described it, but I think I have found the culprit.
 
When I perform the stretch operation, a tiny little flag marker appears some way in from the left; and it is this which gets snapped to the grid.
 
This appears to be a 'snap offset' in the properties - if I change that to zero, everything works from that point onwards.
 
No idea why the offset appears with a seemingly arbitrary number - that appears to be a bug.
 
So, hopefully I can proceed with my project now (apart from all the other bugs that are appearing by migrating from 8.5 to X3, mostly with take lanes getting very confused over how they are supposed to handle what used to be layers).
 

(PS. That post came after 2 hours of 'Unexpected Error' messages. Cakewalk really need to get this forum fixed!)

Kylotan
No idea why the offset appears with a seemingly arbitrary number - that appears to be a bug.

Probably some kind of 8.5/X3 translation, but there's also a keyboard shortcut for that function - don't recall what it is offhand. Maybe it gets triggered accidentally?
 
I always try to finish projects using the program with which they were started, but if that's not possible, then I cheat and export the raw audio and import that into the new version.

It's not a keyboard shortcut, as all I do is Ctrl-drag the edge of the clip and it breaks it. (Also, that ctrl-drag is a real headache - usually about 5 seconds of Hunt The Pixel is required before I can get it to show the right icon.)
 
Most of my projects are never finished, as I use Sonar to record and collect ideas. And exporting raw audio would just be a nightmare as I am trying to work with individual clips.

Kylotan
And exporting raw audio would just be a nightmare as I am trying to work with individual clips.

This is why the time-stamped Broadcast Wave format can be so helpful. Then all the clips show up where they're supposed to. 
 
Try this: In 8.5, export all the clips as individual Broadcast Wave files with names that indicate clearly the tracks to which they belong. I think you can also just "save as" the project and save each clip as an individual file. In X3, open the 8.5 project, then delete all the audio so you have the same "structure" you had before. Then, drag the clips into their respective tracks and they should line up where they were in 8.5.
 
This is from memory, but I'll check into it later as it would make a good general-purpose tip anyway for any kind of transfer, even from one DAW to another.
 
There's usually an easy way to do things with Sonar...the hard part is finding it 

Seriously, this would take hours. I have several hundred audio clips in any given project, plus MIDI clips, markers, and other events. Cakewalk just need to be getting their backwards compatibility working properly if they don't want to supply fixes for old versions. This isn't something I should have to work around.

Kylotan
Seriously, this would take hours. I have several hundred audio clips in any given project, plus MIDI clips, markers, and other events. Cakewalk just need to be getting their backwards compatibility working properly if they don't want to supply fixes for old versions. This isn't something I should have to work around.

I'm going to give it a try anyway. I have several really complex projects I can test...I'll see how long it takes to export from Sonar and import to Cubase. I think there are enough shortcut options, like batch saving or maybe even drag and drop directly from one project to another, that it would take a lot less than several hours. I also have some 8.5 projects but haven't experienced the issues you have, so that's probably not a good test...getting files into a different DAW altogether would be interesting.
 
Remember, the key is opening the old project and just deleting/importing the audio. If the markers and other accoutrements exist, and you don't delete the MIDI files or instruments, then it would be a pretty speedy process.
 
Agreed total backwards compatibility would be great, but there are several key functionality differences. The X-series is essentially a new DAW.

Ok, I have a test case for you that shows it's not a compatibility issue, just a bug.
 
1) Create new project with Normal template.
2) Add an audio track.
3) Record 4 bars of audio, or just over that amount.
4) Slip-edit the start and finish so that only 2 bars remain.
5) Ctrl-drag the end so that the clip now takes up 1 bar, showing '50%' at the top.
6) Note that the clip now has a snap offset - in this test, it appears to be almost exactly half-way through the clip for me.