[Bug 747922] rtpjitterbuffer/rtxreceive: Don't reset the jitterbuffer if too old RTX packets arrive

[GStreamer (GNOME Bugzilla)]

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

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.5.1

--- Comment #14 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit c60038f188a1128d5cb6e981a690e09bba91f2ad
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Mon May 18 17:38:31 2015 +0300

    rtpsource: Queue bad packets instead of dropping them

    So we can send them out once we found the next, consecutive sequence number
in
    case one is following.

commit 9f18a271f31df65d4febef15af0c5be1c14a4a1a
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Mon May 18 17:38:14 2015 +0300

    rtpsource: Use g_queue_foreach() to unref all buffers in queues

commit 54e924332e2900f55298fe9f925acb9fbafff1ec
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Mon May 18 17:19:31 2015 +0300

    rtpsource: Refactor seqnum comparison code a bit

commit 1974b24ef4572ef30eb5556456a7dd29f74f4699
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Mon May 18 17:08:53 2015 +0300

    rtpsource: Allow sequence number wraparound during probation

commit 3386de7a8a765c4f750454888790415138c0805e
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Mon May 18 17:07:23 2015 +0300

    rtpsource: Make sequence number comparison code more readable

    ... by using gst_rtp_buffer_compare_seqnum() and signed integers
    instead of implictly using effects of integer over/underflows.

commit ca110fb0b838c49d31d44c2302b948de8ab01e08
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Wed Apr 22 18:54:06 2015 +0200

    rtpjitterbuffer: When detecting a huge seqnum gap, wait for 5 consecutive
packets before resetting everything

    It might just be a late retransmission or spurious packet from elsewhere,
but
    resetting everything would mean that we will cause a noticeable hickup.
Let's
    get some confidence first that the sequence numbers changed for whatever
    reason.

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

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