This strategy is fine for the final version but if you save multiple versions of your project as you work (I have 20 in my latest!) you'd have to do this for each version.  I like to keep the old versions just in case there is something I want to resurrect from them...

A simple "restrict to drive/folder" option would be all thats required...

I remember coming across this thread about 4 years ago and saying to myself, "I can't believe Cakewalk is still implementing this woefully inadequate (read, virtually useless) utility. The point is, I was saying "still" 4 years ago. Now I'm saying, "C'mon guys..." :-/

The only safe and reliable way I've ever been able to delete unused .wav data is to save each project...one by solitary one...along with it's audio data, to a new location and deleting the old projects along with their old data. 

It would be wonderful if there were a utility that:

1. Analyses each Cakewalk file & audio file in a user-designated folder path, or multiple paths (instead of every single freaking HD in your system)

2. ACCURATELY determines which audio files are orphaned from the analysed Project files...

3. And allows you to delete them...to the Recycle Bin for FREAK'S SAKE, not straight into oblivion like it currently does.

Is it too much to ask...seriously? If I'm way off here and somehow missed that the Clean Audio tool has been fixed or always worked in the 1st place, please please set me straight and show me how it really does what it's supposed to do. 

Cheers!  : )

Ok...sorry for my rant. And for resurrecting this ancient thread. I've been working with it all afternoon and the Clean Audio tool is not exactly useless. However, the fact that I've been working with it all after noon is a strike in and of itself. 

1. Although it does for some reason scan drives and partitions outside the Audio Path that you designate, it doesn't spend much time with them. The longest the scan took for me was about 2 1/2 min. So I can live with that...sorry Bakers.

2. It seems as though it is indeed quite accurate in determining which files are not used by any existing Cakewalk projects. Just be careful...if there are any samples or other audio files that aren't directly used in SONAR tracks, such as samples used by a plug-in (yes they shouldn't be there but if they are...) they will show up in the list...and not show up in their project if you delete them here.

3. However the 3rd issue is still a problem. Hitting the delete button hardly feels "safe" as the tool implies because once you hit the delete button, the files are history...they do not go to the Recycle Bin and if you make a mistake, it's file recovery (and prayer) time.  Bottom line....backup up your files...all the time actually, not just before using this utility. 

So i guess I set myself straight. The utility seems to work ok. Still it's a bit nerve racking; I think Cakewalk can do better.