Removed _completeFrame since we never allow incomplete frames.
In the old jitter buffer the two VCMVideoProtection modes |kProtectionNone| and |kProtectionFEC| could be set on the jitter buffer for it to not wait for NACK and instead generate incomplete frames. This has not been possible for a long time. Bug: webrtc:9378, webrtc:7408 Change-Id: I0a2d3ec34d721126c1128306d5fad88314f8d59f Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/190680 Reviewed-by: Kári Helgason <kthelgason@webrtc.org> Reviewed-by: Sami Kalliomäki <sakal@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Commit-Queue: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32513}
This commit is contained in:
@ -488,9 +488,7 @@ int LibvpxVp8Encoder::InitEncode(const VideoCodec* inst,
|
||||
downsampling_factors_[number_of_streams - 1].num = 1;
|
||||
downsampling_factors_[number_of_streams - 1].den = 1;
|
||||
}
|
||||
for (int i = 0; i < number_of_streams; ++i) {
|
||||
encoded_images_[i]._completeFrame = true;
|
||||
}
|
||||
|
||||
// populate encoder configuration with default values
|
||||
if (libvpx_->codec_enc_config_default(vpx_codec_vp8_cx(), &vpx_configs_[0],
|
||||
0)) {
|
||||
|
||||
Reference in New Issue
Block a user