rtpbin/rtpjitterbuffer: Offsets timestamps based on RTCP in RFC7273 mode
In RFC7273 mode once the jitterbuffer is synced (media clock and offset), the timestamps are already mapping directly to the signalled clock's timestamps (adjusted to the pipeline clock).
The offsetting based on RTCP for either ntp-sync
or inter-stream sync will break synchronization afterwards.
The question is now how to handle this situation best:
- adjust everything in the jitterbuffer to only apply the offset if currently there is no RFC7273 sync happening?
- never offset timestamps if
rfc7273-sync=true
, even if the caps do not contain the required information or the clock is not synced yet - never offset timestamps if
rfc7273-sync=true
, even if the clock is not synced yet (but caps are containing all required information)
I think 1. would be the correct solution, but this also kind of ties in with the question whether packets should be forwarded at all before RFC7273 sync is actually happening.
CC @tpm