[Bug 796382] flvmux: (too) easily produces backwards flv-timestamps

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=796382

Nicolas Dufresne (ndufresne) <nicolas at ndufresne.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #372387|none                        |rejected
             status|                            |

--- Comment #9 from Nicolas Dufresne (ndufresne) <nicolas at ndufresne.ca> ---
Review of attachment 372387:
 --> (https://bugzilla.gnome.org/review?bug=796382&attachment=372387)

This is not really a fix. I think we get in this situation because the mixer
let data go, on timeout, and the some "late" data comes in, and get pushed. If
we want to use that model, late is late, data need to be dropped then. When you
add latency, you move the timeout later, allowing a certain delay between a/v.
So, weigher we follow the paradigm, and massively drop, or just disable timeout
mode, but hacking the timestamp after, I don't agree.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.