If md5sum --check did not return an error with a truncated file, then
the file was likely broken to start with. I think the chances of a
corrupted file generating the same md5sum is close enough to 0 that you
will never see it in a life time.<br>
<br>
Also, you lost me on storing the md5sum value at the begging and the end?<br><br><div class="gmail_quote">On Wed, Jul 29, 2009 at 4:44 AM, Dat Head <span dir="ltr"><<a href="mailto:dathead2@gmail.com">dathead2@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Tue, Jul 28, 2009 at 3:02 AM, Brian Willoughby<<a href="mailto:brianw@sounds.wa.com">brianw@sounds.wa.com</a>> wrote:<br>
> "flac -t filename.flac" works perfectly.<br>
> It will detect a truncated file, missing pieces, jumps, and any other<br>
> mistakes I can think of throwing at it.<br>
<br>
</div>yes flac -t is a life saver because relying on md5sum --check to test<br>
against previously stored metaflac --show-md5sum is not sufficient,<br>
i have had files get truncated several times and pass that test but<br>
of course flac -t flagged them<br>
<br>
this made me wonder if maybe the checksum shouldn't be stored<br>
at the beginning and end of the flac file but maybe not worth it<br>
<br>
also, if you don't use md5check perl script you should!<br>
it recursively finds all md5 sigs in.txt files and checks them and<br>
does flac -t also - has saved me many times...<br>
<div><div></div><div class="h5">_______________________________________________<br>
Flac mailing list<br>
<a href="mailto:Flac@xiph.org">Flac@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/flac" target="_blank">http://lists.xiph.org/mailman/listinfo/flac</a><br>
</div></div></blockquote></div><br>