-
-
Notifications
You must be signed in to change notification settings - Fork 853
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
Webp encoding produces completely transparent images #2763
Comments
@Lovrenc Can you please give examples at which the quality works? |
OK. This is odd... I can replicate the issue with the v3.1.4 release NuGet package but I cannot replicate it with the release/3.1.x branch without explicitly setting the encoder to use Lossless encoding (though there are no commits changing behavior). It appears quality between greater than 83 and less than 88 causes the issue. It's something to do with symbol generation in the VP8LEncoder but I'm not sure what is happening. @brianpopow I likely need your experience here if you have time. |
Sorry I was not around. I see you found a range. I can confirm that values 60, 70, and 75 work, and 85 does not work; I did not test other values. |
@JimBobSquarePants I will take a look into this on the weekend. |
Thanks. I spent a few hours comparing our code to libwebp and couldn’t spot an issue. |
Prerequisites
DEBUG
andRELEASE
modeImageSharp version
3.1.4
Other ImageSharp packages and versions
Not using
Environment (Operating system, version and so on)
Windows 11/Ubuntu 22.04
.NET Framework version
.net 7.0
Description
Webp encoder in some instances produces a completely transparent image (the image still has 262KB tho, so I guess the data is in there.
Attached you have a code to reproduce the issue and a sample image.
Important notes:
Changing encoding quality produces a valid image.
Changing the encoding method also produces a valid image (however, I found faster encoding levels tend to produce artifacts on fade-out transparencies)
Steps to Reproduce
Images
The text was updated successfully, but these errors were encountered: