Can anyone confirm whether this is a bug in X3c?

I can't speak to the exact situation, but I have had intermittent trouble in X3c with snapping to clips.  I will try the workflow you describe and see if I can recreate the problem.

By scrolling do you mean using your mouse wheel to zoom in? I'm not sure I understand the recipe to try and reproduce.

OK, I'll try to be more specific.
 
I do a lot of drum track editing. Sometimes up to 12 tracks of drums. There are many occasions where I have to cut up tracks and move drum hits into time and then time stretch the "gaps" to close the "holes" in the track. I then have to do the same to all of the tracks.
 
These 12 tracks are not always visible on my screen as I'm slightly zoomed in. I'll set my snap to "snap to clips" and start time stretching one drum track at a time. eq Kick, Snare, Hi Hat, Tom1. Now in order for me to stretch the rest of the tracks (Tom 2, Tom 3, Tom 4 etc) I have to scroll down so that the rest of these drum tracks are visible.
 
As soon as I do that (scroll down so that I can see the rest of my tracks), the snap function no longer works.
 
I then have to undo the stretched clips, zoom out completely so that all the drum tracks are visible on the screen and redo all the time stretching again. As long as I don't scroll the snap works.
 
I really hope I'm making sense here.
 
If not I'll make a few pics to try and make it clearer.
 
Thanks guys,
 
Peter.

Hi guys,
 
I've made a few pics to try and demonstrate what my problem is. In Pic 1 the "snap" function works perfectly.

 
In Pic 2 after moving the screen down to reveal the remaining clips the snap function stops working.

 
I'd like to add that this function has worked for me in 8.5, X1 and X2.
 
I hope this make things a bit clearer.
 
Cheers,
 
Peter.
 
 

Bristol_Jonesey

There are many occasions where I have to cut up tracks and move drum hits into time and then time stretch the "gaps" to close the "holes" in the track

 
Are you completely sure this is absolutely necessary?
 
Can you not simply move the individual drum hits to where they should" be and just move on to the next phrase?
 
I assume you're talking about audio tracks here, not Midi yes?

Yes, It's audio.
 
If you cut a clip and move a drum hit it will leave a "hole" in the audio and you will have a gap where there will be no audio. If you have a cymbal crash thats decaying over the hole you will have a gap in the audio.
 
Thats why you have to time stretch the audio to close the gap and not have any breaks in the audio tracks.

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.
 

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.
 

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.

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.

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. 

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.

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.

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.

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.

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