[gstreamer-bugs] [Bug 338292] New: MAD plugin hangs when performing non-flushing seek.

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Wed Apr 12 19:36:14 PDT 2006


Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=338292
 GStreamer | gst-plugins-ugly | Ver: 0.10.2

           Summary: MAD plugin hangs when performing non-flushing seek.
           Product: GStreamer
           Version: 0.10.2
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-ugly
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: artfwo at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.11/2.12
   GNOME milestone: Unspecified


Please describe the problem:
I try to play a short fragment within an mp3 file. When I try to loop over the
fragment as recommended in
http://webcvs.freedesktop.org/gstreamer/gstreamer/docs/design/part-seeking.txt?view=markup
 (i.e. I issue another non-flushing seek immediately after catching
SEGMENT_DONE
message). I can watch the following behaviour:

* The fragment plays okay for some time
* A SEGMENT_DONE message is posted, buffered data continues to play.
* When time comes for the segment to start over, the plugin starts to spew out
tons of SEGMENT_DONE messages one right after another, until the pipeline is
stopped.

Steps to reproduce:
1. I'm going to attach a small python script (a cutout from my app) that can be
used to test segment-seeking behaviour. It can be used like this:
$ segment-test.py test.mp3 20 30 1

argument are:
<start_seconds> <stop_seconds> <loop = 0|1>

Actual results:


Expected results:


Does this happen every time?


Other information:


-- 
Configure bugmail: http://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