Jarsve

Problem is that the zipper chew through every audio file in the audio folder. I bet I have plenty of freeze track files not in use anymore. I bet a bundle file would use only the files needed to make the bundle file.

First use "Save As" with "Copy all audio with project" enabled to create a new project folder with only the audio referenced in the project.

Johnbee58
I just looked on a recent project I did and the file name for the project indicates it's a CWP, but it's in a folder that it made itself and has a folder named Audio.  Would this have everything needed to move to another machine if I chose to do so? 

Probably and more that you do not need. See my reply #11. It is possible to create a project that does not contain everything in the project folder but later versions of SONAR made it more difficult to do so. The default operation of CbB and recent versions of SONAR has all audio data in a per-project folder.
 

Johnbee58
What would be different if this was a CWB file?

Bundles are created from a project and its audio fildes. They cannot be used directly by the DAW but must be parsed back into project and audio files before it can be used by the DAW.

scook

Johnbee58
I just looked on a recent project I did and the file name for the project indicates it's a CWP, but it's in a folder that it made itself and has a folder named Audio.  Would this have everything needed to move to another machine if I chose to do so? 

Probably and more that you do not need. See my reply #11. It is possible to create a project that does not contain everything in the project folder but later versions of SONAR made it more difficult to do so. The default operation of CbB and recent versions of SONAR has all audio data in a per-project folder.
 

Johnbee58
What would be different if this was a CWB file?

Bundles are created from a project and its audio fildes. They cannot be used directly by the DAW but must be parsed back into project and audio files before it can be used by the DAW.

Glad to know this.  It seems to already be set up to the best of my advantage anyway.

i have a few bundle files from back in the olden days that became corrupted and are unopenable.  i wish there were a utility that would allow everything in the bundle file to open up, except the corrupted elements.

You can try to recover the audio by changing the bundle extension to wav, load the file into a project or wave editor and cut out the clips. Unfortunately, the project data is unavailable in a corrupted bundle.

yeah that is unfortunate

Jarsve
What I was thinking of in making a bundle 2.0 file is if the track contains plugins that is not in Cakewalks then freeze the track to the bundle file. Or If the frack has no plugins or just plugins from Cakewalk keep the track unfreeze. And maybe some way to select this in advance.

I see where you're going with this...not just a way to save Cakewalk projects, but a file format designed for sharing and collaboration. I think there's merit to your idea, but it would take a lot of thought to figure out the best way to do this. For example we have AAF and OMF; I think you're considering something more along those lines, but capable of transferring more project-specific data.
 
It would help if DAW mixers were treated more like plug-ins, with a standardized way of expressing levels, pan, buses, and sends. If Mix Recall was an industry standard, think how cool that would be!

Yeah. Right!