[Bug 772646] rtpjitterbuffer: fix lost-event using dts instead of pts

[GStreamer (GNOME Bugzilla)]

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

--- Comment #10 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
I don't have the time for that at least in the next two weeks, and lots of
other bugs that are already piling up on my list, sorry.


But even if you can't actually cause problems here, you surely agree that
changing the jitterbuffer state based on such broken packets that we also drop
afterwards is less than ideal. It's going to bite us sooner or later and then
we'll have a difficult to debug problem somewhere.
But maybe that you can't make it fail now is an indication that the existing
jitterbuffer code is broken. Does your wrong packet go into the skew
calculation code, does it cause updating of the times in the jitterbuffer, and
are those times used then for the following packets? It might not have any
effect here because we only calculate the skew from the packets with the lowest
jitter (the window of packets there), and your packet is always at the very
top?

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