[Bug 739868] rtpmanager: rtpjitterbuffer fixes and improvements

[GStreamer (GNOME Bugzilla)]

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

--- Comment #43 from Miguel París Díaz <mparisdiaz at gmail.com> ---
(In reply to Sebastian Dröge (slomo) from comment #42)
> (In reply to Miguel París Díaz from comment #40)
> > (In reply to Sebastian Dröge (slomo) from comment #38)
> > > See https://bugzilla.gnome.org/show_bug.cgi?id=747922 and
> > > https://bugzilla.gnome.org/show_bug.cgi?id=747919 for that specific bug.
> > > Please confirm that this is what you're seeing.
> > 
> > The main problem is that RTCP stats are reset into rtpsource
> > (https://bugzilla.gnome.org/review?bug=739868&attachment=290316).
> > 
> > The point is why RTP_MAX_MISORDER is 100, and not 500, 2000 or 3000?
> 
> Because even 100 is already very unlikely to be packet reordering. Changing
> that will only hide other problems, not solve anything.
> 
> Your problem is not packet reordering I think, but delayed RTX. See the
> other bug :) We should fix that better somehow than changing some magic
> number.
> 
Yes, I agree with you and I also think that it is a better solution.

> > Moreover, if the solution is based on RFC4588 (using rtprtxreceive and
> > rtprtxsend) we will keep the error if the peer does not support this RFC.
> 
> Well, you should not enable RTX if the peer does not support it.
The point here is that there are some clients that supports NACK but do not
implement RFC4588. So we should take into account this.

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