Just curious...   does this still happen if Landmarks are disabled?
 

If you mean does snap to grid stop working, the answer is no; it's only snap to Clips and MIDI landmarks that's failing; snap to Now and Markers also continues to work. I now have a demo project in which scrolling way from the the fully scrolled up position by even the tiniest possible amount breaks snap to Clips/MIDI landmarks.

Huh... weird.   Well, at least it's logged with CW!
 

brundlefly

neirbod
More details - The failure to snap on my system seems to only affect the lower tracks as the OP observed.  Snapping works consistently on the upper track. I think this has something to do with only snapping to what is visible, and a bug in how Sonar determines what is visible.  I my example above I found that if I reduced the size (vertical) of all my tracks I can actually see all of them without scrolling. In this case snap works fine for all tracks.  When I expand a little so that the lower tracks are offscreen, snapping works for the upper tracks.  When I scroll down to see the lower tracks, snapping does not work.  It seems like Sonar is interpreting "snap to what is visible" as "snap to what is visible when you are scrolled all the way up."
 
UPDATE - I tried this in X2a and found the same bug.  Surprised it has taken so long to get noticed.

 
This analysis sounds about right to me, given how little we have to go on. This kind of failure to snap in creatin situations has been reported before, but I'm not sure anyone ever made the connection with scroll position; a search might run up something. I don't often have a need to snap to clips or other landmarks, myself, so never ran into it. 

I think the snap to landmarks is vital when editing live drums. Hopefully one day when "Audiosnap" becomes more reliable it won't be so important but as of now I can't work without it.

PJH
This is NOT a system specific problem. It's a bug.
 
Lets see what Support says.
 

 
Did you contact support, Peter?  I am interested in hearing what they say about this. I tried calling yesterday but they were closed.  Won't have a chance to do so today.  Any updates are appreciated.  
 
Dave
 

neirbod

PJH
This is NOT a system specific problem. It's a bug.
 
Lets see what Support says.
 

 
Did you contact support, Peter?  I am interested in hearing what they say about this. I tried calling yesterday but they were closed.  Won't have a chance to do so today.  Any updates are appreciated.  
 
Dave
 

Hi Dave,
 
I did contact support via email. This was on Wednesday 20th Nov. The only thing I've heard is from their automated response.
 
I'll report back as soon as I hear anything.
 
Cheers,
 
Peter.

Someone else wrote that this issue seems to have been fixed in X3d, but for me it is still broken as before.  Can anyone else check?

neirbod
Someone else wrote that this issue seems to have been fixed in X3d, but for me it is still broken as before.  Can anyone else check?

I checked my system when I installed the patch and mine seems to be working properly now.
 
Cheers.

Well this is odd. I tried again and now it seems to work.  But I swear it was still acting buggy last night (or maybe it was the wine).  I guess I will put this in the "probably fixed but I am still keeping an eye on it" file.

People always forget about the glass of wine step and it should be used more often!