[gst-devel] Ouyt of Order Timestamps

[Tim-Philipp Müller]

On Tue, 2010-06-08 at 09:58 -0700, Wes Miller wrote:

> I have a buffer probe on the src pad of a capsfilter.  In the callback I
> print out each buffer's timestamp.  The data is demuxed from a matroska
> contaner file and represents a recorded mjpeg 
> 
> Here is a sample of the listing where x is a counter incremented as each new
> frame is processed:

>      x = 1482  --->  4237392448l
>      x = 1483  --->  4269392448l
>      x = 1484  --->  7425152l
>      x = 1485  --->  40425152l
>      x = 1486  --->  75425152l
>      x = 1487  --->  208425152l
> (snip)
> Are the frames really this badly out of order?  Are the timestamps reliable? 
> Is there a pipe element that I need to add after the demuxer to reorder the
> frames?

MJPEG streams should not have out-of-order timestamps. Two things to
check:

1. Are the timestamps in the file really what you think?
   Maybe you are just printing the timestamps incorrectly?

   gst-launch-0.10 -v filesink location=... ! matroskademux name=d \
          d.video_0 ! fakesink

2. Are feeding buffers with good timestamps into
   matroskamux in the first place? Check by looking
   at the debug log, or add an identity element into
   a gst-launch pipeline and use gst-launch -v to
   make it print the timestamps of buffers passing
   through.

Cheers
 -Tim