We did just added an option to suppress the file creation of bryston db, but many people do find it handy even if there using a 3rd party client. Those that find it hand its usually because a consistent file name for the cover art hasn't been used, the Bryston DB automates this task. It also makes the copied cover art a consistent size that most would consider ideal for browsing, this has generally increases the performance. For those that want to get rid of those extra files that why we created librarydoctor.php
Cheers,
Chris
Sure, Chris, as mentioned in my post.
Why don't you point the creation of these bryston files to the scratch drive, or the internal user drive, or, if it must really be elsewhere, on at least a separate Bryston folder on one of the user drives. It used to be that way didn't it?
That way one can 1) keep the data drives clean from anything else but Data/Music, 2) use these folders without issues by other programs/apps, and 3) be assured they will never be compromised by image creating software as an extra but ever so important bonus.
There really shouldn't be any files created by the managing software in these folders. Only content. Imagine all apps doing so
.
Cheers,
Marius