In Krita 4.0.1, exporting a RGB or Grayscale image to EXR throws up an error: "Could not create the output document". If the image is RGB, it will still save it; if grayscale, the output file is corrupted. I could reproduce this with both Windows 7 x64 and MacOS Sierra 10.12.6.
Yes, I can confirm with any color depths: - it saves RGB to EXR, but it trows an error, - it saves Grayscale to EXR, but it trows an error && the file is corrupted. (checked with Krita 4.1.0-pre-alpha (git dac4dc7) on Ubuntu 14.04)
I take it you are trying to save 8 or 16 bit integer images?
Git commit 48cc061544da7404ac8a4730bb1f99c7d0edcf83 by Boudewijn Rempt. Committed on 10/05/2018 at 12:11. Pushed by rempt into branch 'master'. Fix warnings when saving integer images to EXR M +1 -1 plugins/impex/exr/exr_export.cc https://commits.kde.org/krita/48cc061544da7404ac8a4730bb1f99c7d0edcf83
Git commit e9c81a26947d03698d58440a785eaa8e51bf1ed4 by Boudewijn Rempt. Committed on 10/05/2018 at 13:04. Pushed by rempt into branch 'master'. Fix empty warnings when using filters that cannot use QIoDevices If a filter uses a library that handles the file creation, we cannot use QSaveFile, so we shouldn't try to use it. M +8 -6 libs/ui/KisImportExportManager.cpp https://commits.kde.org/krita/e9c81a26947d03698d58440a785eaa8e51bf1ed4
(In reply to Boudewijn Rempt from comment #2) > I take it you are trying to save 8 or 16 bit integer images? Hi Boudewijn, you're right: actually exporting 8-bit depth files didn't throw up the error, only 16/32-bit (both integer and floating). Thanks
Git commit c1eca00db78879a9a1b362efa1e9deff789d105f by Boudewijn Rempt. Committed on 12/05/2018 at 08:26. Pushed by rempt into tag 'v3.0.4'. Fix warnings when saving integer images to EXR (cherry picked from commit 48cc061544da7404ac8a4730bb1f99c7d0edcf83) M +1 -1 plugins/impex/exr/exr_export.cc https://commits.kde.org/krita/c1eca00db78879a9a1b362efa1e9deff789d105f
Git commit d6343e875b431988431c0cdd430bcd29ba4a8ece by Boudewijn Rempt. Committed on 12/05/2018 at 08:27. Pushed by rempt into tag 'v3.0.4'. Fix empty warnings when using filters that cannot use QIoDevices If a filter uses a library that handles the file creation, we cannot use QSaveFile, so we shouldn't try to use it. (cherry picked from commit e9c81a26947d03698d58440a785eaa8e51bf1ed4) M +8 -6 libs/ui/KisImportExportManager.cpp https://commits.kde.org/krita/d6343e875b431988431c0cdd430bcd29ba4a8ece