Cleanup webrtc:: namespace from leaked TimingFrameFlags
Bug: webrtc:9351 Change-Id: Ifbc0a522bf13ab62a2e490b9f129eacfabe7796f Reviewed-on: https://webrtc-review.googlesource.com/80961 Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23520}
This commit is contained in:
committed by
Commit Bot
parent
5352ad7928
commit
b6c462d4e4
@ -84,7 +84,7 @@ RtpFrameObject::RtpFrameObject(PacketBuffer* packet_buffer,
|
||||
_rotation_set = true;
|
||||
content_type_ = last_packet->video_header.content_type;
|
||||
if (last_packet->video_header.video_timing.flags !=
|
||||
TimingFrameFlags::kInvalid) {
|
||||
VideoSendTiming::kInvalid) {
|
||||
// ntp_time_ms_ may be -1 if not estimated yet. This is not a problem,
|
||||
// as this will be dealt with at the time of reporting.
|
||||
timing_.encode_start_ms =
|
||||
|
||||
Reference in New Issue
Block a user