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.

GuitarMech, you are not alone. I noticed this one time in X3a, but I was in a hurry and it wasn't important for me to research at the time.
 
I always meant to get back to figure out what happened, but your description exactly matches my experience.
 
Thanks for sticking with Tech Support on this one. I owe you!

You are very welcome.  :)

Guitarmech111
What do you use to determine what the beats are? I never had to worry about that. This usually always worked for me.

it all depends on how many beats are in your groove clip ?
that's how many beats.
if its 2 measures then 2 measures = 16 beats.
in your other case, 48 beats would = 6 measures.
 
what I find is when groove clips get in to the higher regions, like 32 or more, they have to work harder to analyze your clip.
this is where things can sometimes be harder for sonar to figure out.
 
its actually a very complex function when you think of it. back in the day I would use rex files.
you would have to do a lot more work back then, so I am a bit forgiving towards the process because I know how far it has come and the amazing things it can do.
but sometimes it needs help because the part is complex. 
 

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.

Hi Grem, ... feel free to ignore either my edit or my instructions... or both ... or neither   I started to write my reply, then went to dinner, then came back and submitted the post, then saw brundlefly's and many other replies having the matter well in hand.
 
Bill B.

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.

For future reference, setting snap to measure may not be enough to prevent off-measure snaps, culprits being other landmarks and magnetic strength setting. What relation this may have to wrong grooving, I don't know. The occasional wrong beat counting has been there in the last 8 versions I have owned, so I don't think your install has gotten suddenly corrupted.

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

I solved your main problem in the other thread you posted on the same subject, but just for reference (and this may also explain why MIDI and audio "drift out of sync" for some people), it's actually VERY easy to goof the scissor trim cut because Sonar defaults snap to Snap to Nearest Audio Zero Crossings, which may or may not be exactly on a boundary. 
 
In fact...I just confirmed that unchecking Snap to Nearest Audio Zero Crossing (under Preferences > Customization > Snap to Grid) does not persist. So even if you uncheck it, if you close the project and open a new one, the new one will have that preference checked. 
 
I'm going to put in a request with Cakewalk that this setting persist from project to project. Anyone who does sample-accurate loop edits will thank me if it's implemented