From: TP Diffenbach <rockbox_at_diffenbach.org>
Date: Fri, 19 Dec 2003 11:45:31 -0500

The Id3 business would be a bit kludgy. There's no tag for config
information, but there are tags for volume adjustment and equalization.
There are also user-defined tags, so we could use simple name/operator/value
tuples in a string, e.g., "v*1.1;b=5;t-1" ("Increase volume by 10 percent,
set bass to (absolute) level five, decrease treble by one point" (in real
life I doubt I'd use relative adjustments to treble, but this is an
example)).

As far as MS-Windows tag editing software, Mp3BookHelper supports (I think)
all text tags, at least, and the author (Vlad Scharansky) has been very
generous to me in the past as far as adding additional tags.

-----Original Message-----
From: owner-rockbox_at_cool.haxx.se [mailto:owner-rockbox_at_cool.haxx.se]On
Behalf Of Michael Hentschel
Sent: Friday, December 19, 2003 10:54 AM
To: rockbox_at_cool.haxx.se
Subject: Re: Enqueing all types.


Sounds good. Would encoding into the id3 tag require some kind of special
id3 editor or could this be done in, say, winamp or so? I'm no id3 expert,
so I only know those "normal" parameters like title, artist, etc.

mike

> Easy. When an mp3 is loaded, read it's associated cfg file, if any. To
> associate cfg files to mp3s, we could:
> look for a .cfg in the same directory with the same file name as the
mp3,
> or
> look in the mp3's id3 information for the file name of the .cfg, or
> directly encode configuration options in an id3 tag.
>
> If we did not find a .cfg associated with the file, we'd look for a .cfg
in
> the directory with the same name as the directory; we could keep ascending
> to parent directories until we found a .cfg (and obviously this would
> benefit from intelligent "caching", or really remembering whether we'd
> already looked above a certain directory).
Received on 2003-12-19