projects / platform / upstream / gstreamer.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: cb225b3) | patch
Use the correct SSRC(s) when routing a RTCB FB FIR
authorJohan Sternerup <johast@axis.com>
Thu, 27 Oct 2022 15:30:28 +0000 (17:30 +0200)
committerGStreamer Marge Bot <gitlab-merge-bot@gstreamer-foundation.org>
Wed, 23 Nov 2022 11:31:23 +0000 (11:31 +0000)
commit9794c9bfd04216e293e695112522f07c13618abe
tree5762a7a890d388166983de8acf04493586da8a99tree | snapshot
parentcb225b3682b7e07bf286b73f9a0ef7e8c085b943commit | diff
Use the correct SSRC(s) when routing a RTCB FB FIR

Previously we tried to route an incoming RTCP FB FIR to the correct ssrc
using the "media source" component of the RTCP FB message. However,
according to RFC5104 (section 4.3.1.2) the "media source" SHALL be set
to 0. Instead the ssrc(s) in use are propagated via the FCI data. Now
a specific GstForceKeyUnit event is sent for every ssrc.

Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/3292>
subprojects/gst-plugins-good/gst/rtpmanager/rtpsession.c diff | blob | history
subprojects/gst-plugins-good/tests/check/elements/rtpsession.c diff | blob | history
Domain: Multimedia / Media Common;