-
Notifications
You must be signed in to change notification settings - Fork 611
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
Better avif support #1504
Comments
I looked through cavif-rs and it appears to only output 8-bit avif files so I'm not sure what is going on here since image-rs lists decode support for 8-bit avif files. The image loads fine in Chromium, but image-rs cannot decode it. The image was encoded like this: Github does not support attaching .avif files or I would include a test file. |
Are you able to upload a zipped version of the file? |
@rkfox: you can check the file with https://gpac.github.io/ComplianceWarden-wasm/avif.html to see if it was invalidly encoded |
It did not pass validation. Strange that they appear fine in the browser though.
|
Here's an AVIF version of your JPEG encoded with libavif which does pass validation. I believe there are some compliance issues with cavif-rs (or more precisely avif-serialize). The reason the cavif-rs-encoded file appears fine in the browser (at least in Firefox; chromium uses a different library for parsing) is that it's using a newer version of mp4parse that hasn't been published on crates.io. There's been significant updates to the compliance-related functionality since the last time I published to crates.io. If the newer version would be helpful (this can be tested by changing the dependency on |
Just an update on this. Output:
Encoded to AVIF using this command: Output from AVIF validator (no errors):
|
I would like to be able to decode 10-bit avif images. It appears that cavif-rs outputs 10-bit avif images that cannot be decoded using image-rs.
The text was updated successfully, but these errors were encountered: