[gstreamer-bugs] [Bug 504642] mpeg2enc deadlock

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Tue Mar 4 09:59:05 PST 2008


If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=504642

  GStreamer | gst-plugins-bad | Ver: 0.10.14

Mark Nauwelaerts changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manauw at skynet.be




------- Comment #6 from Mark Nauwelaerts  2008-03-04 17:59 UTC -------
The situation described above is predictably outlined in
http://gentrans.sourceforge.net/docs/head/manual/html/howto.html#sect-mpeg-encoding

To elaborate here; (at present) mpeg2enc does not put timestamps on its output
buffers.  avimux tries to do the best it can with this, and assumes that these
buffers provide some sort of codec/extra-data and makes sure these go in first.
Unfortunately, in this case, it never stops.  So avimux keeps on "pulling in
video" from the input file.  This creates a huge video/audio imbalance (that
can carry on as long/large the queues can handle it) which will eventually
block the pipeline.  As such, actually, the video content grows and grows,
regularly emptying the video queues in between, whereas the audio queues will
grow and grow and never be emptied.  And indeed, whatever output may have been
made should only contain video.

mpeg2enc can not really be blamed either (well, you might :) ), having no
"official" libmpeg2enc specs telling it what to do with provided output
(AFAIK?)  So, that only leaves some hope and the work-around given in URL
above, or using mpeg2enc updated with the patches in bug 520329, which does
make some effort at providing output timestamps.  Tests then show it does
generally work out well  (though don't know about the particular input file).


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=504642.




More information about the Gstreamer-bugs mailing list