[Solved] Groove clip is busted in X3

I can't reproduce this particular example, but see my post #5 in your other thread for the fix.

TS was able to repro in X3b and can't recover. I would call this a broken feature and hope it gets fixed very soon. Once you get into this situation, you can't get out of it. I hope to hear from DEV on this.

I think the bottom line is that the default tempo is incorrectly calsulated for audio files for groove clipping. I don't know what triggers it, but it ends up that way. I hope the bakers chime in on this one with something to try. All of my SONAR versions are affected by this. Groov clip looping does not work...

Broken is a very harsh word, it means:
having been fractured or damaged and no longer in one piece or in working order.
 
what you call broken, I call a possible bug.
but I cant replicate it, so I cant even say it's a bug.

groove clip is not broken. if it didn't work at all I may agree.
sometimes such words can make one potential user decide not to buy x3.
that's why I choose my words wisely. something people should really focus on when describing issues. 

groove clips are working for me fine, you have one scenario here.
how do you call that broken ?
you cant use a certain feature of it ? yet ive been able to work around it using the same method as dave.
 
all im saying is you cant say something is broken while im still using it..lol.
its not broken for me. 

I actually bounced the clip to a trimmed clip minus the audio at the ends. I then went to set it as a groove clip. So I was not working with a slip-edited clip.

Okay, I see what you're doing wrong.
 
You are trying to create a three-measure groove clip. That's 12 beats.
 
When Sonar estimates the clip length, it will typically "guesstimate" to 2, 4, 8, or 16 measures - whichever is closest - as these are the most common loop lengths used in dance music. Since you said it's "larger," then I assume Sonar guessed the 12-beat clip was 16 beats.
 
When I duplicated your steps above, Sonar generated a groove clip that was 16 beats. In the loop construction window, "Beats" said "16." I changed it to "12," because you specified you had created a clip with 12 beats.
 
As soon as I did that, the groove clip was 3 measures (12 beats) long and did exactly what you wanted it to do.
 
Groove Clips are NOT broken, but for situations outside the normal 2-4-8-16 loop lengths of dance music, you will almost certainly need to tell Sonar the number of beats. I did several loops once in 7/8 and believe me, Sonar did not guess those right, either.
 
P.S. This isn't a diss on tech support at all, I've probably logged more hours in the Loop Construction window than ANYONE at Cakewalk...maybe anyone on the planet...
 
P.P.S. I'm determined to fix this for you so please provide all pertinent information - e.g., what the "Beats" parameter says in the loop construction window.
 
P.P.P.S. One reason why the acidization is so lousy in loop libraries is that they just put the loop into Sonar or Acid, click on "make this friggin;' thing a loop," then think that the loop is therefore acidified. No!! Except for all but the simplest loop, Acidization (or groove-clip looping) will require some tweaking and manual intervention. This is also true with Apple Loops and REX files, so you won't get any relief there either. 
 
 

Guitarmech111
 I still get this behavior from a 12 bar loop though. It goes to 4 extra measures. The beats is set at 16 in the loop construction window. It is really only 12 in my test loop and the tempo defaults to 160. My project tempo for the test is 120. There is an error there already. 

No, it's not an error; again, it's an incorrect estimate on the part of Sonar, which as far as I can tell is highly likely with any loop that is not a power of 2. 
 
For example I just created a 12-bar loop. When turned into a groove clip, correct - it goes to 16 measures, but that's because Sonar is guessing to the nearest power of two. However, I think you meant to say beats shows 64 (i.e., 16 measures x 4 beats = 64 beats). The tempo says 160 because it has analyzed that for a clip of that length to cover 16 measures, the tempo would have to be 160.
 
As soon as you tell the construction window that the clip is NOT 64 beats long but 48 beats long (12 x 4 = 48), then the construction window shows the correct tempo of 120 BPM, and the loop length is now 12 measures, as it's supposed to be. 
 
So the bottom line is this: Whenever you create a groove clip and open the loop construction window, check to see if the number of beats is correct. With loops that are a power of 2 in length, it almost certainly will be correct. If the loop is not a power of two, then you will almost certainly need to tell Sonar what the loop length is, in beats.

Guitarmech111
in the case of my bass clip, it does not stay in sync even though it shows 48 even beats and the tempo shows 120. I sent you a PM of a project link that demonstrates what I am seeing and playing with.
 
I understamd all of what you are saying, but the bass clip groove looping does not stay in sync after being converted to a groove clip with 48beats and tempo=120bpm.

this is the setting you need to change, highlighted in red - set beats in clip to 48, and you don't need to bother with LCV for basic looping. 
 

 

Guitarmech111

yeah, I call it broken because I can't use it and neither can one other person who has chimed in as well as tech support. Audio groove clipping is unusable for me. ANY bounced, non-slip edited, clip does not groove clip for me and others with the correct tempo/BPM...
Charlie, let's not try and beat that horse again. If it works for you, great, I am glad. It does not work here and confirmed by TS.

 
hopefully now you could understand what im saying.
 
Good luck.
 
 

good looks, craig!

almost  :-D

I'm glad to help!! Let me add a coda (I guess you can't subtract a coda...never mind).
 
Converting files to the Acid or REX formats appears simple, but doing it right is actually very difficult. Companies have paid me substantial amounts of money to acidize their files because my files worked and theirs didn't...it's a shame that so few sample libraries put serious effort into acidizing files.
 
In this case, I don't think it was about not bouncing to clip, I think it was likely about trying to acidize a clip before trimming it. So for future reference, before acidizing a file, trim it. If you've done anything else with the file (e.g., audiosnap or whatever), you can always play it safe by bouncing to clip.

Anderton
Converting files to the Acid or REX formats appears simple, but doing it right is actually very difficult. Companies have paid me substantial amounts of money to acidize their files because my files worked and theirs didn't...it's a shame that so few sample libraries put serious effort into acidizing files.

I had no idea that the Groove Clip used the Acid format. I used to use Acid for a variety of pre-composition loop generation that I would import into Cakewalk (probably back in the Pro Audio days). Always was very fiddly as I recall!!

Red Firebird
From my last test, if I try to loop 7 measures it tries to make it 4, if I put 9 it tries to make it 8, if 8 it stays 8... interesting!

See post # 14 above for more info...