Erik Språng c8fbd899bd Fixes temporal rate allocation issues. ... This CL fixes a few issues where the reported fraction of frames allocated to various temporal layers could be incorrect: * In LibvpxVp8Encoder, calling GetEncoderInfo() while not initialized, or when first configuring with temporal layers and then without, could trigger incorrect fps allocations. * In VP9 when different spatial layers have different max framerates, the layer fps should be compared to the layer with the highest configured fps, not codec_.maxFramerate which is updated to the current input fps on SetRates(). * In EncoderBitrateAdjuster, just warn and ignore if a layer has non-zero bps but zero fps, rather than passing down the chain and risk weird behavior or divide by zero. Bug: b/152040235 Change-Id: I548fb3e099b1ec9f536a7b93313fb40c4d32e596 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/171516 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30880}		2020-03-25 11:20:47 +00:00
..
vp9_impl_unittest.cc	Fixes temporal rate allocation issues.	2020-03-25 11:20:47 +00:00