JJZolx;154118 Wrote: > If SlimServer encounters an id3v2 tag that is written within an TXXX > (user defined) frame, will it recognize the tag just as if it were a > native frame?
Only certain tags will be recognised within the TXXX tag; it's really intended for extensions, rather than as an replacement for the native frames. I believe the JRiver media jukebox tags are recognised like this. JJZolx;154118 Wrote: > What if the tag written to the TXXX frame is a "freeform" tag such as > those normally encountered in Vorbis and Ape2 tags? For instance, an > Mp3 file has ID3v2 tags and has a COMPILATION=1 tag located within a > TXXX (user defined) frame? The only compilation tag that's recognised by SlimServer is the non-standard TCMP (or TCP in ID3v2.2 parlance) tag. This can be used to indicate a compilation; however it is NOT a standard ID3v2.x frame name. You may wish to contact the ID3v2 mailing list to see whether there's any movement (or opinion) on the state of that frame. JJZolx;154118 Wrote: > Does SlimServer distinguish between id3v2.3 and id3v2.4 tags? If a tag > defined only in the id3v2.4 spec (e.g. TSOP) is encountered in an > id3v2.3 tag, will it be recognized? If you do something which is outside of the scope of the specification you should expect undefined behaviour. In this case, the TSOP frame is - as you say - not present in ID3v2.3, and so you should expect undefined behaviour. Such a frame would have different semantics to that expected by ID3v2.3. An ID3v2.4 frame may have multiple entries delimited by nul characters, may use encodings 2 (UTF-16BE) and 3 (UTF-8), and changes the semantics of encoding 1 (UCS-2 and UTF-16 for .3 and .4 respectively - the difference really only being that of the lack of high surrogates in UCS-2, IIRC). Similarly, meaning of the flags differs between ID3v2.3 and ID3v2.4 - the most important of which is that the latter allows per-frame unsynchronisation, whereas the former must be per-tag. As such, dropping a ID3v2.4 frame verbatim on to ID3v2.3 files will not work. If, on the other hand, you were to just use TSOP within the limited realms of the ID3v2.3 specification with the correct flags, without multiple entries, and limiting yourself to encodings 1 and 2, then you may find that it works. It wouldn't be unreasonable for it to be rejected as invalid at this or any future point in time. -- gerph ------------------------------------------------------------------------ gerph's Profile: http://forums.slimdevices.com/member.php?userid=1819 View this thread: http://forums.slimdevices.com/showthread.php?t=29618 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
