pencilartist
Before you suggest I use CWAF, that's equally backwards, or worse. Why waste my time selecting every drive and folder other than the single one I want to clean? Isn't that sort of... silly?
I don't disagree that CWAF could use some updating, but just to clarify: You aren't selecting what to clean, you're telling it where
not to look for projects that might use the audio, and you only have to do it for the drive(s) you want to "clean". Unlike Clean Audio, it doesn't search outside the chosen drive(s).
If you only store projects on one drive, and have that drive halfway decently organized, it takes a couple minutes to tell SONAR what root folders to ignore, and then you never have to do it again unless you're constantly adding new paths off the root of your project drive, which would not generally be the case in a well-organized DAW.
I keep projects on two local drives (not including the external backup that is always "clean"). One of them has three directories excluded, and the other has four, including the "CWAF Excluded WAVs" folders (one on each drive) that I use to temporarily store discarded audio files after each "cleaning". I took very little time set that up, and I haven't had to touch the setup it for over a year. CWAF may
look clunky, but I find very simple and effective to use.
Sure a checkbox to "Only search this directory and subdirectories" would simplify the setup even more, but it would have to come with a very stern warning that this they could break projects stored elsewhere. And based on the number of posts over the years indicating that users don't understand that Clean Audio is looking for
projects, not audio, I would say that warning needs to be in bright red 24-point caps with at least three exclamation points and a disclaimer that Cakewalk is not responsible for lost audio.