[Hugin-devs] [Bug 1865333] Re: dataWindow and displayWindow look swapped in generated OpenEXR files
Regardless of what darktable should do as an editor, it still effectively means that any compliant viewer will display a border around EXR files exported by Hugin. I find it extremely hard to believe that this border is there on purpose. “all place where images are loaded or saved would be checked and modified for this 2 different ways of storing the information.” Surely I must be missing something but I don’t see why that would be the case. Is there any code in Hugin that actually reads the display window, *and* would be negatively affected if it became correct? We have established that Hugin writes the pixel data that it should write to the EXR and that the data window reflects that. What would be the drawback of also setting the display window to that same window, if it is indeed the window that programs are supposed to use? I believe that this is the only change that would be required to solve the problem. “The current behavior of Hugin is consistent for TIFF and EXR.” Is it, though? When I export the same project as a TIFF, I get a 5242×3914 image (which corresponds to the cropped dimensions) with offset 0.17, 0.26. That does not resemble the properties of the exported EXR file. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1865333 Title: dataWindow and displayWindow look swapped in generated OpenEXR files Status in Hugin: Opinion Bug description: When exporting a high dynamic range image with a crop as an OpenEXR file, the cropped dimensions end up as the dataWindow and the canvas size as the displayWindow, which seems like it’s the wrong way around. When imported back into darktable, the image has a black border on the left and at the top. Export settings: https://i.imgur.com/TFmA6zP.png (also attached) exrheader output: dataWindow (type box2i): (51 78) - (5292 3991) displayWindow (type box2i): (0 0) - (5345 4070) This happens on intermediary remapped files too, not just the final merged output. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1865333/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1865578] Re: hugin crashes on startup if closed with advanced or expert interface
I've got it: it's not a crash after all; when hugin starts in advanced or expert mode, the "tips at startup" dialog pops up but is hidden behind the main hugin window. In that situation the main window does not respond since the tips dialog is modal. However when hugin is started in Simple mode, the tips window appears on top. Thank you for your prompt response and sorry for the confusion. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1865578 Title: hugin crashes on startup if closed with advanced or expert interface Status in Hugin: Incomplete Bug description: Hugin 2019.2.0-2 on Archlinux 5.5.6-arch1-1 #1 SMP PREEMPT. glxgears works. I read hugin faq; feel free to indicate where the "output log" may be found... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1865578/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1865333] Re: dataWindow and displayWindow look swapped in generated OpenEXR files
> I believe that darktable is correct according to “Testing Other OpenEXR > Viewers” I think it is only correct when using darktable as viewer only. But as soon as you process the image, the data outside of the display should not be disregarded. Maybe Darktable should provide an option to use display or data window (as exrdisplay). The current behavior of Hugin is consistent for TIFF and EXR. If we would change it for EXR as you propose this would be different for both file formats which I don't like because then all place where images are loaded or saved would be checked and modified for this 2 different ways of storing the information. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1865333 Title: dataWindow and displayWindow look swapped in generated OpenEXR files Status in Hugin: Opinion Bug description: When exporting a high dynamic range image with a crop as an OpenEXR file, the cropped dimensions end up as the dataWindow and the canvas size as the displayWindow, which seems like it’s the wrong way around. When imported back into darktable, the image has a black border on the left and at the top. Export settings: https://i.imgur.com/TFmA6zP.png (also attached) exrheader output: dataWindow (type box2i): (51 78) - (5292 3991) displayWindow (type box2i): (0 0) - (5345 4070) This happens on intermediary remapped files too, not just the final merged output. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1865333/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 1865578] Re: hugin crashes on startup if closed with advanced or expert interface
That's a strange error. I've never heard of such a behavior. (In simple mode, yes. but not in advanced mode). Just to confirm: 1. You delete .hugin. 2. Start -> simple interface come 3. Switch to advanced interface -> Editor window come up 4. Close Hugin 5. Start again -> now it crashes Is this right? If so please, provide the .hugin file and the full output from the terminal of step 5. Maybe this can help to track down the bug. ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1865578 Title: hugin crashes on startup if closed with advanced or expert interface Status in Hugin: Incomplete Bug description: Hugin 2019.2.0-2 on Archlinux 5.5.6-arch1-1 #1 SMP PREEMPT. glxgears works. I read hugin faq; feel free to indicate where the "output log" may be found... To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1865578/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
