[Solved] Groove clip extends clip by several measures and slows time - X3c

I have a bass clip I recorded that is 12 measures long. I am able to play it and it sounds fine for what I want to do with it. I am trying to put together a new song and want to groove clip this for several iterations in a row. When I go to groove clip this clip, the clip gets extended for several meaures longer than what the original is and the timing is slowed as well. I did not do any timing changes or anything. Why in the world does this happen??
 
I was happy earlier, but now I am back to irritated again with SONAR... I hope this is something simple. any suggestions?

Thanks for the reply Steve, didn't drag anything. I bounced the clip to a single clip removing any extraneous audio so that it fit inside the desired measures.

I right clicked the bounced clip and enabled groove clipping. The clip then extended several measures and slowed down to match the measures it was stretched to. On top of that, the process made the clip sound horrible. Stretching needs to be enhanced somewhat...
 
36 minutes to wait on hold for TS and no 800 number??!!

I don't know why this happens sometimes. Go into the Groove Clip section of Clip Properties in the Inspector and change the Beats in Clip to 48 (assuming 4 beats/measure) , and then roll it back to 12 measures (or out to however many you want).

still the wait time is 36 mins after 10 mins on hold..

Did you miss my post #5? I think that'll fix it.

TS is able to repro this in X3b. When it happens, I get the same results in 8.5. There is something that is gettig corrupted by X3 in a shared component. So basically, Groove clip looping is down for the count for me.

The original tempo is getting set to something than the set tempo. My project tempo is 120, but when I go to groove loop the clip, X3 changes the default tempo to 160bpm. Someone made a bad calculation somewhere in the code. Right now, Groove clip audio is broke for me. this has affected all versions of SONAR that I have.
 
Groove clip midi works as expected.

Is no one else getting this? Isolated problem?

I am able to reproduce a 12-bar clip stretching to 16 and showing 64 beats in clip properties, but changing it to 48 beats fixes it completely. I was not able to reproduce the other one where bars 3-6 were cut out of a 6-bar clip and groove-clipped. That gave me a 4-bar clip that looped as expected.

Edit- sorry, I got here late, ignore ...  This is just Sonar mis-estimating the number of beats in a clip. Happens occasionally. To make sure it's being grooved properly, before you groove it, first make sure the clip begins and ends exactly at measure boundaries for the tempo you recorded it. Then ctrl-L to groove it. Then take a look at the clip's groove properties in the inspector. If the number of beats is wrong, change it in the properties. Then it should line up and extend just the way you expect.

changing it to 48 beats gets it close, but no cigar on the bass track. It gets ever so slightly out of sync. The only way to get the beats is to have it groove clipped I guess. What do you use to determine what the beats are? I never had to worry about that. This usually always worked for me.

You are very welcome.  :)

I can assure you that, having worked with groove clips since Sonar 1.0 as well as with Sony Acid 1.0, the groove clip function in Sonar works and will create loops of the desired length. HOWEVER, and this is REALLY important, it's not a "plug-and-play" function. You can't always tell a file "Hey turn into a groove clip" and assume Sonar will make all the right decisions.
 
Creating groove clips that work really well is an art and a science. In your case, I think the science is more the issue...first, make sure the clip is trimmed to the right length, and second, that you've entered the correct number of beats.
 
In the process of editing thousands of groove clips and producing two sample libraries with groove clips (Technoid Guitars for Wizoo/Steinberg and AdrenaLinn Guitars for M-Audio), I've never had a situation like you describe unless I didn't set a parameter correctly, or didn't trim the clip properly.

thanks for the feedback guys, this is an issue because TS was able to recreate it and also confirmed it was an issue. 

The default BPM/Tempo was not configured correctly in the groove clip when converted. TS has confirmed that. I was on the phone with them for over 30 mins.
 
With that said, my original clip was 12 bars. 48 would be the correct beat according to the math. I wanted to make sure I was on the same page with what was the reference.  

I have snap set to measure, so I think it would be pretty difficult to goof the scissor cut trim to anything but a measure boundary. If this is not the correct thought for groove clipping, I have been using groove clips for many years incorrectly. I remember beta testing the groove clips and never had issues like this.
 
Midi groove clipping works correctly. Audio does not. After I experienced this, all versions of SONAR exhibit this behavior. So something got hosed in the shared folders or registry would probably be safe to say. Since TS has a valid recreate and the symptoms, I am hoping to hear from the bakers.
 
Again, I appreciate you guys chiming in.