bumptech / bumptech/glide

AVIF Image Rendering Issues: Blue Tint and Thin Strokes

Open
#5,141 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
35k
Forks
6.2k
Avg merge
1d 11h
Merged PRs (30d)
8

Description

**Glide Version**: 4.14.2

**Integration libraries**: avif-integration

**Device/Android Version**: Samsung Galaxy M52 / Android 13

**Issue details**:
- Some images with translucent background are rendered with a blue tint.
- Fine strokes are rendered visibly thinner than webp version (I initially thought this is because of data loss, but this was not the case when rendered on Chrome).

Both issues do not occur when rendered on Chrome on the same device. Could this be an issue with the decoder (libavif_android.so) that Glide internally uses to decode AVIF formats?

The demo project can be found [here](https://github.com/vignesh-em-swiggy/avif-android).
Blue Tint - branch: [issue/blue-tint](https://github.com/vignesh-em-swiggy/avif-android/tree/issue/blue-tint)
Thin Strokes - branch: [issue/thin-strokes](https://github.com/vignesh-em-swiggy/avif-android/tree/issue/thin-strokes)

**Screenshots**:

![blue-tint](https://github.com/bumptech/glide/assets/14243984/b8827178-0ba4-4294-ae71-865373dda9e3)
![food-bb-icon](https://github.com/bumptech/glide/assets/14243984/d6a23c72-63ea-4a78-a834-6c42ff5504d7)

Contributor guide

Open the contributing guide

Research direction

Reproduce both cases from the linked avif-android demo using the issue/blue-tint and issue/thin-strokes branches on Android 13. Then inspect the avif-integration path and libavif_android.so; done means identifying the decoder or rendering cause and making translucent images and fine strokes match Chrome.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.