Age | Commit message (Collapse) | Author |
|
|
|
See issue 1088.
Change-Id: Icb15d33b4e316add848f210b50cbccd7c7847207
|
|
Change-Id: Ifb384fa571eb08b516ed08fe05b8bca0c94b1edf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See issue 1087.
Change-Id: I231f6f12f870d0a56391daf1673536048418b207
|
|
VP8E_UPD_ENTROPY, VP8E_UPD_REFERENCE and VP8E_USE_REFERENCE have been
deprecated since the initial public release
Change-Id: Ied16b441eec13434d85f1ab115d49ccaf5f2f7b0
|
|
Some more testing of this patch would probably be useful, but I
think the basics of it should work fine now.
See issue 1035.
Change-Id: I4a36d58f671c5391cb09d564581784a00ed26245
|
|
This experiment allows using full above/right edges for all transform
sizes whenever available (for d45/d63), and adds bottom/left edges for
d207.
See issue 1043.
Change-Id: I5cf7f345e783e8539bb6b6d2c9972fb1d6d0a78b
|
|
In VP9, the ref MV had to point to a block that itself fully resided
within the visible image, i.e. all borders of the image had to be
within the visible borders of the coded frame. This is somewhat
illogical, and had obscure side effects, e.g. clamping of fairly
reasonable motion vectors such as 0,0 were clipped to negative values
if the block was overhanging on frame edges (such as the last rows
on 1080p content), which makes no sense whatsoever.
Instead, relax clamping constraints such that the ref MVs are allowed
to point to blocks exactly outside the visible edges in both Y as well
as UV planes, including the 8tap filter edges (that's why the offset is
8 pixels + block size).
See issue 1037.
Change-Id: I2683eb2a18b24955e4dcce36c2940aa2ba3a1061
|
|
See issue 1040 point 5.
Change-Id: I51a70b9eade39efba392a1457bd70a3c515525cb
|
|
This has various benefits:
- simplify implementations because we don't have to switch between
multiple probability tables depending on frametype
- allows fw subexp and bw adaptivity for partitions/uvmode in keyframes
See issue 1040 point 5.
Change-Id: Ia566aa2863252d130cee9deedcf123bb2a0d3765
|
|
Locate them (code-wise) in frame_context, and have them be updated
as any other probability using the subexp forward and adaptive bw
updates.
See issue 1040 point 1.
TODOs:
- real-world default probabilities
- why is counts sometimes NULL in the decoder? Does that mean bw
adaptivity updates only work on some frames? (I haven't looked
very closely yet, maybe this is a red herring.)
Change-Id: I23b57b4e5e7574b75f16eb64823b29c22fbab42e
|
|
to make meaning of color_range obvious.
Change-Id: I303582e448b82b3203b497e27b22601cc718dfff
|
|
allows controls to be tested for at compile-time
Change-Id: I1cd01287dc144392956c82e6dbac003f37703039
|
|
|
|
Account for rounding in distortion calculation in k-means;
carry out rounding before duplicates removal of base colors;
replace numbers with macros;
use prefix increment.
Slight coding gain (<0.1%) on screen_content testset.
Change-Id: Ie8bd241266da6b82c7b2874befc3a0c72b4fcd8c
|
|
Adjust the qp threshold and consec_zeromv threshold for
limiting cyclic refresh. Also increase the refresh period
when the limit amount is significant, and some code-cleanup.
Small gain in PSNR/SSIM metrics: ~0.25/0.3 gain on RTC set, speed 7.
Change only affects non-screen content.
Change-Id: I1ced87a89a132684c071e722616e445b2d18236a
|
|
This portion was tested to have no effect on asan test failures.
Change-Id: I3de1dab7479148bdffc24c4568cb2e7e9963f099
|
|
Fix a couple of memory related errors. Also fix thread test failures.
Change-Id: I0103995f832cecf1dd2380000321ac7204f0cfc0
|
|
|
|
|
|
Adjust the qp threshold based on the denoising setting; not allow
to scale directly from original resolution to one half and vise versa.
Change-Id: I032a9b22f8e1c88de6bb81cf8351367223a3e40d
|
|
Put the reset at the right place, during the setup and prior
to updating the map.
Change-Id: I75e550ae9d8cc15081330b8857edc04c23947875
|
|
For the re-encoding (at max-qp) on the detected high-content change:
update rate correction factor, reset rate over/under-shoot flags,
and update/reset the rate control for layered coding.
Change-Id: I5dc72bb235427344dc87b5235f2b0f31704a034a
|
|
|
|
|
|
Change-Id: Ifd6581c1bdb8d8f4b2ecf676c1a3d385dc129abf
|
|
Change-Id: I57865e9604ac162ef0d97deb16e81ca436a98428
|
|
Canonical builtin checks for clang are to use
__has_builtin. Much less fragile than version checks.
https://code.google.com/p/webm/issues/detail?id=1082
Change-Id: I8151fb75899acdf1a935c23aad9441da99a9abcd
|
|
Also use the _mm_broadcastsi128_si256 intrisic for
Apple clang versions 4.[012]
https://bugzilla.mozilla.org/show_bug.cgi?id=1085607
https://code.google.com/p/webm/issues/detail?id=1082
Change-Id: I6bc821d8163387194ef663e94bfed91fa7281d88
|
|
|
|
Changes to the breakout behavior for partition selection.
The biggest impact is on speed 0 where encode speed in
some cases more than doubles with typically less than 1%
impact on quality.
Speed 0 encode speed impact examples
Animation test clip: +128%
Park Joy: +59%
Old town Cross: + 109%
Change-Id: I222720657e56cede1b2a5539096f788ffb2df3a1
|
|
|
|
|
|
|
|
Change-Id: I0d7ca20bdd0fc868b28b0755e3114a4499056f45
|
|
|
|
Change-Id: I761256a8100d83abf1b937f3739580237e3fad2a
|
|
The setting of svc->spatial_layer_to_encode was missing
in VP9E_SET_SVC_LAYER_ID.
Change-Id: I015b1a64adb9ef2644d6477a02d9d9364c8462b9
|
|
See issue 1040 point 4.
Change-Id: I79e06bd71a27f45770c760c47dc71bc3767a77a0
|
|
See issue 1040 point 3.
Change-Id: Ieef6d326b7fb50ceca5936525b7c688225a11fd1
|
|
Change-Id: I41b13b8767e30da391c2c4da9a729ca7292b16b9
|