[Bug 694553] New: [adder] doesn't work after commit a86ca53

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Sat Feb 23 16:39:17 PST 2013


https://bugzilla.gnome.org/show_bug.cgi?id=694553
  GStreamer | gst-plugins-base | git

           Summary: [adder] doesn't work after commit a86ca53
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: notverysmart at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


After this commit:

commit a86ca535c88a604daa431b0bc1cf4cd8fbb2d100
Author: Stefan Sauer <ensonic at users.sf.net>
Date:   Thu Feb 21 08:15:45 2013 +0100

    adder: ensure sending a flush-stop after flush-start

    Previously adder was only sending the flush-stop, when it saw the flushing
seek.
    If one sends a flushing see direcly to an element upstream of adder, it
would
    fail to unflush the downstream pads.

the crossfading player pipeline in rhythmbox doesn't work.

This gst-launch line doesn't work either:
$ gst-launch-1.0 -v audiotestsrc wave=silence ! queue ! adder name=a !
audio/x-raw,format=S16LE,rate=44100,channels=2 ! audioconvert ! autoaudiosink  
uridecodebin uri=file:///path/to/file.mp3 ! audioconvert ! queue ! a.

It appears that elements downstream from adder aren't getting a new-segment:

WARNING: from element
/GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse:
Internal data flow problem.
Additional debug info:
gstbasesink.c(3234): gst_base_sink_chain_unlocked ():
/GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse:
Received buffer without a new-segment. Assuming timestamps start from 0.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list