Topic: Utliity to verify FFPs

[blu666z]

Gonna make a stab at knocking this out tonite..see if this makes sense.

User will point program to FLACs and corresponding FFP.  Hit verify and get a list of errors:  Records from FFP where FLAC file wasn't listed, FLAC listed w/o being in the FFP, and records where fingerprints didn't match.

-Kevin

[Chuck]

Sounds goiod to me.
I think something like this would be very useful.

[Ed.]

i'm guessing you'll need a seperate ffp.txt file to do the checking?  what if you put the ffp in the info txt file?

i think i'm confused about this, but once i see it in action i might understand it more.  this could be really helpful.

[blu666z]

Not fully functional yet, but getting close.  

Ed, the ffp in the text file would be a problem.  I might be able to parse it out somehow but there are no standards in how people would list them.  

-Kevin

[Ed.]

could you just make a new txt file and copy/paste out the ffp info from the info file?  seems like that'd be the easiest.  i usually just add the ffp in the bottom of the info, i guess i'll have to get into the habit of leaving it as a seperate file.

+t for this

[blu666z]

Ya the user could def create their own ffp file.  Its not directory specific the way mkw is.  ie.  You double-click an MD5 and it looks in the same folder for the shns.  Mine, you point it to the FLACs and then point it to an FFP and it will check them.  I'm just trying to get a base down right now but I plan on adding the ability to also have mulitple FFP files so you could check multiple shows at once.

-Kevin

[cpclark]

nice work so far kevin, cant wait to see the finished product and btw, i always create a specific txt file for the FFP

[mirth]

Umm... if you use the etree scripts, Caleb's md5check Perl script will check against a .ffp if one exists....

http://www.bklyn.org/~cae/md5check


The latest release of the etree-scripts package fully supports flac as well, even if the script name would lend one to think otherwise.

Here's the email sent to etree's announce list the other day:

         _                                     _       _
  ___| |_ _ __ ___  ___       ___  ___ _ __(_)_ __ | |_ ___
 / _ \ __| '__/ _ \/ _ \_____/ __|/ __| '__| | '_ \| __/ __|
|  __/ |_| | |  __/  __/_____\__ \ (__| |  | | |_) | |_\__ \
 \___|\__|_|  \___|\___|     |___/\___|_|  |_| .__/ \__|___/
                                             |_| V2.0

Announcing release 2.0 of etree-scripts, a set of (mostly) Perl
scripts that is of use to those lossless audio freaks (like myself)
who prefer to work from the command line.

Some important changes in this long overdue release:

* All new "flacify".  This program converts directories of WAV or SHN
  files to well-tagged, CD sector-aligned FLAC files.  Run on existing
  FLAC files, it adds/updates tags based on the show's info file.
  Seeders can use it to do their WAV > FLAC encoding and get tagging
  in the bargain.

* FLAC support is in all of the scripts now, even though their names
  might be "unshn" or "shn2mp3".

* Modularized the info parsing code that is the core of flacify,
  shn2mp3 and makehbx into a new Perl module called Etree::InfoFile.
  The parsing has been improved a great deal from the last offical
  release (1.4) and I hope others can make use of it.

* Added documentation to most of the scripts, resulting in
  man pages, and more detailed online help.

* Uses Perl's powerful Makefile.PL.  Simple installation (perl
  Makefile.PL; make; make install), better checking of dependencies,
  and numerous options for power users.  Debian packages also
  available.

* Portable.  Runs on Linux, Windows (Cygwin), MacOS X, *BSD, and
  anywhere else Perl and the lossless encoders (shorten, flac) have
  been ported.

Dist File: http://bklyn.org/~cae/etree-scripts-2.0.tar.gz
           http://etree.org/software/etree-scripts-2.0.tar.gz

Home Page: http://sourceforge.net/projects/etree-scripts/

Debian:    deb http://etree.org/debian unstable contrib
      _                      ____
  ___| |_ _ __ ___  ___ _   / /  / bt.etree.org
 / _ \ __| '__/ _ \/ _ (_) / / /   db.etree.org
|  __/ |_| | |  __/  __/_ / / /  wiki.etree.org
 \___|\__|_|  \___|\___(_)_/_/ forums.etree.org

--
Caleb Epstein |  bklyn . org  |   The more I want to get something done, the
    cae at    | Brooklyn Dust |   less I call it work.
bklyn dot org |   Bunny Mfg.  |                   -- Richard Bach, "Illusions"

[blu666z]

So should I hold off on this or is a GUI version still usefull?

-Kevin

[Brian Skalinder]

So should I hold off on this or is a GUI version still usefull?

-Kevin

As much as I love command-line utilities, gobs of people prefer GUIs.

However, I think the FFP verification functionality would be much better suited to including in FLAC FrontEnd than a standalone app.  Dunno if you're able to work with the FFE folks to make that happen or not, just a thought.  Either way, I bet people will use it.

[scb]

xACT has it built in  for us mac os x guys

[blu666z]

I'm gonna email the frontend guy and see if he has any plans to incorporate it into his.  Guess I'll hold off on mine until I hear back.  Maybe I'll move on to a utility to create text files if there is any interest in that.  Remember it being mentioned before but discussion kinda died.

-Kevin

[Cooker]

imo, people should always have a separate FFP file. as an etree shn admin, it's a royal PITA to cut them out of info files and paste them into separate files - also, it helps out server admins, and saves bandwidth as people aren't forced to download a fingerprint in the text file just to see source, setlist, etc.

nice work kevin, +T

[Ed.]

i never thought of it that way, i always thought i was saving bandwidth by not forcing people to download two things.  on etree it really didn't specify - said you could do it one way or the other.  i guess in the future i won't bother putting it in the source info and keep it seperate.

good deal.