python-fu pdb.file_exr_save issue - Printable Version +- Gimp-Forum.net (https://www.gimp-forum.net) +-- Forum: GIMP (https://www.gimp-forum.net/Forum-GIMP) +--- Forum: Extending the GIMP (https://www.gimp-forum.net/Forum-Extending-the-GIMP) +---- Forum: Scripting questions (https://www.gimp-forum.net/Forum-Scripting-questions) +---- Thread: python-fu pdb.file_exr_save issue (/Thread-python-fu-pdb-file-exr-save-issue) |
python-fu pdb.file_exr_save issue - JBreckeen - 05-01-2024 Hello again, so I have maybe an odd one. Does anybody know if there are issues with .png's saved with the python pdb.file_png_save()? In my plugin, any image I "save" using that has issues opening on some viewers, while the same image exported through Gimp's UI using the same settings works perfectly fine. As a test, I have a simple white image. If I export it as a .png (16b RGBA) through the UI, works fine everywhere. But same .xcf saved with this code Code: def savePNG(image=None, has the issue. Keep in mind all the variables get their values set from outside, and it does not seem to matter what options are selected - it always has the problem. The "bad" .png works in: Gimp, Photoshop, Blender, Maya, OpenRV, win10 Photos, Paint, Darktable - and probably plenty of otherss. But it does NOT work in DJV, or ColorSync viewers (and maybe others). Which of course is what we normally use and need. When I have looked at the image details in RV, both files appear the same. BTW I also tried pdb.file_png_save() as well So, has anybody seen differences? Thanks much, J. AH!!!!! Nevermind to all of that. I found the issue: I stupidly overlooked the bool vs binary problem: True/False vs 0/1. Doh! Sorry for the interruption. J. |