Petition to fix Bundle files

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.
 

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)

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.

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.

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.

yeah that is unfortunate

Yeah. Right!