[Bug 745539] rtpjitterbuffer: Applying ts-offset to deadline timer can result in a stalled

[GStreamer (GNOME Bugzilla)]

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

--- Comment #6 from Jason Litzinger <jlitzinger at control4.com> ---
I can see how, in some modes, the buffers would be out of sync, but in mode 0,
where the timestamp is derived from the RTP timestamp directly (with ts-offset
applied to correct PTS), how would a long or short delay cause the buffers to
be out of sync?  

The timestamp should independent of the delay in that mode, correct?

Also, given the delay can be arbitrarily long, that will result in no data
flowing downstream for a potentially long time.  I've actually observed minutes
of valid data held up and later discarded.  That said, once the old data is
gone, everything is sync'd up as expected.

Regardless of the above, I suspect my understanding (which predicated the bug)
of the intended functionality is flawed.  Given that should probably be closed
as "Not an issue" and I have something more specific I'll open another bug.

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