Topic: FFP verifier...updated screen shots

[blu666z]

I may be wrong though, but I just deleted the FFP file out of a show directory and ran TEST.  All files verified...would be hard to do without the FFP file if it is in fact comparing.

-Kevin

[blu666z]

Brian..would you minf expanding on the printout?  Anything you would like other than what is already shown in the results box?  Here is what I have so far:

FFP File » F:\SHN-FLAC\htbf2004-07-29-at943.flac16\htbf2004-07-29-at943.ffp.txt
   ----used to verify----
FLAC Directory » F:\SHN-FLAC\htbf2004-07-29-at943.flac16\


Total Files » 25
Files Verified » 24
Files Failed » 1
Files Not Found » 0
**************************
htbf2004-07-29-at943-d1t01.flac --> VERIFIED
htbf2004-07-29-at943-d1t02.flac --> VERIFIED
htbf2004-07-29-at943-d1t03.flac --> VERIFIED
htbf2004-07-29-at943-d1t04.flac --> VERIFIED
htbf2004-07-29-at943-d1t05.flac --> VERIFIED
htbf2004-07-29-at943-d1t06.flac --> VERIFIED
htbf2004-07-29-at943-d1t07.flac --> FAIL
htbf2004-07-29-at943-d1t08.flac --> VERIFIED
htbf2004-07-29-at943-d1t09.flac --> VERIFIED
htbf2004-07-29-at943-d1t10.flac --> VERIFIED
htbf2004-07-29-at943-d1t11.flac --> VERIFIED
htbf2004-07-29-at943-d1t12.flac --> VERIFIED
htbf2004-07-29-at943-d1t13.flac --> VERIFIED
htbf2004-07-29-at943-d2t01.flac --> VERIFIED
htbf2004-07-29-at943-d2t02.flac --> VERIFIED
htbf2004-07-29-at943-d2t03.flac --> VERIFIED
htbf2004-07-29-at943-d2t04.flac --> VERIFIED
htbf2004-07-29-at943-d2t05.flac --> VERIFIED
htbf2004-07-29-at943-d2t06.flac --> VERIFIED
htbf2004-07-29-at943-d2t07.flac --> VERIFIED
htbf2004-07-29-at943-d2t08.flac --> VERIFIED
htbf2004-07-29-at943-d2t09.flac --> VERIFIED
htbf2004-07-29-at943-d2t10.flac --> VERIFIED
htbf2004-07-29-at943-d2t11.flac --> VERIFIED
htbf2004-07-29-at943-d2t12.flac --> VERIFIED

Compiled by FFPVerify v0.1 Beta : 1/11/2005  9:28:26 PM

[blu666z]

OK....saving results to an external file is done.  You also have options to specify a default directory and save file name.  Gonna look at searching subdirectories but that may be a little more involved.  Lastly, you have the option of which reults are shown in the results.  ie.  You can choose to show or not show "VERIFIED", "FAIL", and "NOT FOUND" independant of each other.

Anything else?

-Kevin

[Brian Skalinder]

Good stuff!  I think as long as the "save the results" feature supports capturing any and all messages output by FLAC, then you've got it all covered!

OK....saving results to an external file is done. You also have options to specify a default directory and save file name. Gonna look at searching subdirectories but that may be a little more involved. Lastly, you have the option of which reults are shown in the results. ie. You can choose to show or not show "VERIFIED", "FAIL", and "NOT FOUND" independant of each other.

Anything else?

-Kevin

[blu666z]

At the moment, it will only output the results that you wanted to see in the RESULTS tab.   ie.  VERIFY, FAIL, and/or NOT FOUND.  Do you think all messages should be output to the file or only what you have asked to be shown on the RESULTS tab?

If nobody else has any suggestions, I'll go ahead and test this for another few days and then try to get it distributed. Maybe let you all test it for a while before passing it on to Etree for 'public consumption.'

-Kevin

[Brian Skalinder]

I guess I'd really like two different features:

[1] An option to display ALL messages in results.  If something goes whacky during en/decoding, I want to know precisely what happened, what the message is, so I can seek out a resolution online.

and

