studley;264089 Wrote: > I looked through the code (gorgeous!) and it appears as if SqueezeServer > dosen't care whether it's 2.3 or 2.4. Cheers, D.
Yeah, I don't think SlimServer will reject an id3v2.4 native frame if it's found in an id3v2.3 tag. I transcode my Flac library into Mp3, using id3v2.3 tags for compatibility. It's mostly for use on my iPod, but I also take the Mp3 library to work and have another SlimServer running there using just Mp3 files. I have a transcoding script that takes Flac fields which don't have id3v2.3 native counterparts and just throws them into TXXX/whatever frames. So ARTISTSORT and ALBUMSORT and COMPILATION become TXXX frames. SlimServer picks them up as though they were freeform fields in Flac, Ape, Ogg files. The flexibility is very nice. It's a lot harder getting Mp3tag set up right if you're tagging both Flac files and Mp3s using id3v2.4. For most fields, you need to design actions that examine the file type (or extension) and use either the Mp3tag field name (knowing exactly what it maps to in either tagging system) or else use your own. PERFORMERSORTORDER will map to TSOP only in id3v2.4 tags. In id3v2.3 tags it becomes a TXXX frame. In Flac, it just remains the literal PERFORMERSORTORDER. So if you're writing id3v2.4, you'd use PERFORMERSORTORDER (TSOP) on Mp3s, but ARTISTSORT on Flacs. With id3v2.3, just use ARTISTSORT for both. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=42822 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
