X1b groove-clipping bug

Activating Groove-Clip Looping on an audio clip is causing audio clipping and digital pops & noises that happen on transients. Deactivating Groove-Clip Looping and the audio clip is fine.

I also tried an alternative solution - by selecting the Groove-Clip activated loops on the audio track and chose Bounce To Clip to consolidate them into one continuous audio file. Doing that removes the Groove-Clip Looping of course, but all the noises still remain in the audio clip.

I'm doing a system restore to reverse the installation of the X1b patch to see if that will fix the Groove-Clip Looping issue and wait for the X1c patch

I tried that and it didn't fix the issue.

The same problem in happening in the media browser.

When auditioning a groove-clip/acidized audio file, I get the noises. But, when auditioning a non-groove audio file it plays fine.

I no longer use groove clips , 100% broken... I have done a simple test with x1 and 8.5.3 and 8.5.3 dose not have the same problems.. Anyone can do this pls try and tell me If Im nuts or not... 
 Take a loop from the included loops from Cakewalk/sample magic. copy it 14 times on 14 different tracks, groove clip it and pull it out 20 bars or so.. Click save and you will see it takes a few seconds to save,, Now take that same loop and copy it again 14 times but this time copy and paste it without groove clipping it then hit save .. Now it saves almost instantly , I do realize groove clipping has more information attached to it but this is ridiculous , 8.5.3 dosen't eat up that much resources .. I been running into intermittent problems with groove clipping.. Also I realize CW's Hotfix was to fix this issue and it has not... 

It actually looks like they somehow forget to translate between 32bit float and 64 bit float in there somewhere. The groove clipping engine is probably 32bits float internally and should be upgraded to 64 bit float or the translation might be sometimes not be active. The end result looks like they didn't change from offset binairy to sign & magnitude or something.

While we're speculating wildly about possible causes, I'm going to wager it's hardware- or driver-specific. If it were the kind of generalized bug you're describing you'd have far more participants in this thread, and there would likely be ten other reports that had preceded it. As it stands, you've already got two who can't reproduce a problem.

Does everyone with this groove clip noise problem have a Sandy Bridge and Windows 7 latest SP?

I was kind of wondering that myself.