avif.io
avif.io copied to clipboard
EXIF to HEIF metadata conversion
I have jpeg files with orientation metadata, that displays rotated once converted to .avif.
Maybe it's because orientation metadata is supported in jpeg and not in avif ?
Maybe the orientation metadata should be used at conversion time to rotate the input image ? I have the same issue with avifenc with this input file.
As far as I remember, we strip all EXIF data in the conversion process. I'm not certain whether adding an optional setting to keep the data is easy to implement, but let's keep it on the roadmap to investigate further.
As far as I remember, we strip all EXIF data in the conversion process. I'm not certain whether adding an optional setting to keep the data is easy to implement, but let's keep it on the roadmap to investigate further.
I tried to emulate this behaviour. Chrome does not seem to support EXIF Orientation metadata in AVIF, so the picture still appears rotated.
Is EXIF orientation deprecated ? If so i would expect the conversion tool to remove them, optionally rotating the input image. If not, maybe i should check Chrome's bug tracker.
I created a chromium issue also but not very hopeful : https://bugs.chromium.org/p/chromium/issues/detail?id=1249385
I created a chromium issue also but not very hopeful : https://bugs.chromium.org/p/chromium/issues/detail?id=1249385
It seems like they are on it as long as we provide some samples!🥳
Hum... Deprecation of EXIF metadata seems real. There is a debate in the chromium issue saying that the AVIF/HEIF container format has its own orientation / mirroring metadata and that the EXIF one "can" be ignored according to the specification.
The "modern" way of doing the jpeg->avif tranformation seems to convert the EXIF orientation metadata into the corresponding HEIF container metadata. The resulting files will then be supported by current Chromium and other HEIF compliant decoders.
Hum... Deprecation of EXIF metadata seems real. There is a debate in the chromium issue saying that the AVIF/HEIF container format has its own orientation / mirroring metadata and that the EXIF one "can" be ignored according to the specification.
The "modern" way of doing the jpeg->avif tranformation seems to convert the EXIF orientation metadata into the corresponding HEIF container metadata. The resulting files will then be supported by current Chromium and other HEIF compliant decoders.
Hum... ye, it seems like it. Sad to hear there's no fallback for EXIF if HEIF doesn't store information. I'm afraid the coding effort is too high/complex for me to add this to the converter, so I'd have to wait for someone to be able to implement this feature of converting metadata.
I'm not sure how, but exiftool-12.51 is able to write exif data to the avif file previously converted at avif.io. Gimp developer version 2.99.12 is able to read it. I used simple command: "exiftool -tagsFromFile "source file" "destination file"". Example here: https://mega.nz/folder/k4dnxRZC#0KA51AUyiF2lKgHeumvy0A