id3 parsing

Hi all,

I just hacked a plugin for my mp3 player gadget (a matchbox sized
thingy which accepts mp3 over ethernet and plugs into my stereo). I 
initially though this must be an Output class plugin, but after some 
reading I discovered that an Input class would be closer (mimicking 
the tonegen and mpg123 ones).

Now, the question. What's the plan (if there is one) for ID3 parsing? 
Today it's linked to the mpg123 plugin, but that creates a rather tight 
linkage between that plugin for all sorts of tasks (opening sources, 
decoding them, (id3) tagging them etc). Wouldn't it be nicer if these 
tasks were split up into separate units? Or is that just wishful 
thinking from my side since i have to go copying the ID3 code now...

I noticed in the todo that there is/was ideas to separate out the 
decoder from mpg123 to the generic library, is that separation part 
of a larger plan?

Cheers,

/Anders