Skip to content

rtpjitterbuffer: Use an extended RTP timestamp for the clock-base

It is compared to other extended RTP timestamps all over rtpjitterbuffer and since 4df3da3b the initial extended RTP timestamp is not equal anymore to the plain RTP time.

Continue passing a non-extended RTP timestamp via the sync signal for backwards compatibility. It will always be a timestamp inside the first extended timestamp period anyway.

Merge request reports

Loading