First, many thanks to Kerry Hoath (and some to a friend who is not on this list, but mostly to Kerry) for help with my batch file question. It's working, pretty much, but I'm still tweaking it, and I'll share the results when it's polished to my satisfaction. Related question: according to the longer help file, if you use the "verify" option during encoding, flac checks its own work as it goes along, decoding the bit of flac data it has just calculated and comparing the results to the .wav data it had used as input. If you're going to run flac -t later to test the .flac file, isn't it redundant to have verification on during encoding? If you know (for example, if you encoded the file yourself) that -V was used during encoding and that flac reported "Verify OK," is there any reason to test the file?
--- "David W. Tamkin" <dattier@panix.com> wrote:> Related question: according to the longer help file, if you use the > "verify" > option during encoding, flac checks its own work as it goes along, > decoding > the bit of flac data it has just calculated and comparing the results > to the > .wav data it had used as input. If you're going to run flac -t later > to test > the .flac file, isn't it redundant to have verification on during > encoding?yep.> If you know (for example, if you encoded the file yourself) that -V > was used > during encoding and that flac reported "Verify OK," is there any > reason to > test the file?nope, unless you suspect the file of being corrupted some time after encoding. Josh __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
When I asked,
| > If you're going to run flac -t later to test
| > the .flac file, isn't it redundant to have verification on during
| > encoding?
Fearless Leader Ace Coalson responded,
| yep.
OK.
| > If you know ... that -V was used
| > during encoding and that flac reported "Verify OK," is there
any
| > reason to test the file?
| nope, unless you suspect the file of being corrupted some
| time after encoding.
Thank you. I've been doing both, so it would save time and cycles to do
only
one of them.
Additionally, Josh, thank you for using different terms ("testing" and
"verifying") for the two functions. Over in the Monkey's Audio
universe,
Matthew Ashland has dubbed both of them "verifying." I propose
further that,
when it comes to sharing audio in FLAC format, we use "validating" for
checking FLAC files against a file of MD5 sums and "certifying" for
comparing
the fingerprints of our tested FLACs to those posted by the seeder.