Open maver2 opened 1 month ago
See also https://github.com/darktable-org/darktable/issues/17534, https://github.com/darktable-org/darktable/issues/17429, https://github.com/darktable-org/darktable/issues/15388 (and maybe some other related issues).
As explained in the release notes, due to limitation in exiv2 write support (which makes behavior different to e.g. JPEG/PNG/TIFF) and privacy concerns, it is currently possible to export metadata to JPEG XL only if all the boxes are explicitly checked in the GUI (i.e. "opt-in"). Not sure if there is a way to enable those from the CLI...
@TurboGit I wouldn't close/reject this just yet, it might indeed be worth exploring how to achieve the same feature parity from CLI, if possible... (Note that this also affects AVIF, EXR and XCF.)
Ok reopen then. I've probably fired too fast given the number of issue (expected and documented) requests we have with JXL & metadata :)
Describe the bug
When using darktable-cli to export a Nikon raw image file to JPEG XL (JXL) format, the exported jxl file does not contain the metadata of the original raw file, tested with exiftool and digiKam. Exiftool only lists a few file-related data and info derived from jxl-image like width, height and megapixels. DigiKam does not list any metadata.
For comparison: these procedures produce exported files containing many (all) metadata:
Steps to reproduce
Expected behavior
the exported file should contain all the Exif, manufacturer data, IPTC data of the original raw file. and image metadata
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
distro packaging
darktable version
4.8.1
What OS are you using?
Linux
What is the version of your OS?
Manjaro Linux up-to-date on 2024-09-30 (rolling release)
Describe your system?
No response
Are you using OpenCL GPU in darktable?
None
If yes, what is the GPU card and driver?
No response
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response