Set frame timestamps in MediaPipeline
Categories
(Core :: WebRTC: Audio/Video, enhancement, P2)
Tracking
()
People
(Reporter: dminor, Assigned: dminor)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Bug 1515205 has a quick fix to set frame timestamps in VideoStreamEncoder::OnFrame. The proper place for this is in VideoConduit.
|
Assignee | |
Comment 1•6 years ago
|
||
I think MediaPipeline makes more sense now that I've had a closer look.
|
|
Assignee | |
Comment 2•6 years ago
|
||
In the past we relied upon ViEEncoder::OnFrame to set the render time for
frames. With the branch 64 update, this code moved to
VideoStreamEncoder::OnFrame, and only sets the timestamp if it is greater than
the current time. This results in broken rtp timestamp estimates in the rtcp
sender report, which causes problems for Meet and possibly other services
that rewrite rtp timestamps based upon the sender report.
This patch explicitly sets the timestamp in MediaPipeline. This should give us
the same behaviour that we had before the branch update without requiring local
modifications to upstream code. This leaves the rtp timestamp as zero as that
was not being set before.
This also removes an unused overload of the VideoFrameConverted method.
|
||
Updated•6 years ago
|
|
||
Comment 4•6 years ago
|
||
| bugherder | ||
Description
•