You know, I want to like X3, but stuff keeps happening that really irritates me after I try to find features I like.
(UPDATES IN RED)
I have a guitar clip for use as a scratch take for a group to take home and work with. It is 96 beats long. I have the clip, decide to groove clip it. Groove clipping breaks down the clip to 64 beats. No problem. All the crap I went through trying to sync groove clipping reminded me that I could just change the beats on the clip. I change the beats to 96 and the whole clip gets deleted!!??!!.

Now, I did not find anything on search, but maybe something is there.
 
1. Create clip 100 beats long
2. Trim clip on both ends so that clip is 96 beats
3. Bounce to clip to remove the ends
4. CTRL-L - Groove clip enable the clip :Notice the clip goes to 64
5. Double click clip properties and change beats to '96' only and hit enter. (Do not change to 96:000)
 (turns out 'Beats' was 'clip length')UPDATE
At this point the clip is deleted no sound whatsoever. (clip should not have been deleted)UPDATE
 
For step 5, if I change the clip size to 96:000 and hit enter, the clip length changes to 27:704. Entering 96 gets the clip deleted again. (This behavior is weird regardless of what I was trying to do)
 
I am trying to do this with 3 other people in the room with me and they are asking what happened. Not cool to have SONAR behave this way. I was highly embarrassed. This is one of the MAJOR functions of SONAR and it does not work on my machine.
 
Right now, I see no way to groove enable this clip.
 
Thoughts and suggestions to remedy this? (a shot of something strong)
 
Updated title to refer issue in X3E although reported in X3c.

8.5 works flawlessly and X1-X3 crap out, as earlier reported, with bad results.

I'm not seeing a problem. I did a quick check of two different clips -  random length recordings in 4/4 time, ending at 26-27 measures edited down to 24 measures = 96 beats. Both defaulted to 128 beats when groove clipped, but after correcting them to 96 beats, all was well.
 
BTW, it shouldn't be necessary to bounce before groove-clipping; groove clipping will warn you it's discarding the hidden parts. But I did it both ways for good measure - no difference.
 
 

I think I have found the issue. I am not in the groove clip section of the clip view. I was changing the 'length' in the Properties view which is how I used to use this in 8.5. If the length values are not supposed to affect the beats and such, what use is the length feature at all during groove clipping?
 
So, #1 - Resolved as titled, but with a twist and a couple bugs I believe.
 
Using the Groove clip beats per clip got me what I needed. I hope this helps someone out because it just frustrated the heck out of me.

Guitarmech111
I think I have found the issue. I am not in the groove clip section of the clip view. I was changing the 'length' in the Properties view which is how I used to use this in 8.5. If the length values are not supposed to affect the beats and such, what use is the length feature at all during groove clipping?

 
I meant to ask you about that when you mentioned entering 96:000. As you noted, Length is in the general clip properties section, not the groove clip section. Changing it basically slip edits the end of the clip which will change the number of beats in the clip proportionally, but what you needed to do was change the number of beats by stretching, which is what the Beats in Clip value does.
 
All that said, it appears you've stumbled on an unrelated bug with the Length property. I also found that changing the length was giving bizarre results in clips over about 64 beats. A little investigation showed that values over 68:256 were being modded to that value. So entering 68:257 gives a length of 1 tick, 69:258 gives 1:002, etc.  And, surprise, surprise, 68*960+256 = 65536 = 2^16 ticks. Looks like they didn't declare a large enough data type to hold the total number of ticks when entering a value directly.

Thanks for checking Dave! You have pinpointed the 'sort of'.
 
I will report the error and get a ticket number back here.

I know this sounded familiar, so I was able to track down this thread from back in 2008 (starting at post # 9):
http://forum.cakewalk.com/Lack-of-understanding-heregroove-clips-m1296832.aspx
 
This seems to be the same core isssue/limitation, though I don't recall the specifics. 

I'm not sure where that idea of a 256-beat limit mentioned in the other thread came from. If that was ever true, it doesn't appear to be the case any more. I just created a 288-beat groove clip without a problem. The Beats in Clip did default to 256, but I was able to correct it to 288 without a problem, and it rolls out correctly.
 
Just to summarize, then, I'm not seeing any issues or limitations in creating long groove clips other than the mis-detection of Beats in Clip which is easily corrected in the Groove Clip section of clip properties. But if the length needs to be adjusted before groove clipping, it should be done by slip editing or splitting in the track view rather than by entering a Length in clip properties if the target length is over 68:256 beats.

Yeah, I'm not sure either, Dave.   It just seemed similar. 

In my use of the groove clips, I almost exclusively use them to repeat patterns from the point where the clip is created and not usually for converting, stretching or anything like that. I want to repeat patterns in a clip that I want to groove clip. It would be nice if you could confirm the number of beats in a clip before the groove process is executed. That way SONAR would produce exactly what the user expects and not have to go through any additional hoops to get what they desire.

Billy was a good bit of info. He is missed.