[2] The ability to write ALL messages from the results to a file for reference.

At the moment, it will only output the results that you wanted to see in the RESULTS tab.   ie.  VERIFY, FAIL, and/or NOT FOUND.  Do you think all messages should be output to the file or only what you have asked to be shown on the RESULTS tab?

[blu666z]

I guess I'd really like two different features:

[1] An option to display ALL messages in results. If something goes whacky during en/decoding, I want to know precisely what happened, what the message is, so I can seek out a resolution online.

and

[2] The ability to write ALL messages from the results to a file for reference.

Assuming I understand what you want, this exactly how it is designed to work right now.

On the options tab, there are three checkes boxes.
Show Verified
Show Failed
Show Not Found

ie.  If you only have Show Fail checked and all but one FLAC verified fine, the only output in the Results tab would be:
Total Files » 25
Files Verified » 24
Files Failed » 1
Files Not Found » 0
**************************
htbf2004-07-29-at943-d1t07.flac --> FAIL



Currently, the save file only contains what you have selected to be shown on the Results tab.  So if you wanted the save file to reflect the status of each file, you would check all three Show checkboxes and rerun the verification.  Or....I can change the code to always output the status of each file regardless of what you have asked to be shown in the Results tab.  Am I making sense or just rambling?

-Kevin

[Brian Skalinder]

Kevin,

Makes perfect sense, I like it the way you have it described.  I forgot this is simply an FFP verifier!  I was thinking of the sometimes funky messages I get  in the command-line logs left by FLACFrontEnd while actually en/decoding FLACs. 

It sounds like the only potential messages as a result of verification are:  VERIFIED, FAILED, and NOT FOUND.  In which case you've got it covered - good stuff!

I guess I'd really like two different features:

[1] An option to display ALL messages in results. If something goes whacky during en/decoding, I want to know precisely what happened, what the message is, so I can seek out a resolution online.

and

[2] The ability to write ALL messages from the results to a file for reference.

Assuming I understand what you want, this exactly how it is designed to work right now.

On the options tab, there are three checkes boxes.
Show Verified
Show Failed
Show Not Found

ie.  If you only have Show Fail checked and all but one FLAC verified fine, the only output in the Results tab would be:
Total Files » 25
Files Verified » 24
Files Failed » 1
Files Not Found » 0
**************************
htbf2004-07-29-at943-d1t07.flac --> FAIL



Currently, the save file only contains what you have selected to be shown on the Results tab.  So if you wanted the save file to reflect the status of each file, you would check all three Show checkboxes and rerun the verification.  Or....I can change the code to always output the status of each file regardless of what you have asked to be shown in the Results tab.  Am I making sense or just rambling?

-Kevin

[Tall Adam]

Kevin,

Makes perfect sense, I like it the way you have it described.  I forgot this is simply an FFP verifier!  I was thinking of the sometimes funky messages I get  in the command-line logs left by FLACFrontEnd while actually en/decoding FLACs. 

kinda off topic but...ever since ive started using wavelab to record and edit i keep getting messages when i encode to flac about "skipping unknown sub-chunk "PAD"" ive gotten this only on wavelab wavs. it doesnt seem to affect anything. is it simply something that wavelab puts in the metadata of its wav files? anyone know?

[Brian Skalinder]

ever since ive started using wavelab to record and edit i keep getting messages when i encode to flac about "skipping unknown sub-chunk "PAD"" ive gotten this only on wavelab wavs. it doesnt seem to affect anything. is it simply something that wavelab puts in the metadata of its wav files? anyone know?

I believe that's correct, yes.

[ChrisV]

kinda off topic but...ever since ive started using wavelab to record and edit i keep getting messages when i encode to flac about "skipping unknown sub-chunk "PAD"" ive gotten this only on wavelab wavs. it doesnt seem to affect anything. is it simply something that wavelab puts in the metadata of its wav files? anyone know?

Yeah, that is an annoying message.   What I do is convert the wav to flac and then back to wav again and dump the original wav.  Then I'll create my normal md5 file for archiving my edited masters.

[blu666z]

Here's a shot of the options if anybody needed clarification of earlier discussions.

-Kevin