So what I wrote in post #7 isn't the issue?
 
Incidentally, moving drum hits within a clip using Audiosnap automatically takes care of the stretching for you. I understand if you've chosen splitting over Audiosnap for other reasons, but thought I'd mention it in case you're not aware of this feature. 
 
 

brundlefly
So what I wrote in post #7 isn't the issue?
 
Incidentally, moving drum hits within a clip using Audiosnap automatically takes care of the stretching for you. I understand if you've chosen splitting over Audiosnap for other reasons, but thought I'd mention it in case you're not aware of this feature. 
 
 

And FWIW, the OP does have the Landmarks icon enabled.
 

 

brundlefly
So what I wrote in post #7 isn't the issue?
 
Incidentally, moving drum hits within a clip using Audiosnap automatically takes care of the stretching for you. I understand if you've chosen splitting over Audiosnap for other reasons, but thought I'd mention it in case you're not aware of this feature. 
 
 
 
I do have the landmarks icon enabled.
 
 I have tried Audiosnap and find it notoriously unreliable. It seems to work fairly well on a single drum track but to try and get a decent result with 8 or 10 tracks of live drums is so hit and miss it's a complete waste of time.
 
Has anyone else tried what I'm attempting? I'd just like to know if they have the same result as I do. I'm convinced it's a bug. I cannot believe that "snap" stops working when you merely use your mouse to adjust the level of your screen.
 
Cheers,
 
Peter.
 
 
 
 
 

PJH
Has anyone else tried what I'm attempting? I'd just like to know if they have the same result as I do. I'm convinced it's a bug. I cannot believe that "snap" stops working when you merely use your mouse to adjust the level of your screen.

 
Okay. After some experimenting, I am able to replicate this. Snap to clip landmarks just quits working when the track view is scrolled to certain positions, especially down where only the last few tracks are in view.
 
Looks like a bug to me. You'll want to take a minute to report it here:
 
http://www.cakewalk.com/support/contact/problemreport.aspx
 
I'll do the same.
 

brundlefly

PJH
Has anyone else tried what I'm attempting? I'd just like to know if they have the same result as I do. I'm convinced it's a bug. I cannot believe that "snap" stops working when you merely use your mouse to adjust the level of your screen.

 
Okay. After some experimenting, I am able to replicate this. Snap to clip landmarks just quits working when the track view is scrolled to certain positions, especially down where only the last few tracks are in view.
 
Looks like a bug to me. You'll want to take a minute to report it here:
 
http://www.cakewalk.com/support/contact/problemreport.aspx
 
I'll do the same.
 

Thanks, brundlefly. I did fill in a problem report but it was the usual story.
 
"The problem you are
experiencing is most likely a system specific problem or a configuration issue
that we believe can be resolved with assistance from Cakewalk Technical
Support. Unfortunately, as explained in the Problem Report Form, this form does
not put you in direct contact with our support staff."
 
This is NOT a system specific problem. It's a bug.
 
Lets see what Support says.
 
Cheers,
 
Peter.

Confirmed here as well.  I am not sure exactly what triggered the change.  I have two tracks far enough apart that I need to scroll to see them, both split.  At first I can move the edges of the clips around and then snap back to each other at the break.  I tried scrolling (both with mouse wheel and arrow keys on the track view) and everything still snapped correctly. I then tried vertical zooming and it still worked. I then tried a few random moves of scrolling and zooming and suddenly the snap stopped working, despite the markers button still showing that snap is on.
 
Glad you picked this up as I had intermittent problems with this that I never dug into.  I will file a bug report as well and link to this thread.  Having a few of us point out the issue should make Cakewalk look into it and not blame a specific system.

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.

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.

Thanks neirbod,
 
Hopefully if more users file reports, it will get looked at.
 
Cheers,
 
Peter.

I got the same message:
The problem you are experiencing is most likely a system specific problem or a configuration issue that we believe can be resolved with assistance from Cakewalk Technical Support. Unfortunately, as explained in the Problem Report Form, this form does not put you in direct contact with our support staff.
 
I will try calling tech support, but given three of us have the same problem this almost certainly a bug.  I linked to this thread in my report and mentioned several of us are experiencing it, so I am surprised they don't see it as a bug.
 
Dan, are you still following this?  I'd be curious to see if this sound system-specific to you.

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.