I need to clean this project page up. There are 9 songs of 45 tracks each all laid on the time line like a giant roll of tape.  I've been recording at one location and bringing home entire 1gb.  dump of say all of the vocals for the album. then I reimport the track into my master mixing copy of the album. It's been growing and growing after every recording session. I need to do some kind of save as in a separate folder so I can clean this up and have it make clips of only the files that I'm currently using. (I don't need copies of the scratch tracks that deleted months ago) I know to possibly save it as a bundle or something but I'm not quite sure exactly what to do. Once everything is finally recorded then I'm going to split the songs up and mix each on their own.,but for now this is how we are recording as the mics are already setup and all I have to do is arm the tracks and hit record.
 

Hi. What I would do is "save as" to a new folder, and make sure to copy audio with project. This should get rid of the excess files, and cut the size of the project down. Hope it helps.
All the best. 

Thanks! If I'm only using one 30 second piece of audio from a 45 min clip. Will the rest of the audio be copied over to the new save? Or will the clip be clipped down to a 30 second size?
 

You may also want to try Anderton's Week 70 Tip of the Week to see if it could help.
http://forum.cakewalk.com/FindPost/3329517

In the Save as dialog there is a box at the bottom to save each clip as a file. This will remove data outside clip boundaries so only the clips visible are the actual waves. This DOES prevent future slip-editting outward on each clip though, since there is no data there anymore.

mettelus
In the Save as dialog there is a box at the bottom to save each clip as a file. This will remove data outside clip boundaries so only the clips visible are the actual waves. This DOES prevent future slip-editting outward on each clip though, since there is no data there anymore.

Is that for certain mettelus?  I thought that saving as a Cakewalk Bundle file was the only way to delete hidden data by saving compacted audio while 'save as' actually kept whole referenced files. 
Happy to stand corrected though if I'm wrong. 

It should be possible to Bounce to Clip (or Apply Trimming, I forget the difference) all the slip-edited files before doing the Save As operation, and that will mean the reference to the longer takes is now gone.

tenfoot

mettelus
In the Save as dialog there is a box at the bottom to save each clip as a file. This will remove data outside clip boundaries so only the clips visible are the actual waves. This DOES prevent future slip-editting outward on each clip though, since there is no data there anymore.

Is that for certain mettelus?  I thought that saving as a Cakewalk Bundle file was the only way to delete hidden data by saving compacted audio while 'save as' actually kept whole referenced files. 
Happy to stand corrected though if I'm wrong. 

A clip is a "window" into the underlying wav file, so unless bounced one-by-one, an entire 45min wav is "needed" even for only a 30s window. The issue with a track bounce, is that all of the silence between clips becomes a wav as well. Even "Remove Silence" does not bounce anything, it simply slides clip boundaries to the settings chosen in the Remove Silence dialog.
 
I ran a test a year or so ago about "Remove Silence" which actually did nothing to underlying wav files, and the "solution" there was to Save As with "Create one file per clip" checked. The recipe is here to prove to yourself.
 
To the point with bundles... bundles DO strip out FX region and I believe also AudioSnap transient markers, so this will make the cwp file itself smaller, but AFAIK does nothing to the underlying wav files referenced by the project. Another advantage to a bundle is that during the unpack portion it can place the wav files closer together on the hard disk to cut down on disk read times (if they were originally all over the place).
 

gokidsmusic
You may also want to try Anderton's Week 70 Tip of the Week to see if it could help.
http://forum.cakewalk.com/FindPost/3329517

I wanted to second this.  Anderston's tip here is fantastic.  As are many of them. But this one can take a bloated project and very quickly cut it back to size.  Keep one of teh old copies, and you can always recover the full clips.

mettelus

tenfoot

mettelus
In the Save as dialog there is a box at the bottom to save each clip as a file. This will remove data outside clip boundaries so only the clips visible are the actual waves. This DOES prevent future slip-editting outward on each clip though, since there is no data there anymore.

Is that for certain mettelus?  I thought that saving as a Cakewalk Bundle file was the only way to delete hidden data by saving compacted audio while 'save as' actually kept whole referenced files. 
Happy to stand corrected though if I'm wrong. 

A clip is a "window" into the underlying wav file, so unless bounced one-by-one, an entire 45min wav is "needed" even for only a 30s window. The issue with a track bounce, is that all of the silence between clips becomes a wav as well. Even "Remove Silence" does not bounce anything, it simply slides clip boundaries to the settings chosen in the Remove Silence dialog.
 
I ran a test a year or so ago about "Remove Silence" which actually did nothing to underlying wav files, and the "solution" there was to Save As with "Create one file per clip" checked. The recipe is here to prove to yourself.
 
To the point with bundles... bundles DO strip out FX region and I believe also AudioSnap transient markers, so this will make the cwp file itself smaller, but AFAIK does nothing to the underlying wav files referenced by the project. Another advantage to a bundle is that during the unpack portion it can place the wav files closer together on the hard disk to cut down on disk read times (if they were originally all over the place).
 

Thanks Mettelus. I had know idea that bundles didn't trim down hidden audio! That will teach me to take it's 'writing compacted audio' dialogue at face value. 
 
I just ran a few tests and was really surprised to discover that no saving method actually applies slip edits and trims down the data. You live and learn:)