I found this confusing section in the ID3V2.4.0 documents:
> TCON
> The 'Content type', which ID3v1 was stored as a one byte numeric
> value only, is now a string. You may use one or several of the ID3v1
> types as numerical strings, or, since the category list would be
> impossible to maintain with accurate and up to date categories, define
> your own. Example: "21" $00 "Eurodisco" $00
>
> You may also use any of the following keywords:
>
> RX Remix
> CR Cover
> This is confusing because it appear to syntactically conflict with the
previous standard.
In the id3V2.3.0 docs, it says:
> TCON
> The 'Content type', which previously was stored as a one byte
> numeric value only, is now a numeric string. You may use one or several
> of the types as ID3v1.1 did or, since the category list would be
> impossible to maintain with accurate and up to date categories, define
> your own.
>
> References to the ID3v1 genres can be made by, as first byte, enter
> "(" followed by a number from the genres list (appendix A.) and ended
> with a ")" character. This is optionally followed by a refinement, e.g.
> "(21)" or "(4)Eurodisco". Several references can be made in the same
> frame, e.g. "(51)(39)". If the refinement should begin with a "("
> character it should be replaced with "((", e.g. "((I can figure out any
> genre)" or "(55)((I think...)". The following new content types is
> defined in ID3v2 and is implemented in the same way as the numerig
> content types, e.g. "(RX)".
>
> RX Remix
> CR Cover
>
This seems closer to what our regexp programmer was trying to do, but
then he got it wrong. Or else old godfather got it wrong when it
encoded your 60's tag and understood it as (60)'s. I'll need to see the
file tags before figuring out which is wrong. But I'm pretty sure the
code is wrong in any case.
--
Michaelwagner
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
