Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

very visible chroma macroblock artifacts on some images (probably bug) #11

Closed
jonsneyers opened this issue Jul 27, 2017 · 6 comments
Closed

Comments

@jonsneyers
Copy link

I tried using cpik with target Butteraugli score 2.0 on some images. On some of them, the results had very visible chroma macroblock artifacts. For example this original image:
008 png

became this after cpik/dpik:
008 png png-pik2 0

I assume this is a bug in either the encoder or decoder.

@jyrkialakuijala
Copy link
Collaborator

Yes, this is a bug. Without looking at the code, it looks like a sign reversal (perhaps due to an overflow) in the intensity-to-blue deltas. We'll write to this bug when this is fixed.

Out of curiosity -- did you find this with SSIMULACRA or was this the first image you tried?

@jonsneyers
Copy link
Author

I looked at 20 images and 3 or 4 of them had this problem. This was the one where it was most obvious.

@jyrkialakuijala
Copy link
Collaborator

jyrkialakuijala commented Jul 30, 2017

The first attempt to reproduce this failed, this bug could be related to the undefined behavior found in other issues. If you could upload the related .pik file, we could find out if this problem is in the decoder or in encoder, and reduce the space for bug hunting.

@jyrkialakuijala
Copy link
Collaborator

Just a FYI, this problem happens on some compilers and not with others. We will provide a fix in a few days.

@dominikhlbg
Copy link

One day before this issue open I sent a pull request with a fix for this bug. #9

szabadka added a commit that referenced this issue Aug 3, 2017
@szabadka
Copy link
Collaborator

szabadka commented Aug 3, 2017

@jonsneyers Could you verify that the issue is fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants