do a dry run especially for the freeware;
seeing the amount of "fixes" suddenly go down on my live library was terribly frightening.
I really need to know what will be changed where, my library is too large to let random software do something on it.
Nothing on this in many years but I was recently given the same shock when trying out Bliss. I believe the default, certainly for trial versions with 100 fixes, should be to touch NOTHING unless given explicit permission. I might not choose to "spend" fixes the same way, and while I would likely end up going unlimited, for those would buy fixes, which ones to expend should be their choice.
You can certainly change the folder that bliss monitors. That's a workaround I've heard from a few people: a 'staging' folder that people copy files into and out of that bliss monitors.
Could you copy say 10, or 100 songs into a different directory and run Bliss on that; then compare to your original files?
Ideally bliss would give you the ability to approve individual fixes. I realize this would no longer be fully automatic but there is still tremendous value in automatically finding uncompliant music and offering a one-click fix.
I like the idea of having the ability to check what changes would be applied to my music files before actually approving them. I took me ages to digitize my 500+ CD collection and I certainly wouldn't want to corrupt my work.
Fair enough Jeff. Actually, this is where I see the new activity stream work going (see http://www.flickr.com/photos/dan-gravell/5915273252/in/photostream ). I'm thinking the first time someone uses bliss, all the upcoming work is shown here for confirmation. Then, there's a 'latch' to automate all the actions, if that's what you want.
Obviously bliss's history is as a fully automatic tool - that's not something I would want to lose.