Age | Commit message (Collapse) | Author |
|
Change-Id: I2c6950e7d79fc89c6f97e6dcf47317ef66c453a5
|
|
Initializes total_actual_bits and total_target_bits to 0
Change-Id: Ia50d3bf5df765146a44aa1f6045e73367ccf50df
|
|
Change-Id: I4bd635949240880ced5f581c24e981ccd0374e40
|
|
If we are already saving a lot in bits from the target (maximum)
bitrate in the constrained quality mode, allow the quantizer
to go lower than the cq level. This hopefully will solve issues
with getting too low a bitrate and consequently poor quality for
certain videos in cq mode.
Change-Id: I1c4e8b0171fcf58f95198b3add85eea5f3c8f19f
|
|
|
|
Change-Id: I7ca46fa26acd80a21210cb8d9584ad812cb995bf
|
|
Allow slightly larger minq-maxq range for P frames. This improves
the compression performance of speed -5 for rtc set by 2.7% in psnr.
Change-Id: I438653d52d0fe51111509c6092e2334bac2de0cf
|
|
tx_mode supercedes whatever mechanism is used to push for 16x16
allowing for the use of the 4x4 transform.
Change-Id: I6c3f05ab9fe52050e40cc6303de9334653763289
|
|
Merged minq tables for arf and gf cases.
These tables were almost the same and for
VBR the arf table was not used at all.
Change-Id: Ie3c87e91dab613cf06f6945ac1ace0e0e4213d34
|
|
Small adjustment to the active Q range calculations.
These changes should slightly extend the available Q range
for KF/GF/ARF and narrow it for other frames.
The results for this change in isolation are broadly positive
for SSIM and average PSNR and slightly up but mixed for opsnr.
derf +0.293% opsnr, +1.286% SSIM
std-hd + 0.528% opsnr, + 1.746% SSIM
yt +0.056% opsnr, +0.457% SSIM
yt-hd -0.147% opsnr, + 0.226% SSIM
Change-Id: If065280342027ecc5d44b49fc1d440dfef041002
|
|
|
|
Change-Id: I62ab0f4346b4157a90dc5b5f73ab5e597d69c1bd
|
|
|
|
Change-Id: Id6ab59e505be28cd4eb9f1fe114feb47debe0539
|
|
Change-Id: I7cc6f441f414ca1b4d95dad3f789fff6faf8c3c4
|
|
This member of VP9_COMP seemed unnecessary since it
only shadowed VP9EncoderConfig.key_freq that is
accessible through VP9_COMP.
Change-Id: Ib751bb1cf1b0b3c50a2a527d7c34f6829dd6fee3
|
|
The end_useage parameter is confusingly named since it
now actually defines the rate control method used.
Change-Id: I98912caabfe556b7af0b939a645d1336409e4d71
|
|
|
|
|
|
Change-Id: Id48edd12c6f649c82113128491ef6ea7410e93b2
|
|
Use cq_level (which is identical) from VP9_CONFIG instead.
Change-Id: I1aaf2fcef3d2dbd4577f613d27693ff8a68989fd
|
|
To make direct side by side testing this patch combines two
VBR corrections schemes to allow more direct side by side testing.
(The other patch was by Debargha chg id I0cd1f7...)
Change-Id: I271c45e5c4ccf8de8305589000218b80d9dc3a25
|
|
Add code to monitor over and under spend and
apply limited correction to the data rate of subsequent
frames. To prevent the problem of starvation or overspend
on individual frames (especially near the end of a clip) the
maximum adjustment on a single frame is limited to a %
of its un-modified allocation.
Change-Id: I6e1ca035ab8afb0c98eac4392115d0752d9cbd7f
|
|
|
|
Fix rate control bug whereby the rate factor heuristics
were being updated on arf overlays causing a rate surge
for a few frames followed by a corrective drop.
This fix eliminates many of the overshoot problems that
we were seeing on hard clips (even without applying
stricter vbr rate control) and also helps quality on
almost all clips with some hard clips improving by >5%.
Overall quality results measured at speed 2.
Derf +1.78% opsnr , +2.44% SSIM
Stdhd +2.41% opsnr, +2.85% SSIM
Change-Id: I2369df6295c2705963fa6307877f6acb304bcc39
|
|
Just to be consistent with min_frame_bandwidth & max_frame_bandwidth names.
Change-Id: I36702c708cba9ad1a5c36393f37758a2edeadb90
|
|
|
|
|
|
Change-Id: Ie0c905b6f32a37e4360bbb44ceeae77c42ad1dc5
|
|
Change-Id: Idb1289aa0eadff8f75dcf995547ab3a1b9e27375
|
|
This increases the range of Q values available to
normal inter frames to allow encoder a better chance
to hit the target rate.
Change-Id: I33cd96469a46577fdcea631e26d3355710909e6d
|
|
The limits applied under the flag
"LIMIT_QRANGE_FOR_ALTREF_AND_KEY"
behaved in an undesirable way if the gap between
active_worst_quality and active_best_quality was
changed.
In this patch, the adjustment is made using the
vp9_compute_qdelta_by_rate() function and fixed
rate multiplier values. Hence it is not impacted by
the relative value of active_best_quality.
Change-Id: I93b3308e04ade1e4eb5af63edf64f91cd3700249
|
|
Change-Id: Ib00a694b9cf8e0c276dfefddab8cb36b8693e022
|
|
And change a parameter setting in vpx_temporal_scalable_patterns.
Change-Id: I7c208296ebcecbc8f73de032f6cdb26a1fc1442b
|
|
Change-Id: Ibc040bee99908e4dc5793d7a9f6e8bf2d15610e7
|
|
Change-Id: I0f4a5c50561a2653d22c366c214a937272ecfa2c
|
|
Change-Id: I08aa0c213df34c084eb7a3c51b6b3306e49c7757
|
|
|
|
|
|
Change-Id: If8044d9c71afe02ed1e6c94487344e143bdfcd74
|
|
|
|
|
|
|
|
Change-Id: I512f2a287dd8765879a2d1144e2f028dc65f71ff
|
|
Change-Id: Iab3effc39064f265426c82b455ef38d37dcce5a8
|
|
These functions do nothing about rate control.
Change-Id: I714e80b1c1f4f9aa157a56df705247fce6db138d
|
|
ARF overlays now use the same rate correction factor as regular inter
frames, further testing would be needed to see if it makes sense to use
a completely separate rate correction factor for ARF overlays.
$ vpxenc --cpu-used=5 --fps=50/1 --target-bitrate=2000
parkjoy.y4m -o out.webm
=> Before: 3356 kb/s
=> After: 2271 kb/s
Change-Id: I73e4defa615ba7a8a2bdb845864f4b1721cbbffe
|
|
Change-Id: If1b0a2d6603ce24f5dd99855e8dfe459e7a2835a
|
|
Change-Id: Ib3886cb7cafc211581f4f9e7f76782d9d1984434
|
|
Change-Id: I6371ef7301c6bc3138552bd349e9bd154dee3e08
|