[Bug 709965] matroskademux: block parsing/lacing issues generate GST_CLOCK_TIME_NONE timestamps

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=709965
  GStreamer | gst-plugins-good | git

--- Comment #14 from Sebastian Dröge (slomo) <slomo at coaxion.net> 2013-11-01 14:02:11 UTC ---
Please correct my statements below

(In reply to comment #13)
> Oops, had missed the line-prior assignment.  Correction:
> 
> On the file produced directly from GStreamer, once, at the start, when the else
> block is hit:
>  lace_time: 0.
>  Duration: 0

This should cause a timestamp of 0 for the first lace in the block, and
GST_CLOCK_TIME_NONE for the others

> On the same file, but with "--disable-lacing":
>  lace_time: 0
>  Duration: 0
>  ========================================
>  lace_time: 1000000
>  Duration: 0
>  ========================================
>  lace_time: 15000000
>  Duration: 0
>  ========================================
>  lace_time: 38000000
>  Duration: 0
>  ...

This should cause proper timestamps for all

> On the failing sample:
>  lace_time: 0
>  Duration: 0
>  ========================================
>  lace_time: 18446744073709551615
>  Duration: 0
>  ========================================
>  [prior block repeated x 6]
>
>  ========================================
>  lace_time: 185745408
>  Duration: 0

This should cause timestamps of 0, followed by GST_CLOCK_TIME_NONE, followed by
185745408


If any of my statements is not true, that should and can be fixed. The
GST_CLOCK_TIME_NONEs I mention can't be prevented by the demuxer and should be
filled by the decoder.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.