Thomas Orgis

OK, I'll get into that then somewhen. About the placement: texts is for unique ID3 frame IDs, extra is for multiple TXXX that are distinguished by description. So that fits UFID, of which there could be many. The W URL frames should go into texts then, except for WXXX. Anything that is unique without description goes into the text array. I'll only have to think about hiding the additions behind an opt-in flag or not. I think clients should not be surprised by added text entries, but they might be...

Say, is there anything that speaks against just treating UFID frames like text frames? It doesn't have a language, but the owner/URL maps to a description and the content can just be a hex string for the up to 64 bytes. So mpg123-id3dump would print UFID description(http://musicbrainz.org) E7C22B994C59D9CF2B48E549B1E24666636045930D3DA7C1ACB299D1C3B7F931F94AAE41ED for a 36 byte identifier. The information would be stored, hex-encoded as text in either in mpg123_id3v2.text or mpg123_id3v2.extra. I'm...

So this is still on the list. I'll get around to it eventually.

SIZEOF_OFF_T assertion error with cmake, mingw32, and mpg123 as a subproject

got this in 1.33.4

Missing error handling of __wgetmainargs()

I think we handled this in 1.33.0.

error: Unknown mpeg MIME type text/html