• SONAR
  • Groove Looping re-size issue
2014/07/14 10:40:04
RexRed
Anyone know why when I drag a wave (.wav) into a project, Cakewalk Sonar X3e re-sizes the loop to fit my project tempo, the wave then aligns perfectly to the measures and when I apply groove looping the wave shrinks to the wrong size. So I end up undoing groove looping and manually copying the wave instead.
 
Just wondering if i am doing something wrong...
2014/07/14 14:08:02
Anderton
Ctrl-L is a toggle. It sounds like what's happening is that you are bringing in a file that already has the Groove Clip metadata so it is conforming to the project tempo. When you "apply" groove clipping, you are actually undoing it so the clip goes to whatever its size would be at its native tempo.
 
The easiest way to tell Groove Clip status is to look at the corners. If they're rounded, it's a Groove Clip. If right angles, standard file.
2014/07/14 14:36:03
RexRed
I think you have answered my question. I have not had a chance to test that yet but I am quite sure you are right, thanks! I did not know about the meta data thing and I seem to recall the rounded corners on the wave when I bought it in. I have noticed this happen quite a bit before and did not figure it out. Much appreciated for your reply Craig! :)
2014/07/14 15:21:52
Sanderxpander
I actually have the same issue sometimes, but it's definitely not that I'm dragging it in looped. Sometimes Cakewalk just analyzes it wrongly and thinks it's a different tempo or number of beats. You can solve this by opening the loop construction window (alt+7), going to clip properties and adjusting the number of beats.
2014/07/14 16:27:05
Anderton
Sanderxpander
I actually have the same issue sometimes, but it's definitely not that I'm dragging it in looped. Sometimes Cakewalk just analyzes it wrongly and thinks it's a different tempo or number of beats. You can solve this by opening the loop construction window (alt+7), going to clip properties and adjusting the number of beats.



When that happens, most of the time the issue is Sonar assuming double the number of beats. Changing (for example) 32 to 16 in the Beats field solves the problem.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account