Identity Element in silent=FALSE mode not printing anything

Sebastian Dröge sebastian at centricular.com
Wed May 7 12:36:39 PDT 2014


On Mi, 2014-05-07 at 11:34 -0700, renecalles wrote:
> Hi,
> 
> starting the app with GST_DEBUG=qtdemux:5 gives the following info:
> 
> 0:00:01.892847000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:6242:qtdemux_parse_samples:<demuxer> parsing up to sample 214
> 0:00:01.892882000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:6457:qtdemux_parse_samples:<demuxer> sample 214: index 214,
> timestamp 0:00:04.969070294
> 0:00:01.892904000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:6558:qtdemux_parse_samples:<demuxer> setting all keyframes
> 0:00:01.892918000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:4212:gst_qtdemux_loop_state_movie:<demuxer> pushing from stream 0,
> offset 1969131, size 11722, dts=0:00:04.960000000, pts=0:00:04.960000000,
> duration 0:00:00.040000000
> 0:00:01.909611000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:3696:gst_qtdemux_advance_sample:<demuxer> segment 0 ended 
> 0:00:01.909644000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:4212:gst_qtdemux_loop_state_movie:<demuxer> pushing from stream 1,
> offset 1980853, size 382, dts=0:00:04.969070294, pts=0:00:04.969070294,
> duration 0:00:00.023219955
> 0:00:01.909707000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:6242:qtdemux_parse_samples:<demuxer> parsing up to sample 215
> 0:00:01.909717000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:6457:qtdemux_parse_samples:<demuxer> sample 215: index 215,
> timestamp 0:00:04.992290249
> 0:00:01.909727000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:6558:qtdemux_parse_samples:<demuxer> setting all keyframes
> 0:00:01.909734000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:6606:qtdemux_parse_samples:<demuxer> parsed all available samples;
> checking for more
> 0:00:01.909740000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:5943:qtdemux_add_fragmented_samples:<demuxer> next moof at offset
> 0
> 0:00:01.909746000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:5946:qtdemux_add_fragmented_samples:<demuxer> no next moof
> 0:00:01.909753000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:4212:gst_qtdemux_loop_state_movie:<demuxer> pushing from stream 1,
> offset 1981235, size 410, dts=0:00:04.992290249, pts=0:00:04.992290249,
> duration 0:00:00.023219955
> 0:00:01.933154000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:3696:gst_qtdemux_advance_sample:<demuxer> segment 0 ended 
> 0:00:01.933181000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:4165:gst_qtdemux_loop_state_movie:<demuxer> all streams are EOS
> 0:00:01.933188000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:4299:gst_qtdemux_loop_state_movie:<demuxer> No samples left for
> any streams - EOS
> 0:00:01.933197000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:873:gst_qtdemux_push_event:<demuxer> pushing eos event on all
> source pads
> 0:00:01.933204000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:878:gst_qtdemux_push_event:<demuxer> pushing on pad 0
> 0:00:01.933216000 29212 0x7fa402100280 DEBUG                qtdemux
> qtdemux.c:878:gst_qtdemux_push_event:<demuxer> pushing on pad 1
> Received End-of-Stream Signal
> STOPPING Pipeline
> 0:00:05.067833000 29212 0x7fa401ce0b60 DEBUG                qtdemux
> qtdemux.c:1797:gst_qtdemux_reset:<demuxer> Resetting demux
> DELETING Pipeline
> DELETING Bus
> 
> 
> So, there is a "segment 0 ended" in the pipeline but no message sent.

If you look at the corresponding code in qtdemux (the one I linked in a
previous mail), you'll see that this means that qtdemux did not receive
a seek event with the SEGMENT flag set. It is going into the normal EOS
case and sends an EOS event downstream instead of posting the
segment-done message.

Check with the debug logs if it actually received the correct seek
event, and if it did why the flag is not set in the EOS handling code.

-- 
Sebastian Dröge, Centricular Ltd - http://www.centricular.com
Expertise, Straight from the Source
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140507/a7bd73ad/attachment.sig>


More information about the gstreamer-devel mailing list