GNOME Bugzilla – Bug 711437
apev2mux: should not put APEv2 tags at beginning of WavPack files
Last modified: 2014-12-12 16:44:06 UTC
I have been testing Banshee 2.6.0-2linuxmint1 and found that WavPack files created from CDs contain APEv2 tags at the beginning of the files. This is counter to the WavPack specs and causes the files to be unplayable on players that use FFmpeg (like VLC) and most other software (except Banshee). Players that use libwavpack directly can play the files because it skips the tags, but does not recognize the tag data at that location. Please see section 4.0 of the WavPack format documentation at http://www.wavpack.com/file_format.txt - here is an excerpt: "Both the APEv2 tags and/or ID3v1 tags must come at the end of the WavPack file, with the ID3v1 coming last if both are present." I have also filed this bug against Banshee, but believe that it is using apev2mux to place the tags here, so am filing this against GStreamer as well. Thanks!
This should hopefully fix it: commit 023a1637d941bfa22377c89287fb45edcaab4051 Author: Tim-Philipp Müller <tim@centricular.com> Date: Fri Nov 28 13:12:46 2014 +0000 apev2mux: write APE tags at end for wavpack files http://www.wavpack.com/file_format.txt: "Both the APEv2 tags and/or ID3v1 tags must come at the end of the WavPack file, with the ID3v1 coming last if both are present." WavPack files that contain APEv2 tags at the beginning of the files are unplayable on players that use FFmpeg (like VLC) and most other software (except Banshee). Players that use libwavpack directly can play the files because it skips the tags, but does not recognize the tag data at that location. https://bugzilla.gnome.org/show_bug.cgi?id=711437
Cherry-picked into 1.4 branch.