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

Image quality #412

Closed
Tolriq opened this issue Apr 14, 2015 · 5 comments
Closed

Image quality #412

Tolriq opened this issue Apr 14, 2015 · 5 comments
Labels
Milestone

Comments

@Tolriq
Copy link
Contributor

Tolriq commented Apr 14, 2015

Me again :) with latest snapshot.

I have image quality problem with big images but does not happens when using ARGB8888

        Glide.with(YatseApplication.getInstance())
                .load(DisplayHelper.getGlideImageRequest(buffer))
                .centerCrop()
                .placeholder(mDefaultImageResource)
                .error(mDefaultErrorResource)
                .crossFade(250)
                .into((ImageView) view.getTag(imageViewId));

As you can see if you zoom the image (but very visible on the device) the fanart images have horrible vertical bars all over and looks bad :(

The images in cache that I return with a simple new FileInputStream(cachedFile); is joined too so you can see the source size and that the source image is artifact free.

screenshot_2015-04-14-17-10-49

774465504fc32e79634908be499616f3

@Tolriq
Copy link
Contributor Author

Tolriq commented Apr 14, 2015

@sjudd I posted without edit to open discussion but the problem is caused by e9cfd2d I have reverted locally it and have no more problems even with ARG 565.

I remember that I had to remove the inDither in my own code to avoid such problems.

No idea about the paint flags as I did not used that before.

@sjudd
Copy link
Collaborator

sjudd commented Apr 15, 2015

Interesting find. Everything I could find about inDither indicates it is in fact the right thing to do when decoding RGB_565 images. It's supposed to add noise to break up banding (ironically).

Did you revert that entire commit, or just inDither? ANTI_ALIAS should also be totally unnecessary, I can't imagine that would have an affect...

@Tolriq
Copy link
Contributor Author

Tolriq commented Apr 15, 2015

I reverted the whole commit, but I can test the flags if you want, I have just no idea how they are used and the impact :)

@sjudd
Copy link
Collaborator

sjudd commented Apr 15, 2015

If you can confirm that just the flags change is fine, then we can go ahead and revert the inDither change.

@sjudd sjudd added the bug label Apr 15, 2015
@sjudd sjudd added this to the 3.6.0 milestone Apr 15, 2015
@Tolriq
Copy link
Contributor Author

Tolriq commented Apr 15, 2015

Seems comment was lost :( No visual impact with the FLAG change in the previous PR, on inDither degrade image quality.

But only tested on Android 5.0 and 5.1

@sjudd sjudd closed this as completed in 6c85b13 Apr 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants