QUOTE (Synthetic Soul @ Mar 9 2006, 04:26 AM)
I don't know anything more about sn0wman's work than is visible in that thread. Why not PM him?
If MP3Tag can export the MD5 for any file (not just LAME-encoded files, as per LAMETag) then why not load all of your files into MP3Tag, and export a list.
When you want to do a compare reload all the files again and export another list. Then use a text file comparison tool like
WinMerge to spot any differences.
Depending on the MP3Tag report it's possible you may need to parse the reports first, to ensure that only the MD5 values may change (e.g.: if the report has the current date/time on each line).
It's an option. How would you like to see this process work?
Edit:
QUOTE (hsc @ Mar 9 2006, 12:21 PM)
I'm using mp3tag now for quite some time (great tool), but have never seen that feature. I just tried it and it seems to work quite well.
Can I/we see a small example of a report please? If it's HTML perhaps you could upload it to some free webspace?
MP3Tag can be customized and besides html you can also get a .cvs output style which makes parsing quite easy. With regard to the process/workflow I consider currently the following as an option:
(1) Use mp3tag to generate one reference md5 file (e.g. baseline.cvs ) per subdirectory. This would serve as a reference.
(2) For verifaction:
(2.1) Basicly repeat step (1) but with a different output filename (e.g. new.cvs)
(2.2) Start a tool (which needs to be written) which scans all subdirectories from a given starting point. For directories with a baseline MD5 file and a newly created MD5 file: Parse both and log an error message if there are diffs in the MD5 checksum.