Kylotan
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).
AHA!!!! I'm going to have to give that a try because I had to completely abandon Sonar for the MASSIVE time stretching adventure I've been on (which is thankfully/hopefully coming to an end today).
So yes... I noticed Ctrl stretching was not obeying Snap and yes I saw the grey Offset flags (but didn't know what they were). If changing a setting fixes it that would be AWESOME.
However it still doesn't help me with the type of bulk work I've been doing (multi track sessions) because even if the clip stretching obeys Snap it does not obey "Clip Groups" (as in grouped clips of a multi track session will not stretch simultaneously and instead need to be stretched one at a time).
So the combination of having to manually and visually line up my transients to the desired measure/beat marker without Snap and then having to REPEAT that process for EVERY clip (which requires VERY high Zoom resolution to avoid "phasing" across the tracks/clips) was of course VERY cumbersome.
If Snap worked then it becomes WAY easier but still a pain because each clip would still need to be Snap Stretched one at a time.
If there is a solution to that Grouped clip stretching problem I would LOVE to hear it (and I posted a thread about it some months back once I discovered this).
In the meantime I've taught myself how to make this all happen in Reaper (which was a massive undertaking itself). Multi track stretching works SOOOOOOO much better/faster in Reaper but of course once it's done I scramble back with the files to Sonar because to me it's just a better creative tool for me.
If they fixed these time stretching issues I would be ECSTATIC but they seem to be focusing on other stuff so I can only hope some love will be given to clip stretching in the future.
The other problem is that even using brute force to make this type of stretching happen with Sonar (I did a couple songs before giving up) it causes some crazy instability and eventually project corruption. The method I figured out works flawlessly for a while (although time consuming) but as the project plods on things get quirkier and quirkier until it's impossible to continue.
Not a rant or whinge. Mostly just posting this so people don't have to suffer through the growing pains I did and to maybe get the attention of the Baker's/community so this gets sorted at some point.
Personally I'm finding shuffling back and forth between Reaper and Sonar quite useful and interesting. The two programs compliment each other quite well IMO.
Cheers.