"do-timestamp" leds to [ no 'moov' atom within the first 10 MB ] problem in pipeline
Ashish Kumar Mishra
ashish.kmishra at dexceldesigns.com
Tue Jan 5 05:17:29 PST 2016
Hi All ,
(w.r.t video playback , not considering the audio-video sync aspect as of
now )
1) Below is the pipeline ( actual implementation is in C code ) :-
filesrc -> qtdemux -> avdec_h264 -> videoconvert -> timeoverlay -> q1
-> avimux -> filesink
audiotestsrc -> capsfilter -> q2
2) Clock is set by gst_pipeline_set_clock(GST_PIPELINE (pipeline),
gst_system_clock_obtain())
3) Problem Statement :-
----------------------
a) filesrc ( "do-timestamp" = FALSE ) + audiotestsrc ( "do-timestamp" =
TRUE )
The created file seek bar plays for 2sec properly.
Then the complete playback "PAUSE" with seek bar buffers for next 3sec.
The complete file playback resumes. This continues for the total
duration of file.
b) filesrc ( "do-timestamp" = TRUE ) + audiotestsrc ( "do-timestamp" =
TRUE )
The pipeline fails throwing error
ERROR: from element /GstPipeline:pipeline/GstQTDemux:qtdemux0:
GStreamer encountered a
general stream error.
Additional debug info:
qtdemux.c(6065): gst_qtdemux_process_adapter ():
/GstPipeline:pipeline/GstQTDemux:qtdemux0:
no 'moov' atom within the first 10 MB
c) filesrc ( "do-timestamp" = FALSE ) + audiotestsrc ( "do-timestamp" =
FALSE )
Seems to play properly.
Could group member please provide some pointers as to what aspect of
buffer-time is the cause for (a) & (b)
Thanks ,
Ashish Kumar Mishra
--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/do-timestamp-leds-to-no-moov-atom-within-the-first-10-MB-problem-in-pipeline-tp4675118.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
More information about the gstreamer-devel
mailing list