Platinum freezes after creating CWB files

I am doing some long overdue bundling. My process has been this: open a project, save as CWB, then delete the original (I have Sonar do this). That all works fine (most of the time), but when I open the next project to work on it, I get trouble. The project typically opens, and it may even begin to play if asked to, but Sonar goes into the (not responding) mess, then I have to close it. Once I restart Sonar, I can go right on to the next file and it works fine.
 
At what step have I caused this freeze-up to happen, if it's indeed my own fault?
 
I have also determined this will not happen if I do not delete between songs.

Then if someone can move it, please do so.

Bundles I am making today reopen easily. I'm still able to open bundles made before Sonar.
 
But why would Sonar freeze after deleting the original project?

pencilartist
Bundles I am making today reopen easily. I'm still able to open bundles made before Sonar.
 
But why would Sonar freeze after deleting the original project?

That freezing is a mystery to me, but I would never trust only cwb-files in storing my projects. Then again, I have read many, many posts about freezing when exiting SONAR, but I can't recall ever seeing a clear answer to that issue.
 
The point is: If a bundle goes corrupt, your project is gone forever, if a cwp gets corrupt, you still have the audio
(if that's any comfort if your projects contain a lot of MIDI :o/)

Consider the scenario where your bundle contains a project with a call to a plugin that is not on the computer where you want to open it. And consider the not unheard of case, where that plugin is either a) no longer available anywhere in the version required, or B) you are no longer licensed to use it because your subscription has expired. The fact that you could open the bundle immediately after you saved it does not necessarily mean you will be able to open it in a couple of years. The bundle file is not a compressed format. You will save more space by zipping the project folder.

I don't think we should backup using the bundle format.
But I do use bundle files a lot, and again, only to shrink the size of the song down to exactly I need.
In the CWP format, things get stored after you edit, delete, bouncing, rebouncing, etc...
Even if I use the clean audio file, things were still there.
Only saving in the bundle file format will get rid of unwanted stuff.
But here is the catcher. right after I save the song to bundle, to shrink down the size of the file, I reopen it and save it in the CWP format into a new directory, then to an external USB drive, then reopen from the external drive twice just to be safe.
After CW came out with Per Project Folder, using bundle files might not be the safest way to backup your work.
Yes CW want us to use bundle to send a project back and forth, but you can achieve the same thing by compressing the whole folder using Rar, and then send it.
With bundle files, a single hiccup will stop it from loading.
I have not lost a single song in 10 years yet, using 3 external USB drives to backup. Talking about OCD. Ha ha.
dan
 

Its incorrect info that bundle files wont load if plugins are missing. The load is no different from CWP in this regard.
Regarding the hang is anyone can repro it or post a sample project well fix it.

Bundles files are great for portability. I use them on wetransfer.com all the time. And you know the person at the other end will have everything. It's quick and easy.

I don't see it as a storage medium.

If the bundle is still on WeTransfer that is ideal for troubleshooting. Can send Noel a PM with a link to it (if still there).