[Bug 635020] Flushing everything on a discont produces worse result than just ignoring the discont flag

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=635020
  GStreamer | gst-ffmpeg | git

--- Comment #9 from Wim Taymans <wim.taymans at gmail.com> 2012-04-19 14:48:15 UTC ---
(In reply to comment #3)
> It depends whether the DISCONT means "some missing data skipped" or "completely
> unrelated data".  This is a difference that needs to be addressed in 0.11,

DISCONT on a buffer means that one or more earlier buffers are missing. It does
not matter if it is 1 buffer or unrelated data (= many,many buffers missing).
For new streams we have the STREAM_START event. For discont after a seek
(unrelated data in the same file) it usually should fall on a keyframe.

> preferably by a corrupt or missing data marker on buffers.  In particular,

There is a CORRUPT flag for buffers in 0.11. It is meant to be used when you
know that the data in the buffer could have errors, like when a checksum failed
or so.

In 0.11 there is also a RESYNC flag on buffers to tell elements that this
buffer is a good place to resynchronize against the clock. This is most useful
for raw audio where an audiosink ignores jitter in the timestamps to align the
samples.


> passing this information downstream allows better opportunities for
> reconstruction.

-- 
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.