Clean Audio Folder...how much is it usable..?

Hello,
 
In all these years I used the 'Clean Audio Folder', to reduce disk data occupation...
How this feature is done, at least for me, it has a little flaw, the fact that projects to consider which file as used or unused must reside in the local system disk....
Here is my problem :
The PC where Sonar ( I still use X2 producer ) is installed has its own root folder under which all projects are developed and saved, an such a folder is 'backupped' each day, at least changed files are, automatically on a NAS, so that I have an exact restorable copy of the project realtime whatever it happens, even for files that may be wrongly deleted...
Now, once per week, the backup folder on the NAS is copied on a remote FTP for safety purposes, and here comes the problem...
The backup folder owns all the files for a project, from audio to projects, templates and so on, but it even holds temporary files like cut, edits, bad recordings and so on...
So, the Backup folder usually grows to about twice the size of the original folder owning all the original Sonar projects, creating a huge amount of unnecessary data to be eventually copied remotely...
If I use the 'Clean Audio Folder' feature of Sonar on such a NAS, Sonar, for the check, will consider only projects that are stored on the local disc, and, if a project has been removed from the disk to make more space, deleted for error or even just corrupted, but it is still present on the backup folder, well, results in the backup folder are the loss all its audio files, at least, for what I read on the online documentation for this command still now...
 
So, my question is :
Is still the 'Clean Audio Folder' working this way... ( it's 2 years since I am out of Sonar use )...?
And if so, why not making an option in this very useful function to select which folder to refer to for projects that may use such Audio files...?
Or, even simpler, why not making such feature looking from the selected folder locally down both for both audio and linked project files to make sure a folder would be consistent with itself both as audio and as projects...?
Eventually even an independent tool would be useful performing such an action, to make this very useful feature more usable...
 
I hope I have explained quite clearly what I mean...
 
Thanks,,,
 
Alex
 
 

Try Utilities > Cakewalk Audio Finder instead. Not perfect, either, but far more flexible and powerful in terms of what paths get searched, what it tells you about what it finds, and what to do with orphaned audio files.

If you have a bunch of co-mingled audio clips in a common audio folder, for multiple projects, I would suggest you start creating a separate new project folder for each project, then do a Save As with the option checked to copy all audio during the Save As, and that would build up each project folder to have a sub-folder called Audio with only the active audio clips for the project.
 
At the end of that exercise, every project would exist with its proper active audio clips, and I would think then that you could archive or even delete the original project folders and that giant massive mis-mash of co-mingled audio from that single audio folder.
 
Wouldn't the above be another approach to fixing the issue?
 
Bob Bone
 

Hi Alex.
 
I would strongly recommend adopting the procedures described by Robert above.
For backup purposes, you can simply drag & drop your entire projects folder to your backup drive of choice every day.
 
This folder should end up a LOT smaller once all your projects have been subjected to the "Save As" and the originals deleted.