| Polyphony Suite Documentaiton | ||
|---|---|---|
| <<< Previous | Archiving | |
The plan is to have the catalogue server read both ID3v1 and ID3v2 tags but there will be no requirement to use of ID3. Because we have a tersely defined naming scheme for the MP3 files themselves, ID3 is of limited use, except the comment field (see below). Still, it is often convenient to at least fill out ID3v1 tags as many players recognize them, and seeing that the current track is "Dave Holland Quintet - Candlelight Vigil" instead of "Dave Holland Quintet##Prime Directive##07##Candelight Vigil" is kind of nice.
I hope to include a feature in the catalogue server to update the ID3 tags in a set of files based on the info in the catalogue server's database.
Some searching will be based on data retrieved from the ID3v1 comment field, OR the ID3v2 comment field (if present). The comment field will contain information about the ripping and encoding of the file.
Because ID3v1 sucks (to use the technical term), we only have 28* characters to play with for the comment, and we want to enter data like so:
[ripping software]##[encoder and switches]
When I rip and encode I use EAC and LAME respectively, so I would write a comment something like this:
EACv0.9b4##LAMEv3.92--r3mix
Even that small comment is 27 characters, which is a good illustration of the constraints of ID3v1.1.
* - Technically there could be 30 characters, but we'll assume ID3v1.1 which steals 2 bytes from the comment to support having the track number in the tag as well.
Good quick overview: http://www.id3.org/id3v1.html
More than you really want to know: http://www.id3.org/
| <<< Previous | Home | |
| Utilities | Up |