Closed GoogleCodeExporter closed 9 years ago
There are simply too many differences to make this sensible. ID3v2.3 writing
could not present anything like the same API (no multiple values, half the
frames missing). It would have to be an entirely new module, mutagen.id3v23.
But then, why bother? It's not like the world lacks ID3v2.3 writers.
Original comment by joe.wreschnig@gmail.com
on 26 Jan 2011 at 8:11
[deleted comment]
Most of the OSS libraries seem to be aimed at makers of Linux media player
software and as such most of the good ones I've seen have moved to v2.4 tags by
default. Sure there are libs that write v2.3 tags but then you need another lib
to do AAC, FLAC etc... and I thought this is what Mutagen was for - one
all-purpose audio tagging library?
I'm not making a media player but rather a web app that needs to tag files that
will be downloaded by users, many of them on Windows. Mutagen looked like a big
win as it's Python, like my app, and it's very nicely done but then I found
that Windows is really crap and I need to write old tags...
Anyway, sorry, it sounds like a lot of work, I thought maybe since you already
read 2.3 tags it might be a simple switch somewhere to enable writing them.
Original comment by e...@anentropic.com
on 26 Jan 2011 at 8:45
Original issue reported on code.google.com by
e...@anentropic.com
on 26 Jan 2011 at 1:07