Hi, 
 
A friend of mine created a bundle (cwb) file from a project in Sonar X2. I think he has X2 Producer.
I have Sonar X3 Producer on my computer (x3e build 352 - x64), and when I try to unpack the bundle using the default settings ("store project audio in its own folder" and "create one file per clip"), Sonar creates the project folder with an "Audio" folder inside of it and fills the Audio folder with 104 wav files, but it never creates the project (cwp) file; the cursor just spins indefinitely.
 
Is this a known issue, and does anyone know a workaround?
 
Thanks!
Jonathan
 
 

There isn't really a known issue with opening X2 bundles in X3 that I'm aware of, but bundle files in general have been known to be troublesome. The workaround would be for him to Zip the project file with its audio folder instead of saving as a bundle. Zip files are generally more reliable with the added benefit of being smaller due to using better compression.

Hi Brundlefly. Thanks for the response!
I don't think he uses per-project audio folders, so I don't know of any way for him to to zip up the project.
Any other ideas?
 
Jonathan

I would suggest he enable Per Project folders (at least temporarily), and save a copy to a new folder. Or, since you've apparently been able to extract the audio files successfully, you could copy them to a project folder on your system, have him send you just the CWP, and tell SONAR where to find the audio files when it reports missing files on opening.
 
But I would tell him to stop skinning that Woolly Mammoth for a minute, and enable Per Project audio folders. 

Saving a Per Project Folder is a one click action. When he does his "Save As" there is a checkbox in the save window. Check that, send it to a convenient location, bingo bango... done.
 
Then he can send that folder as is or zip/compress it and send it that way.
 
However... if you have X2 installed on your system open the .bun file in X2. That might open it more reliably then you can do your own Save As and open it in X3 or rebuild the project manually (the latter of which is what I usually prefer to do to get rid of the Bundle/old version critters that can make a project turn to poop).
 
 

I spoke to Cakewalk support and they helped me solve the problem, so I'm posting the solution here in case anyone runs into a similar issue.
What I did was to open the bundle file in safe mode by holding down the shift key.
When you do that, Sonar prompts you before loading each resource in the project, and you can figure out which one is missing. Turns out it was V-Vocal, which was dropped after X2.