Problem opening wavpack 4.22 files.

Bug #2469 reported by PsychoTrauma
4
Affects Status Importance Assigned to Milestone
gst-plugins-multiverse0.8 (Ubuntu)
Fix Released
Medium
Sebastian Dröge

Bug Description

Once the gstreamer-wavpack package was installed I tryed to open several different wavpack 4.22 encoded files with no luck. I tried with rhythmbox and totem-gstreamer but they couldn't be decoded. When I would try to open them with rhythmbox it would automatically close without error. I then opened rhythmbox with the cli and attempted to open a wavpack 4.22 file and got the following.

(rhythmbox:7064): Gtk-CRITICAL **: gtk_file_system_path_is_local: assertion `path != NULL' failed

(rhythmbox:7064): Gtk-CRITICAL **: gtk_file_system_path_is_local: assertion `path != NULL' failed
Segmentation fault

Revision history for this message
Sebastian Dröge (slomo) wrote :

This problem is on my todo list since some weeks already... I hope to get some time to look at it before breezy :/
But from a first look this seems to be a problem upstream... at least the wavpack cli tools that use the same libraries work so I suspect a problem at the gstreamer-plugin side...

Revision history for this message
Sebastian Dröge (slomo) wrote :

Can you please retest... it seems to work now in totem/rhythmbox... at least on i386

but gst-launch and gst-launch-ext don't want to play wavpack files so I filed a bug at the gstreamer bugtracker... maybe they can tell us something more ;)

Revision history for this message
PsychoTrauma (psychotrauma) wrote :

I just tested with a fully updated i386 breezy install and I still get the segmentation fault. I Did a fresh install with a nightly cd dated 09/25/05 so its five days old but I made sure to update everything before the test. If there is some instructions you could give me to get you more detailed information I would be glad to help.

Revision history for this message
Sebastian Dröge (slomo) wrote :

Can you upload such wavpack file somewhere so I can take a look at it?

Revision history for this message
PsychoTrauma (psychotrauma) wrote :

Here is a rapidshare link for one of the wavpack files.

http://rapidshare.de/files/5787410/04_-_1349_-_Deathmarch.wv.html

Revision history for this message
Sebastian Dröge (slomo) wrote :

Good musical taste :)
I'll take a look at it

Revision history for this message
Sebastian Dröge (slomo) wrote :

Ok, I can reproduce this... wvunpack works on that files so most probably broken gst plugin...
wvunpack and wavpack on this file again works too...

did you create the file? what settings for compression did you use?

Revision history for this message
PsychoTrauma (psychotrauma) wrote :

I ripped and encoded the album as a backup, and used -hm as the string. Thats high compression with md5sums embedded into each file. I tried running a file without the md5sums embedded but the results were the same. I'm glad to see another black metal fan btw.

Revision history for this message
Sebastian Dröge (slomo) wrote :

ok, I can easily reproduce this :/
it's the -h switch which causes the problems... I'll report upstream, hopefully we get this fixed for breezy

Revision history for this message
PsychoTrauma (psychotrauma) wrote :

I would have never guessed it was the -h switch. I'm glad you were able to pinpoint the problem and hopefully with that info it won't be to hard to fix upstream.

Revision history for this message
Sebastian Dröge (slomo) wrote :

Maybe you want to add a comment so they pay attention to that bug ;) Otherwise we won't get this fixed for breezy :(

http://bugzilla.gnome.org/show_bug.cgi?id=317774

Revision history for this message
PsychoTrauma (psychotrauma) wrote :

I added a comment but there wasn't much I could say that you hadn't already said.

Revision history for this message
Sebastian Dröge (slomo) wrote :

all wavpack related bugs shall be fixed with the gst-plugins-multiverse0.8 package I upload to dapper in a few minutes :)
please reopen otherwise

Changed in gst-plugins-multiverse0.8:
status: Accepted → Fixed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.