[Bug 711593] [rtpjitterbuffer] receiving a not very old packet could make it unnecessarily reset

[GStreamer (bugzilla.gnome.org)]

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

Wim Taymans <wim.taymans> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |NOTABUG

--- Comment #2 from Wim Taymans <wim.taymans at gmail.com> 2013-11-11 15:41:49 UTC ---
I would prefer not to change the behavior of this check. We currently do it
like suggested by the spec.

The idea is that in a typical network, you can't have packets being reordered
100 seqnums, this is only based on network conditions and has nothing to do
with jitterbuffer size. 

Changing this would, for example, cause problems with very high rate streams,
like uncompressed video. In those cases, the seqnum wraps around in 0.5 seconds
and the check against the oldest packet would not make sense anymore because
you could have multiple wraparounds in the buffer.

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