One thing, though... Instead of database fields, would ID3 tag values be okay?

That idea has good points and not so good points.

I don't think any of the ID3V1 fields are "available" for this usage, at least not in my system, I use them ALL and would not willingly give any of them up.

However, there are 40-odd additional fields defined in ID3V2 (in addition to the 'V2 fields that duplicate the 'V1 fields) and I would be happy to sacrifice any of them. The down side being... there is no way to edit the data contained in any of those fields in emplode. This wouldn't be a deal-killer, though -- chances are, as Tony (the other Tony, not you) points out, these EQ presets would be applied an album at a time, and it would be easy to do so with MP3TS or a similar program. It does mean, though, that instead of just fixing and rebuilding the database to change the EQ settings of a song or group of songs you would have to delete those songs from the player, modify their tag information, and then reload them.

I could live with that.

tanstaafl.