chuckebaby
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. 

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.

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. 
 
 

Cool beans Craig.
 
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. 
 
I have a bass clip, non-slip edited, and it is exactly 48 beats. When trying to groove clip it, it is 64 beats by default. I change it to 48 and the clip changes to what seems to be the correct length iteration of the loop and thema partial drag of the next sequential loop. I drag the partial loop back to a whole groove clip loop where the clip is only 48 beats and the clip(bass) gets out of sync with SD within 3 bars. When I undo GCL and the original clip is playing, it is as expected.
 
 

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.

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.

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. 
 

 

Fixed!
 
First of all, did you know the guitar and bass clips are not the same length (the bass clip is correct, the guitar is longer)?
 
Second, the bass clip was not trimmed and it seemed to have some other metadata or weirdness, perhaps from trying to loop before it was trimmed properly. You always should make sure the loop is the right length before trying to loop it. So here's the fix:
 
1. Select the bass clip. Choose "Apply Trimming."
2. To make sure it's a "clean" clip so you can start over from a suitably initialized state, select the bass clip and choose "Bounce to Clip." This will return it to a standard WAV file.
3. Select the clip and choose Ctrl-L to loop. It will lengthen to 16 measures, but no worries.
4. Double-click to open the Loop Construction Window.
5. Set Beats to 48. Tempo will indicate 85 BPM, and you're good to go.
 
The reason I knew it hadn't been trimmed properly was that the first time I tried to loop it and I set beats to 48, the BPM was 84.175 or something like that. That's why it was going out of sync.
 
I didn't have Superior Drummer, but set up SD3 and used your MIDI track. I've been looping the bass and drums for 15 minutes and everything is in sync; FYI that's with the metronome off, so I'm not convinced that you have to have the metronome on for things to be in sync. I think it has a lot more to do with cutting to zero-crossings instead of measure boundaries.
 
BTW I posted this response in the duplicate thread on the same subject. 

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.
 
 

the above steps did work!
 
I think that this is a 2-fold issue where the zero crossing and bounce to clip didn't perform as expected and I was expecting a different behavior. I always thought that bouncing to a clip would remove the audio without having to apply trimming. I have always used the bounce to clip as my 'apply' trimming process. The bigger issue is the zero crossing. I will definitely remember that!
 
Thanks Craig! great detective work. I am glad that project was able to help identify the issue. Your time is very much appreciated!
 
I am able to groove clip this project and no out of sync conditions are present after your steps above.

good looks, craig!