Bugzilla – Bug 1881
Enhancement: Support APEv2 Tags for MP3s
Last modified: 2008-09-15 14:38:10 UTC
SlimServer does not presently support APEv2-tagged MP3 files. I'm certainly not an expert on this, but these are the reasons why this might be a worthy enhancement: * Foobar2000, a very popular audio player among "audio enthusiasts", is using APEv2 as opposed to ID3v2 to tag MP3s in its standard configuration. For better or worse, it is often regarded as superior. --> APEv2 is much more stable in its specification than the ever-changing and often backwards-incompatible ID3v2. --> APEv2 tags are located at the end of the file. It is therefore not necessary to rewrite the whole file on changes (as is the case for ID3v2 if there's no padding). * I'm not a coder, but from what I gather APEv2 is far easier to implement than ID3v2. If Slimserver already supports it for MPC (where it is the standard), the work should be done already. If this is implemented, the user should be able to choose if Slimserver looks at ID3 or APE first, as two sets of tags can be present on a single file. APEv2 specification: http://wiki.hydrogenaudio.org/index.php?title=APEv2_specification
Created attachment 673 [details] APEv2-tagged MP3 file This sample file has APEv2 tags only. A combination of ID3v1 and APEv2 is probably more common.
should be sufficient to suggest that if a user decides to put APE tags in, that the intent is that those are read, same way that ID3v2 is set to override ID3v1. already too many 'options' littered all over the place. Plus, this is would match the way MusePack is handled. APE tags are merged over top of ID3V2, leaving any ID3 tags that are not overridden by matching APE tags. you are correct, AUDIO::APETags module is already included from CPAN, so it could be fairly straightforward, following the example in Slim::Formats::MusePack
This has been fixed in both the 6.2 and trunk trees. Will be in the 3/14/2006 nightlies