AFAIK there is no information the failure rate is anywhere close to 1%. The current zeal on this subject has forced Cakewalk staff to correct misinformation in a recent thread http://forum.cakewalk.com/FindPost/3044959 . I am just suggesting based on what we really know, moderation in the message.

Wow, thanks for all the replies and help. 
 
Well, I finally figured it out, one little thing that Grem said that I missed was the "apply trimming" command, that seems to do the trick and now my 70gig file is only 600meg!!
 
Thanks

To shrink the new project try "apply trimming" to the clips.

Thanks Scook, just figured that out about the same time you posted!!
 
Again, thanks for all the help, it's great to have a place to get good help!

gbowling
Wow, thanks for all the replies and help. 
 
Well, I finally figured it out, one little thing that Grem said that I missed was the "apply trimming" command, that seems to do the trick and now my 70gig file is only 600meg!!
 
Thanks

Hmm. That's interesting. So, also when you cut you have to apply trimming? That's really easy to miss, isn't it? I thought you only need to apply trimming when slip editing.

Slip editing IS cutting. They both retain the full clip - just hide the portions you don't see. Bouncing or Trimming deletes the hidden portions so the clip is now WYSIATI (what you see is all there is).

Kalle Rantaaho

Grem

To OP, Cactus makes an very important point. You HAVE to save the new file to a DIFFERENT location for what is suggested to work properly.

 
 "Per Project Audio Folder" method sort of includes that, doesn't it?  If you change the name of the project and use Per Project Folder there's no other option than to save to a new location, ie. a new folder. 

Not necessarily.
 
You can do a save as "in place" i.e. within the current prject folder. I do this all the time when I've made or am about to make, a significant change to the project.
 
You must, as has been stated, choose a completely different location in order to discard the audio not referenced by the project

Cactus Music
I find it hard to swallow that any file format becomes corrupt if saved to a normal hard drive. Over the internet of course that's different. These people have all saved their work as a bundle on a hard drive, CD/DVD ROM or USB stick only to find they cannot open it latter down the road or at their friends house. Why?

Because all those storage media are capable of dropping bits. When you format a hard drive, it marks off the bad sectors and won't let you write to them. However, there's no guarantee additional blocks won't go bad over time. The surface of a hard disk is not immune to old age.
 
Flash RAM can lose cells. In fact flash memory has fairly complex data management schemes to avoid writing to the same areas over and over again, which wears the cells out and eventually causes failures. Optical disks are subject to a variety of problems, especially if stored incorrectly. CD-ROMs have had pinholes in the aluminum, and various other issues such as exposure to heat or ultraviolet light can corrupt data. Production runs of cheap optical discs can be bad and you won't know it until you try to retrieve a file years later. Blu-Rays are probably the most robust of the optical media but when you're storing 25 to 50GB on a disc, that's a lot to lose if there's a problem.
 
This is why I don't just save multiple times, I save to different media if possible. I also use offsite storage. I just gave 135GB of video backups on Blu-Ray to a friend who's involved in the company for whom I made the videos.
 
The only reason people freak about bun files, or zip files for that matter, is if one little thing goes wrong you can't recover the data. As a result, it's not the best choice for long-term storage. But it's a great choice for exchanging projects over the web. Right tool for the right job, and all that.