[Bug 742141] New: pulsesink: writeable size will increase bigger than total buffer size if no data feed to pulse.

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Tue Dec 30 23:22:53 PST 2014


https://bugzilla.gnome.org/show_bug.cgi?id=742141
  GStreamer | gst-plugins-good | 1.4.1

           Summary: pulsesink: writeable size will increase bigger than
                    total buffer size if no data feed to pulse.
    Classification: Platform
           Product: GStreamer
           Version: 1.4.1
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: kevinbing.song at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Is it reasonable below writeable size will increase bigger than total buffer
size if no data feed to pulse?

        pbuf->m_writable = pa_stream_writable_size (pbuf->stream);

It will cause our use case fail. But alsasink no such kind of issue. Per my
understand, the total ring buffer size is the max value of the writeable size.
But pulse audio will increase the writeable size without limitation if pulse
un-corked.

Our use case is send EOS to audio pipeline when rewind playback. The pulse will
be un-corked as need provided clock. And the writeable size will increase. When
change to normal playback, the writeable size will huge and consume large mount
of audio data. It will cause pause pipeline fail as audio buffer come to audio
sink per one second (audio sample duration is 1 second) and audio sink haven't
blocked on audio ring buffer commit function.

-- 
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