GNOME Bugzilla – Bug 709886
"pitch" plugin prevent pipeline creation
Last modified: 2013-10-12 22:57:01 UTC
After GStreamer upgrade to 1.2 version using "pitch" plugin cause me a pipeline error, I've try with many different configuration, but nothing to do. Using this simple pipeline "audiotestsrc ! audioconvert ! pitch ! audioconvert ! alsasink" with "gst-launch-1.0 -v" the output is: ##################################### Setting pipeline to PAUSED ... Pipeline is PREROLLING ... /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0.GstPad:src: caps = audio/x-raw, layout=(string)interleaved, rate=(int)44100, format=(string)F32LE, channels=(int)1 /GstPipeline:pipeline0/GstAudioConvert:audioconvert0.GstPad:src: caps = audio/x-raw, layout=(string)interleaved, rate=(int)44100, format=(string)F32LE, channels=(int)1 /GstPipeline:pipeline0/GstAudioConvert:audioconvert0.GstPad:sink: caps = audio/x-raw, layout=(string)interleaved, rate=(int)44100, format=(string)F32LE, channels=(int)1 ERROR: from element /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0: Internal data flow error. Additional debug info: gstbasesrc.c(2865): gst_base_src_loop (): /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0: streaming task paused, reason not-negotiated (-4) ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... /GstPipeline:pipeline0/GstAudioConvert:audioconvert0.GstPad:src: caps = NULL /GstPipeline:pipeline0/GstAudioConvert:audioconvert0.GstPad:sink: caps = NULL /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0.GstPad:src: caps = NULL Freeing pipeline ... ############################# I'm currently using Arch Linux, and unfortunately I've failed using gdb for retrieve more information.
I can reproduce, this is a regression from 1.0, we should fix it
Actually was a regression from 0.10, fixed in 1.0, 1.2 and master commit 0587ab41b4f9979e9cfc11011ed5c970569ee3d3 Author: Olivier Crête <olivier.crete@collabora.com> Date: Sat Oct 12 16:04:25 2013 -0400 pitch: Fix inverted condition in setcaps
Re-milestoning to next "current stable" release - we don't know if there'll be another 1.0.x.