-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Metadata for AVIF, format returned as 'heif' #2504
Comments
libvips v8.11.0 will contain logic to expose the |
Not sure if this is related, but
I'm guessing not supported at the moment. |
$ hexdump -C 2.avif | head -1
00000000 00 00 00 20 66 74 79 70 61 76 69 73 00 00 00 00 |... ftypavis....| Please see strukturag/libheif#377 |
v0.29.0 now available. |
When we use https://sharp.pixelplumbing.com/api-output#tobuffer with |
@adityapatadia This issue relates to the |
Yes, but ideally |
The object returned/resolved by |
Using Sharp 27, which now supports AVIF and is great. Thanks!
Downloading this image and then extracting metadata with
sharp(inputavif).metadata()
The format returned is
heif
as that's the encoder used by libvips.Is it true that this metadata format will be returned for both
avif
andheic
images?If so, it's not going to be possible to use the metadata to distinguish between the two, one of which is patent-encumbered and cannot be processed without globally installed libvips, as I understand it.
Would it be possible for the libvips metadata to return
avif
as the format, for consistency with mime type headers and Sharp output format strings?The text was updated successfully, but these errors were encountered: