So I don't know why I never really had this issue in Sonar 8.5 (not really never, sometimes I did, but far far less)... But I have it almost every single time in X3.
 
So I go hit record, I start playing my keyboard, until I have a nice little melody/progression that works. Lets say for the sake of the story its a 4 bar loop and the part I like is from bar 4 to bar 8. I also quantized it at 1/8th notes. So with snap on, I cut it at bar 4, I cut it at bar 8, delete everything before and after, and proceed to drag out some copies to repeat that little piece. Like 90% of the time, it looks perfect, but when I play back I notice a hesitation. So sure enough I go in, and there was the tiniest of tiny little blank space before the first note in the progression, leaving all the copies off by a little bit. The first note doesn't start at 4:01:000 it's at like 4:01:xxx some random little number. Not even a nicely quantized number even though the whole thing was selected when I hit quantize.
 
So obviously I then delete all the copies I had made, right click the original, hit Apply Trimming, drag the clip that little tiny fraction of a bit back to start at 4:01:000 and then make my copies and all is right. It's just annoying and if there's something I'm not doing that would save me that hassle I'd love to know.
 
Thanks!

Honestly I have never been completely happy with Sonar's snap behavior. For some reason Logic always does exactly what I mean it to without needing to specify landmarks, resolution or snap to/by.
But that doesn't really help you. The way I cut is by selecting the clip and then navigating to the correct bar with CTRL+PGUP/PGDN and then hitting split. I think this way it's impossible to get extra bits or too short bits. Sounds like when you're mouse cutting, you may be inadvertently hitting some landmark rather than the barline.

that's interesting, the ctrl+pgup/pgdn. I didn't know of that keyboard shortcut. Nice to know and maybe it will help. Thanks.
 
I'm kind of the opposite, the reason I've stuck with Sonar all these years (Since Cakewalk Pro Audio 4.0) is exactly because I always had an easier time making my clips and snapping them to bars to create grooves/loops out of what I played on the keyboard. I've played with Logic, Cubase, Protools... None of them ever felt right to me. But now that I just recently switched to the X series from 8.5 I'm having all these little growing pains. I'm sure I'll get used to it eventually. It was definitely time to finally switch haha.

I will agree that 8.5 certainly did this better. I think they made all this fancy editing features way to complicated in the X series and for some of us it does not behave the way we think it should. It's totally illogical. I get the same results you do  if I try and record a simple drum pattern and drag it out.  So I just stopped working that way. In 8.5 this always worked without issues. Many will claim improved workflow with X3 but this after 6 months is not true for me. That's why I'm lurking the forum hoping to shed some light on this...
 
 

Good to know I'm not alone haha.
 
I'm sure the "right" thing to do is use groove clip looping for this, but copying and pasting and or shift-dragging is like muscle memory for me at this point after 10 years of doing it every day.
 
I also can't for the life of me figure out why comping is the default recording mode for when you're recording midi. I could save a new Normal template I know but I always forget to do it until I'm already in the middle of a new project and realize that I can't hear the notes already recorded when I go to try to record a few different notes in over a track haha. It's like I'm taking crazy pills over here...

Groove clipping can lead to the same issue and others. You still need to trim correctly.

laaaame.
 
like I said. correctly is kind of like, a relative term here? I don't know if that's the right phrase haha... But if I am snapped to grid, and pretty well-enough zoomed in to see that I'm definitely clicking on the start of bar 4... And with snap on it would HAVE to truly be the start of bar 4... Yet it still doesn't trim correctly... That ain't me making the mistake. :-)

I agree. But for that use case, the CTRL+PGUP/PGDN navigation really helps.

Hrm. Check your snap settings maybe? If it's set to "Move By" instead of "Move To" (though I always use "Move By"), and/or clip landmarks are selected you may not actually be trimming it at bar 4 and bar 8, but instead are snapped to something that is also very close to that beat boundary.
 

...wicked
Check your snap settings maybe? If it's set to "Move By" instead of "Move To" (though I always use "Move By"), and/or clip landmarks are selected you may not actually be trimming it at bar 4 and bar 8, but instead are snapped to something that is also very close to that beat boundary.
 

^^^^
 
Having been around these parts for a long time, what you're describing is not new to the X series.  The "perfect" loop has always been dependent on snap settings, zero crossings, etc, etc.   Has it gotten a little more sensitive in X?   I dunno, maybe.   But whatever is there now has been all along to some extent, so I by default go through the process I always have of insuring that I've properly trimmed the clip before proceeding.