Camilo Celis Guzman e4d8cda9a1 rtpvp8pay, rtpvp9pay: increment PictureID on FLUSH_START ... In recent versions of Chrome (M106) a change on their jitter buffer means that they are very susceptible to PictureID discontinuities. Then avoid at all cost resetting the PictureID. Moreover, according to the RFCs for VP8 and VP9 payloads; the PictureID can start off at any random value. So there is no logical problem of incrementing it here rather than resetting it, as long as it is a different PictureID. WebRTC's recent corruption issue: https://bugs.chromium.org/p/webrtc/issues/detail?id=15101 Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/4530>		2023-05-05 07:45:19 +00:00
..
check	rtpvp8pay, rtpvp9pay: increment PictureID on FLUSH_START	2023-05-05 07:45:19 +00:00
examples	jack: Dynamically load libjack at runtime instead of linking	2023-04-20 11:10:15 +03:00
files	qtdemux: Add audio clipping meta when playing gapless m4a content	2023-05-03 08:47:55 +00:00
interactive	tests: rename 'icles' subdir to be more descriptive	2022-04-14 11:57:11 +00:00
meson.build	tests: rename 'icles' subdir to be more descriptive	2022-04-14 11:57:11 +00:00