I've already written a perl script for my own use that you might want to
take a look at. It doesn't even bother with id3 tags since I can't find a
decent editor/tagger that supports version 2 fully yet... it just pulls from
the pathname, an example for the beautiful south's "carry on up the charts"
disk's 1 and 2:
/usr/local/share/mp3/pop-folk/beautiful south, the - carry on up the charts
(disk 1)/
/usr/local/share/mp3/pop-folk/beautiful south, the - carry on up the charts
(disk 2)/
Since the id3v1 tag won't let me fully list "Carry On Up the Charts (Disk
1)" as an album name, both get listed under the same album in Obs, instead I
use a perl script that reads in the input from a:
find /usr/local/share/mp3/ -name "*.mp3" > addfiles.pl
And pulls apart the file and path names to get the required fields. And
since I use the:
artist - tracknum tracktitle.mp3
file format I even keep track of album order (something the current version
doesn't with it's renaming).
I'm more than willing to send the script, although I'm sure it could be ALOT
more efficent (it was my first effort with perl and I only spent a few days
on it)
The nice thing about this is though, I put this in a cron script along with
the removeempties and checkfiles scripts and my database is automatically
updated nightly even if I add or remove files from my directory (people add
via a SAMBA share which is much easier since we're pretty much all NT on
workstations).
I would however, love to go to id3v2 tag usage though as soon as a decent
editor/mass tagger is available as it would allow me to automate indexing
CD-ROMs of mp3's for the database much easier.
On a different note: Anyone know if there's a preset limit on the title
stream size? Quite a bit I get only my titles chopped off in streaming...
-F
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 27, 1999 6:31 PM
To: [EMAIL PROTECTED]
Subject: Database features
The code in CVS right now has features that allow a user to edit the
database information on the server. Right now the code does not change
the underlying filenames or directory names to reflect the changes in
the database. I will add code to make sure that it does that.
However, a few of you have asked for better support to work with an
existing MP3 collection. For instance, if I write a perl script that
will take a path argument from the command line, the script could
simply enter the necessary data records in the database, without ever
moving/renaming/duplicating the MP3 collection. The metadata (artist,
title, album, etc) could simply be plucked from the ID3v1|2 tags and
stuffed into the database. What should that script do with files that
have no meta data?
Would that do the trick? How about a script that takes the metadata
from the database and stuffs it back into the ID3v1|2 tags in the files?
Please help me define what these new scripts need to do and I will get
them written and after that I'll do a release.
If you have any thoughts on this, please share them with me.
--ruaok Freezerburn! All else is only icing. -- Soul Coughing
Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
