You started with the data collection part of the problem. I see some interesting ideas in your proposal:
- capture the information about a composer once, including spelling. - capture the information about a composition once. - don't wire in the way this information is stored in tags. - capture the info about CDs in a format that is different from the CDDB/FreeDB format. So how will this information get into music files or player databases? Do we have to write new ripper s/w? If not, how do we interface to existing ripper s/w? (We might write some s/w that acts like a FreeDB server but how do we pass extra tag info like composer, comductor, work and performers through the FreeDB interface?) If we don't provide an interface to the riper s/w, how will we know where the ripper stores music files and what's in them? Do we have to write a tag editor? If not, how do we interface to existing tag editors? (This is somewhat like the ripper situation but the music files have already been stored.) Do we have to write a new player? if not, how do we get our info into the player? Or is it all in tags in the music files? If you have the disk ID that CDDB and FreeDB rely upon in each music file, a music player could look up the rest of the info in the database you propose without having to read all the tag information in the file. Bill -- Listener ------------------------------------------------------------------------ Listener's Profile: http://forums.slimdevices.com/member.php?userid=2508 View this thread: http://forums.slimdevices.com/showthread.php?t=19858 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
