X1c Clean Audio Folder STILL not working correctly

Clean Audio Folder STILL scans through every single directory, on every single mounted drive on my PC.
 
There is no reason for this. The audio path is explicitly stated in the form, and my settings declare I am using per-project audio folders.
 
Last night I installed X1c and, full of hope, I tested it.
 
When it starts, there is no way of stopping it. No Cancel button; nothing.
 
I sat there watching helplessly for a full 25 minutes as it scanned and scanned and scanned.
 
In the end, it found my Windows service pack .tpl files and said they were unreadable and were created by a different application. Why is it even looking in \Windows\ServicePackFiles\i386?
 
I do a lot of dragging and dropping of externally edited wav files and need to clean up regularly.
 
Yes, I know, creating a new project and copying is a workaround; but it would be so great if the Clean Audio Folder utility could finally be brought up-to-date.

I noticed this also. Rather strange.

This has been a problem for a seriously long time. I have always hated that. No matter what folder you point it at. It always does a full scan of the whole system. This should have been fixed way long ago even before X1c. 

Very frustrating if your have terrabytes of data over 2 or 3 drives.

Hope this is fixed soon, too!!

You'll notice that if you clean more than one project (one after another w/o closing Sonar completely )the scanning time is cut down substantially.

brundlefly


I agree it should be possible to limit where it looks, but understand that it is not scanning for audio files; it's scanning for project and template files that might use them.

I and many others have been using the copy-to-new-project workaround forever, with complete disregard for templates. If this is a worry to the bakers, they might provide a checkbox to allow users to include templates in the scan should they wish.

I'm guessing the Bakers figured they would get fewer support calls about how long it takes to scan, than they would calls about lost audio files if it only looked in the parent directory of the current path.

More likely it was written at a time where hard drives were far smaller, users were trying to save space and the scan was relatively quick.
 
This tool seriously needs to be brought in-line with modern hardware.
 
It needs:
 
1. an additional checkbox to enable/disable said template scan with a warning of the time required, and
2. a CANCEL button!
 
It should be fairly quick to program these.

brundlefly

I'm guessing the Bakers figured they would get fewer support calls about how long it takes to scan, than they would calls about lost audio files if it only looked in the parent directory of the current path.

Better slow than sorry. 

Come to think of it, I'm not even so sure about that!
 
The first two times this happened to me, I physically switched my PC off in panic because I thought a virus had gotten hold of my machine!
 
There is NO explanation offered to the user what it is doing (you can see the directories being scanned), and after at least 10 minutes of this, any normal user is going to start getting worried.

JazzSinger

brundlefly

I'm guessing the Bakers figured they would get fewer support calls about how long it takes to scan, than they would calls about lost audio files if it only looked in the parent directory of the current path.

Better slow than sorry. 

Come to think of it, I'm not even so sure about that!
 
The first two times this happened to me, I physically switched my PC off in panic because I thought a virus had gotten hold of my machine!
 
There is NO explanation offered to the user what it is doing (you can see the directories being scanned), and after at least 10 minutes of this, any normal user is going to start getting worried.

Maybe you're right about "normal" users. I'm probably abnormally calm and analytical about these things:


BrundleFly to self: "Sheesh, why is this thing scanning every folder on every drive... could something be wrong?" 


Self: "Think about it Brundle... SONAR is just checking everywhere to make sure the audio files in this folder aren't used by any project or template anywhere on the machine." 


BrundleFly: "Ah, of course. Thanks, Self! We should get together more often. How about we go out for a yummy cup o' Joe while this scan completes?" 






Incidentally, when drives were smaller, they and the PC's hosting them were also slower. Clean Audio has always taken a loooooong time.

Anyway: instead of whingeing, I'm going to enter a bug report.

@THambrecht: I want use your observation as part of my bug report, I hope you don't mind? I shall credit it to you.