aboutsummaryrefslogtreecommitdiffhomepage
path: root/tests
diff options
context:
space:
mode:
authorGravatar msarett <msarett@google.com>2015-09-18 12:06:04 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2015-09-18 12:06:04 -0700
commit8ff6ca6e73644b0bec65c9dfeaa5ca01110d948c (patch)
treee151e3e7c0335fe262607c364f45a75508258dee /tests
parent496d29f6b273340efa59f1077d9338688c685f1b (diff)
Disable dithering in libjpeg-turbo for 565 decodes
libjpeg-turbo turns on dithering by default. When we decode to RGBA, it uses Floyd-Steinberg dithering - consistent with the libjpeg6b gold standard, When we decode to 565, it uses ordered dithering. Ordered dithering for 565 is not part of the 6b standard (libjpeg6b doesn't even support 565) and is causing us a number of issues: (1) Ordered dithering + nearest neighbor sampling is causing checkerboard visual artifacts in some outputs. (2) The ordered dither function in libjpeg-turbo actually behaves differently depending on the alignment of the memory that it decodes into. This means that two image decodes that should be identical may look different just because they decode into different memory blocks. This was causing some diffs on Gold with the scanline_subset test that were causing me some confusion. (3) Maybe not the best evidence, but visually I can't tell a difference with and without dithering (except when nearest neighbor scaling causes the checkerboard artifact). (4) Turning off dithering should be a more significant performance improvement than you might expect. libjpeg-turbo has SIMD color conversions to 565, but when dithering is on, it defaults to scalar code. This CL should make every jpeg decode to 565 on Gold look slightly different. Yay! BUG=skia: Review URL: https://codereview.chromium.org/1349563007
Diffstat (limited to 'tests')
-rw-r--r--tests/CodexTest.cpp21
1 files changed, 12 insertions, 9 deletions
diff --git a/tests/CodexTest.cpp b/tests/CodexTest.cpp
index 041e71c67f..2ea6eda57e 100644
--- a/tests/CodexTest.cpp
+++ b/tests/CodexTest.cpp
@@ -99,14 +99,6 @@ static void check(skiatest::Reporter* r,
SkImageInfo info = codec->getInfo().makeColorType(kN32_SkColorType);
REPORTER_ASSERT(r, info.dimensions() == size);
- {
- // Test decoding to 565
- SkImageInfo info565 = info.makeColorType(kRGB_565_SkColorType);
- SkCodec::Result expected = (supports565 && info.alphaType() == kOpaque_SkAlphaType) ?
- SkCodec::kSuccess : SkCodec::kInvalidConversion;
- test_info(r, codec, info565, expected, nullptr);
- }
-
SkBitmap bm;
bm.allocPixels(info);
SkAutoLockPixels autoLockPixels(bm);
@@ -117,7 +109,18 @@ static void check(skiatest::Reporter* r,
SkMD5::Digest digest;
md5(bm, &digest);
- // verify that re-decoding gives the same result.
+ {
+ // Test decoding to 565
+ SkImageInfo info565 = info.makeColorType(kRGB_565_SkColorType);
+ SkCodec::Result expected = (supports565 && info.alphaType() == kOpaque_SkAlphaType) ?
+ SkCodec::kSuccess : SkCodec::kInvalidConversion;
+ test_info(r, codec, info565, expected, nullptr);
+ }
+
+ // Verify that re-decoding gives the same result. It is interesting to check this after
+ // a decode to 565, since choosing to decode to 565 may result in some of the decode
+ // options being modified. These options should return to their defaults on another
+ // decode to kN32, so the new digest should match the old digest.
test_info(r, codec, info, SkCodec::kSuccess, &digest);
{