[gst-devel] ffmpeg muxers - index not written in the result file

Wim Taymans wim.taymans at gmail.com
Tue Nov 25 12:27:03 CET 2008


On Tue, 2008-11-25 at 12:02 +0100, Julien Isorce wrote:
> Hi
> 
> I join to this mail a simple test.
> 
> The test demonstrates that when the pipeline is stopped when sending
> eos from the client code, then ffmux_asf does not write the index, so
> it's not possible to seek when playing back the result file.

You are not sending an EOS event but (forcefully) posting an EOS message
from the pipeline to the application.

> If I set num_buffers=N instead of sending eos, then the muxer write
> the index.
> 
> Yes it should be the same result because when GstBaseSrc reachs
> num_buffers_left = 0 then it return GST_FLOW_UNEXPECTED then an EOS is
> generated.
> 
> So something is not flushed when ffmux receive eos in the first way.

ffmux never receives EOS because there is no such event generated.

> 
> Is it a bug from gstffmpegmux or a problem in
> ffmpeg-asfmux-libavcodec ? or something else ?

It's a bug in the application.

Wim
> 
> ( ./test 0 rec.asf   -> index not written)  (eos sent from a
> g_timeout_add callback)
> ( ./test 1 rec.asf   -> asf correclty generated)  (use num_buffers=N)
> 
> Sincerely
> 
> Julien
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________ gstreamer-devel mailing list gstreamer-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gstreamer-devel





More information about the gstreamer-devel mailing list