Should you make another ffp to verify flacs before you burn them. Let's says you have a show whose ffps aren't archived on a site like etree. Should you make that extra ffp to ensure that nothing changed during the burning process, or does the test/full ffp vrf feature in TLH handle this for you?

I don't know if you understood my question. Let's say you make another ffp before you burn the flacs, but you don't burn that ffp to disc, only the original. Now after the discs are burned, should you use the ffp you made before you burned the flacs to verify nothing changed. I'd like to think all you have to do is run a simple test or full ffp vrf in TLH.

Is it even possible for a ffp to become corrupt during the burning process?

Is it even possible for a ffp to become corrupt during the burning process?

a ffp file is nothing else than a .txt file, with the flac fingerprints in it. should it get corrupt for some reason, you can simply open the ffp with notepad and copy the text into a new .txt file and then rename it to .ffp (e.g. rename 1991-02-02.txt to 1991.-02-02.ffp). all waht TLH is doing is comparing the chesums of the flac files with the ffp file, it's basicly reading the ffp of the .txt/.ffp. but well, the ffp files are tiny as nothing so there will be no way way they get corrupt during burning processes i think, and if they do than the whole disc will be fucked anyway...

I don't know if you understood my question. Let's say you make another ffp before you burn the flacs, but you don't burn that ffp to disc, only the original. Now after the discs are burned, should you use the ffp you made before you burned the flacs to verify nothing changed. I'd like to think all you have to do is run a simple test or full ffp vrf in TLH.

Is it even possible for a ffp to become corrupt during the burning process?

Oh, Ok. Yeah, it is possible for any file that gets burned to disc to be corrupted. Just double check the files you burned vs. the ones on your hard drive before you delete them off your hard drive and you'll be OK.

something to realize about FLAC and ffp is that every FLAC file contains one ffp checksum in its header. so testing a ffp just reads what's in the ffp file and compares it to what's in the header of each FLAC file in the list, without checking anything else. In order to truely check the FLAC files, test mode must be used, which decompresses the audio in each FLAC file and compares it to what it written in its own header as being the correct checksum. st5 also checks the decompressed audio data, but not against the checksum in the header but rather against what is written in the st5 file (which is a txt file like a ffp).

is that confusing enough?

in a nutshell, testing via ffp is not enouh, also use test mode on FLAC files, or test using st5 and ffp for full verification.

there's a tutorial in my signature that covers most of the nitty-gritty.

Modern social theory casts a highly skeptical eye on any declaration that a group of persons is without conflict, and insists, on the contrary, that conflict is natural to groups, and even more, is essential to them. -Patrick Henry

perhaps I didn't make it clear... ffp verification is of very little value for testing files, it is mainly a way of identifying filesets. if you want to test the files you burned you have to run either test mode or st5 verification (md5 will also work but is no longer in common use for audio sets).

Modern social theory casts a highly skeptical eye on any declaration that a group of persons is without conflict, and insists, on the contrary, that conflict is natural to groups, and even more, is essential to them. -Patrick Henry

perhaps I didn't make it clear... ffp verification is of very little value for testing files, it is mainly a way of identifying filesets. if you want to test the files you burned you have to run either test mode or st5 verification (md5 will also work but is no longer in common use for audio sets).

perhaps I didn't make it clear... ffp verification is of very little value for testing files, it is mainly a way of identifying filesets. if you want to test the files you burned you have to run either test mode or st5 verification (md5 will also work but is no longer in common use for audio sets).

After thinking about it...what is the point of having an ffp in your fileset? If you download a show and they test okay, well, doesn't that mean it's an exact set? The same for after burning your flacs, wouldn't they be exact if they tested o.k.? In your response you say a ffp is mainly for identifying filesets. Can't you just identify a fileset by the source info?

ffp is mainly for the convenience of viewing the contents of the FLAC headers of the fileset. st5 is really much better to include because it runs a full test when executed from TLH and while the formatting is different, the 32-character hash will be the same as what's in the ffp. st5 also works with SHN and APE, unlike ffp (this is also a key advantage over md5).

Modern social theory casts a highly skeptical eye on any declaration that a group of persons is without conflict, and insists, on the contrary, that conflict is natural to groups, and even more, is essential to them. -Patrick Henry

something to realize about FLAC and ffp is that every FLAC file contains one ffp checksum in its header. so testing a ffp just reads what's in the ffp file and compares it to what's in the header of each FLAC file in the list, without checking anything else. In order to truely check the FLAC files, test mode must be used, which decompresses the audio in each FLAC file and compares it to what it written in its own header as being the correct checksum. st5 also checks the decompressed audio data, but not against the checksum in the header but rather against what is written in the st5 file (which is a txt file like a ffp).

is that confusing enough?

in a nutshell, testing via ffp is not enouh, also use test mode on FLAC files, or test using st5 and ffp for full verification.

Quote:

Originally Posted by Five

perhaps I didn't make it clear... ffp verification is of very little value for testing files, it is mainly a way of identifying filesets. if you want to test the files you burned you have to run either test mode or st5 verification (md5 will also work but is no longer in common use for audio sets).

This is a very common misunderstanding if/when you're using Trader's Little Helper. If you've selected Full Verify in the Preferences section (this is the default setting in the lastest release, in the previous release you have to check the box on the Verify ... page) each flac file will be decoded, the fingerprint for the decoded audio data will be re-calculated, and the re-calculated checksum will be checked a) against the fingerprint stored in the header of the flac file and b) against the fingerprint given in the checksum file. So there is absolutely no need to test the flac files (testing a flac file means doing all the steps already done during verification, that is decoding, re-calculating the checksum of the raw audio data, and comparing the checksum to that stored in the flac file header).

Modern social theory casts a highly skeptical eye on any declaration that a group of persons is without conflict, and insists, on the contrary, that conflict is natural to groups, and even more, is essential to them. -Patrick Henry