GNOME Bugzilla – Bug 317592
gst-launch-ext doesn't support wavpack
Last modified: 2005-10-02 12:54:45 UTC
Distribution/Version: Ubuntu Breezy Hi, wavpackdec segfaults on all wavpack files when used the following way: gst-launch-0.8 filesrc location="test.wv" ! wavpackdec ! osssink RUNNING pipeline ... Segmentation fault when running the following way it just fails: gst-launch-0.8 filesrc location="test.wv" ! wavpackdec ! audioscale ! audioconvert ! osssink RUNNING pipeline ... ERROR: from element /pipeline0/wavpackdec0: Internal GStreamer error: pad problem. File a bug. Additional debug info: gstpad.c(2562): gst_pad_set_explicit_caps: /pipeline0/wavpackdec0: failed to negotiate (try_set_caps with "audio/x-raw-int, rate=(int)8000, channels=(int)1, depth=(int)8, width=(int)8, endianness=(int)1234, signed=(boolean)true" returned REFUSED) ERROR: pipeline doesn't want to play. when running it with gst-launch-ext-0.8 the following happens: No suitable pipe found for extension wv. gst-inspect shows the following: gst-inspect | grep wavpack typefindfunctions: audio/x-wavpack: wv, wvp typefindfunctions: audio/x-wavpack-correction: wvc wavpack: wavpackparse: Wavpack file parser wavpack: wavpackdec: WAVPACK decoder and the funniest thing... totem/rhythmbox plays the file without problems
The correct pipeline to use is gst-launch-0.8 filesrc location=test.wv ! wavpackparse ! wavpackdec ! osssink wavpackdec only works with framed wavpack data, wavpackparse gets raw wavpack data and splits it into frames.
ok... sorry then :/ but why doesn't gst-launch-ext work?
added support for wavpack to current cvs. Closing..