I remember I used bundle files many years ago and bundle files made in cakewalk 9 can still be opened in CbB. I think this is a genius invention, but it has been neglected and forgotten. I think this could be the best way of sharing projects.
 
But what is not working good enough now?
What needs to be fixed?
 
For me the old bundle projects have worked like a dream. The only problem I can see it that it can be a little bigger in file size than mp3 files. But with mp3 files you lose tempo, markers, ability to edit midi. But bundle is a great way to take backup too.
 
What do you think?
Can it be fixed so the community embrace it?
 
If someone wants to cooperate on a song, he has no arguments by saying he don’t have Cakewalk now. Cakewalk is free. And for those using Mac. Who cares.

Bundles became redundant when per-project audio folders were introduced 14 years ago. Bundles are fine for sharing projects as long as audio snap data does not need to be shared. Bundles are not suitable for project archiving. Fortunately projects using per-project audio folders are suitable for archiving. The only reason the bundle function still exists is for backward compatibility.

The scarry thing is, would you want you audio to be compressed, uncompressed, re compressed and re uncompressed? I'm not sure what happens to audio when you save as a bundle but if the file size is smaller then something bad just happened to your audio. All these people now recording at 96Hz it would certainly be pointless. 
 
To share songs you can make a version of your project that is smaller buy keeping as much as possible midi. 
You can even convert real drums and bass to midi if need be. 
All you want from the other person is for them to say add a lead guitar part, then all they need is a basic version of the song. 

scook
Bundles became redundant when per-project audio folders were introduced 14 years ago. Bundles are fine for sharing projects as long as audio snap data does not need to be shared. Bundles are not suitable for project archiving. Fortunately projects using per-project audio folders are suitable for archiving. The only reason the bundle function still exists is for backward compatibility.

To echo what Steve says...if you zip a per-project folder, you basically have what a bundle did except that unlike a bundle, it includes all information about a project.

Cactus Music
The scarry thing is, would you want you audio to be compressed, uncompressed, re compressed and re uncompressed? I'm not sure what happens to audio when you save as a bundle but if the file size is smaller then something bad just happened to your audio. All these people now recording at 96Hz it would certainly be pointless. 

There is no compression used in the bundling process. Here is Noel's explanation of the process. I believe a new project file is created for the bundle which could reduce the size of the product file. These files are usually not very big but have occasionally been blown out by excessive amounts audio snap data. Bundling and unbundling use to be recommended as a way to repair these projects.

scook
There is no compression used in the bundling process. Here is Noel's explanation of the process. I believe a new project file is created for the bundle which could reduce the size of the product file. These files are usually not very big but have occasionally been blown out by excessive amounts audio snap data. Bundling and unbundling use to be recommended as a way to repair these projects.

So, is there a point in finding a work around there? Or is the Zip file way better?
 
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.
 
Or even a way of rendering Just the plugin sound beside the clean audio if there is plugins outside cakewalk standard, so you have the clean track and the plugin sound when opening the bundle.
 
A fast way of sharing the project to others via BandLab. Like you can select the receiver in Cakewalk, and the file uploads immediately to a shared cloud project. Of course this needs to be optional.
 

JarsveOr is the Zip file way better?

ZIP file is better, 7-zip is the tool you need https://www.7-zip.org/

pwalpwal

JarsveOr is the Zip file way better?

ZIP file is better, 7-zip is the tool you need https://www.7-zip.org/

Wow my install file for 7-zip was 10 years old. Had to look up the newest one.
Here is my numbers out of using 7-Zip on a project folder:
Standard Project folder: 1,46 GB (1 572 429 381 byte)
Zip file standard format: 486 MB (509 972 480 byte)

I forgot to put in that this was the standard settings of 7-Zip. And you can be fooled by zip files if you don’t check at file size after zip file is done. This was at the "normal" settings. made a new file after posting with the "uncompressed" setting, and the file is the same size 1,46 GB (1 572 466 688 byte), as the folder.
 
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.

Forgive me if this was addressed in another thread or part of this one, but I'm a bit confused on the difference between the two.  Whatever I have mine set to, when I start a new project and name it, a folder is created in Cakewalk Projects which has the project as it was last saved along with an audio folder.  When (or if) I record audio, that is automatically put into the audio folder and subsequently linked to the audio track in the project.  I don't know if this is a CWP or a CWB, but I always assumed it was a bundle because it's automatically "bundling" everything I need to back up for the project.  A few years back I bought the computer I'm using now and had to transfer the Sonar X3 Studio projects from my previous PC to my new one.  I moved the folders that I made (bundles, I assume) on the old PC from that to the new one and when I went to open them in the new one they opened fine.  All the audio was linked and ready to go. 
 
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?  What would be different if this was a CWB file?
 
Thanks for the education.
 
John B.