[Bug 752911] New: Regression: interaudiosink/src does not work with adder

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=752911

            Bug ID: 752911
           Summary: Regression: interaudiosink/src does not work with
                    adder
    Classification: Platform
           Product: GStreamer
           Version: 1.5.2
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: dustin at virtualroadside.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

This can be demonstrated with the following pipeline which works on gstreamer
1.4.5 (fedora 22) but does not seem to work consistently in gstreamer 1.5.2
(compiled from source, in uninstalled environment)

gst-launch-1.0 audiotestsrc ! interaudiosink interaudiosrc ! adder !
autoaudiosink

It appears that *sometimes* it doesn't fail in 1.5.2. But when it does, it
fails with:

$ gst-launch-1.0 audiotestsrc ! interaudiosink interaudiosrc ! adder !
autoaudiosink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Redistribute latency...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstInterAudioSrc:interaudiosrc0:
Internal data flow error.
Additional debug info:
gstbasesrc.c(2943): gst_base_src_loop ():
/GstPipeline:pipeline0/GstInterAudioSrc:interaudiosrc0:
streaming task paused, reason not-negotiated (-4)
Execution ended after 0:00:00.001261506
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Playing around with my actual code and the GST dot debug tool, it appears that
the adder ends up with a S16LE src pad and the interaudiosrc has a S32LE sink
pad, and that's why it fails. Not sure why the adder provokes it. Adding an
audioconvert element doesn't seem to make a difference.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.