Lost video

[Ian Davidson]

Further investigation - it seems that alsasrc is creating audio buffers 
each with a timestamp of 0.  I have run alsasrc -> audiorate -> wavenc 
and alsasrc -> wavenc and both show this timestamp.  alsasrc does not 
appear to log any debug information.

This timestamp means that audiorate drops all buffers after the first 
since all the subsequent ones are seen as duplicates.

I do not know whether avimux gets upset by receiving timestamped video 
but audio with a timestamp of 0.

Is this a bug on the part of alsasrc or a feature?

Ian

On 19/01/2013 16:31, Ian Davidson wrote:
> I have done some analysis of the trace from Attempt 4, Outcome 1 in 
> the document I attached previously.
>
> Execution ended after 1819237914 ns.  In that time, I noticed that 
> avimux logged "gst_avi_mux_do_one_buffer:<mux> selected pad audio_0" 
> 174 times, and each time the given time was 0:00:00.000000000 .  In 
> the same time, 'do_one_buffer' was called for the video pad 27 times, 
> starting at 0:00:00.6307555650 and ending at 0:00:01.669455512.
>
> It seems to me that the video data is getting passed through with a 
> timestamp for each 'packet', but that the audio stream does not have 
> an incrementing timestamp.
>
> Could this be causing the problem?
>
> Ian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20130120/a5e37682/attachment.html>