--- Sean Goller <[EMAIL PROTECTED]> wrote:
> Josh wrote:
> 
> > I use single file with embedded cue for CDs.  all my metadata is
> > in an external DB and I've been using custom s/w with a rio
> receiver
> > for playback.  now that I have a SB2 to play with I want to look
> > into how to do the same thing (even if it means I have to tag
> > the FLACs somehow).
> > 
> > Josh
> > 
> 
> 
> Hi Josh,
>       Would you be willing share a bit on how you've implemented this? 
> I'm 
> currently wrestling with how to store flac images in a meaningful
> way, 
> and hadn't considered external storage for metadata. What do you 
> actually name your images? Something human-readable, or something
> more 
> processing-oriented like the md5sum of the flac file? would you be 
> willing to share your schema?

I currently use mysql for the store.  CD primary keys are formed
from a custom 160 bit hash I compute from the CD TOC data.  it
is an SHA-1 digest of a message composed by packing as much bits
as possible from the TOC (including track type).  it's similar to
the musicbrainz/cdindex hash but uses more bits from the TOC to
further reduce chances of collision.

the schema is a little more complicated than id3v1 but less than
v2. I have mostly classical music so the main thing I wanted was
separation of performer and composer, multiple performers/composers
possible, hierarchical genre and mood, and keywords, and a simple
query language that uses it all for quickly composing dynamic
playlists (think "play all slow chamber music by j.s. bach random").

I was planning to release it as open-source but never got the whole
way through.  it's not in a shape to release, and metadata is a
personal thing; I was not sure that it would be as useful to anyone
else as it is to me.

Josh


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to