Android: Use RTP timestamp instead of capture_time_ms_ in VideoDecoderWrapper.
capture_time_ms_ is always 0 for frames received from the network. This caused a bug because it was used as an unique identified. Bug: b/68271454 Change-Id: Ic4417a52e61cf2b0cd796a89207a90b603a16590 Reviewed-on: https://webrtc-review.googlesource.com/24940 Reviewed-by: Magnus Jedvert <magjed@webrtc.org> Commit-Queue: Sami Kalliomäki <sakal@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20837}
This commit is contained in:
committed by
Commit Bot
parent
1882d8509a
commit
ce86e2965c
@ -56,9 +56,10 @@ class VideoDecoderWrapper : public VideoDecoder {
|
||||
|
||||
private:
|
||||
struct FrameExtraInfo {
|
||||
uint64_t capture_time_ns; // Used as an identifier of the frame.
|
||||
int64_t timestamp_ns; // Used as an identifier of the frame.
|
||||
|
||||
uint32_t timestamp_rtp;
|
||||
int64_t timestamp_ntp;
|
||||
rtc::Optional<uint8_t> qp;
|
||||
};
|
||||
|
||||
|
||||
Reference in New Issue
Block a user