At 10:27 -0400 2001.10.19, Drew Taylor wrote: >Hmmm, according to tagged.sourceforge.net MP3::Tag "At the moment >ID3v1/ID3v1.1 and ID3v2.3 tags are supported".
Ah, OK. >I wonder if it would be >possible to borrow some of MP3::Tag's ID3v2 writing code. From my brief >reading of the docs, Tag does not have the writing limitations you mention >below. Are you interested in me looking into this further? Sure, go ahead. I can't give anyone much help, but let me know if you have questions. Or, you might want to consider looking into adding the support to MPEG::ID3v2Tag, and then making MP3::Info use that. With something so complex as ID3v2, consolidating the codebases is really valuable. I tried to get the various ID3vx authors together, but not much happened. >>MP3::Tag is OOP, while MP3::Info is functional (but supports a basic OOP >>interface for weirdos who want it). > >So I'm a weirdo. :-) Assuming I could come up with a useful API, are you >interested in adding to the OO functionality? I'd have to take a look at it. >So my final question is, should I even be bothering with having ID3v2 tags >in my MP3's? My primary box at home is Windoze and WinAmp supports ID3v2 >just fine. Thanks for your comments. The point is not that WinAmp etc. don't support ID3v2, but they don't (in many cases) support the latest ID3v2 spec, most MP3s don't have ID3v2 tags, and most clients don't support MOST of what ID3v2 is. There are dozens of ID3v2 tags predefined, and a given client will probably only support a small handful of them. I don't know how many clients support the advanced features of them, like compression of tags and Unicode (and I don't know if any of the MP3 modules handle that, either). Like I said, it is complex. :) -- Chris Nandor [EMAIL PROTECTED] http://pudge.net/ Open Source Development Network [EMAIL PROTECTED] http://osdn.com/
