GNOME Bugzilla – Bug 540920
Editing metadata corrupts ogg files
Last modified: 2008-07-10 19:50:04 UTC
Please describe the problem: Banshee is corrupting my ogg files if I edit their metadata. If I turn the "write metadata to files" on from the preferences and edit the metadata of any ogg file in the library, the file will corrupt. Steps to reproduce: 1. Have an ogg file in the library 2. Edit some part of the metadata eg. song title or genre 3. Try to play the file with banshee or use ogginfo to check the file consistency Actual results: the file is corrupted and banshee (or anything else) can't play the file anymore. Expected results: The files shouldn't corrupt. Does this happen every time? yes, it does. Other information: Distribution: Gentoo The bug seems to be somewhat the same as this oldish bug in launchpad: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/194766
Created attachment 113690 [details] ogginfo logfile of noncorrupted file ogginfo log of a ogg file before banshee has edited the file
Created attachment 113691 [details] ogginfo log of the corrupted file This is the same file after banshee has edited it. The last warning message was repeating over and over so I cut ~500kb of it.
Which version of TagLib# (or taglib-sharp) are you using ? It looks like there was a bug in TagLib# that seems similar to the problem you're having. Could you try to reproduce your problem with TagLib# 2.0.2.19 or above ? The discussion about the TagLib# bug : http://forum.taglib-sharp.com/viewtopic.php?f=5&t=156 This bug might have re-appeared because banshee 1.0 doesn't bundle TagLib# anymore, it uses the version found on the system.
(In reply to comment #3) > Which version of TagLib# (or taglib-sharp) are you using ? > > It looks like there was a bug in TagLib# that seems similar to the problem > you're having. Could you try to reproduce your problem with TagLib# 2.0.2.19 or > above ? > > The discussion about the TagLib# bug : > http://forum.taglib-sharp.com/viewtopic.php?f=5&t=156 > > This bug might have re-appeared because banshee 1.0 doesn't bundle TagLib# > anymore, it uses the version found on the system. > I had TagLib# 2.0.2.0 which is currently the "newest" package available. I made a new ebuild for 2.0.3.0 and now banshee seems to be working correctly. I will take this forward to gentoo bugzilla so that the problem gets fixed in gentoo. You should probably update dependencies list at http://banshee-project.org/download/archives/1.0.0/ so that >=taglib-sharp-2.0.3.0 would be a dependency instead of 2.0?
(In reply to comment #4) > I had TagLib# 2.0.2.0 which is currently the "newest" package available. I made > a new ebuild for 2.0.3.0 and now banshee seems to be working correctly. I will > take this forward to gentoo bugzilla so that the problem gets fixed in gentoo. Thanks for letting us know. If you want, you could post a link to Gentoo's bug report for others to look at. > You should probably update dependencies list at > http://banshee-project.org/download/archives/1.0.0/ so that > >=taglib-sharp-2.0.3.0 would be a dependency instead of 2.0? Well, the dependencies to work at all are 2.0, but that's not the same thing as saying "please use 2.0.2.19 or greater to avoid a bug". Otherwise, when would you ever be able to set an appropriate dependency? :)
well, I can't argue with that. :) Anyway, below is a link to the Gentoo's bug report. The fix is already committed to portage tree. http://bugs.gentoo.org/show_bug.cgi?id=230465