diff options
author | paulwilkins <paulwilkins@google.com> | 2018-01-15 12:00:01 +0000 |
---|---|---|
committer | paulwilkins <paulwilkins@google.com> | 2018-01-31 17:44:46 +0000 |
commit | 41d3331d423c5dc08ea582316262492f29f4d623 (patch) | |
tree | dabbc983750d4f9d6128f689c9c63a790aa3fdb0 /vp9/encoder/vp9_aq_cyclicrefresh.h | |
parent | ea1d0a6b53e83c3f2e89aac06d47e39123f706a4 (diff) | |
download | libvpx-41d3331d423c5dc08ea582316262492f29f4d623.tar libvpx-41d3331d423c5dc08ea582316262492f29f4d623.tar.gz libvpx-41d3331d423c5dc08ea582316262492f29f4d623.tar.bz2 libvpx-41d3331d423c5dc08ea582316262492f29f4d623.zip |
Further change to code detecting slide transitions.
Eliminate false positives in previous patch.
The previous patch did a good job of detecting slide transitions but
in discussions a number of situations were identified that might trigger
harmful false positives. This risk seems to be born out by some testing
on a wider YT set done by yclin@.
This patch adds an additional clause that requires that the best case
inter and intra error for the frame are very similar,meaning it is almost
as easy to code a key frame as an inter frame. This will certainly prevent
the false positive conditions that Jim and I discussed and even if one
does occur it should not be very damaging.
The down side is that this clause may mean that we still miss some
real slide transitions, especially if the images are small and similar. If this
proves to be the case then some further adjustment of the threshold may be
required. However, in the specific problem sample provided we do trap every
transition correctly.
Change-Id: I7e5e79e52dc09bc47917565bf00cc44e5cddd44c
Diffstat (limited to 'vp9/encoder/vp9_aq_cyclicrefresh.h')
0 files changed, 0 insertions, 0 deletions