Problem using Gimp with hugin pano

30 views
Skip to first unread message

Didier Quatrer

unread,
Jun 18, 2020, 5:43:12 AM6/18/20
to hugin and other free panoramic software
Hello,

I have a new problem using Gimp 2.10.18 to resize my panos, created by Hugin 2019 2.0.
Most of the time, I do not get 180° vaov, but around 130 ° (part of sky missing)
Image size is Ok, example 8192x2959.

When I open the tiff file using Gimp, it adds an empty sky to fit a 180° vaov. I do not know why.

If I remove the blank upper part of sky, and export my picture to jpg, I cannot display it correctly using pannellum and a json config file.
Picture is centered by panelum, it looses bottom position.

Same method was working with Gimp 2.10.10
I only had to calculate vaov to match my resulting panorama x - y dimentions, and display under panellum was perfect !

Workaround : I keep 2/1 size generated by gimp, (8192x4096),  exporting to jpg creates a white sky, removed by json file (maxpitch =35 instead of 90 ...)

This means Gimp looses some information about pano position.

Thanks in advance for your help !
gimp-hugin.jpg

Bruno Postle

unread,
Jun 19, 2020, 6:29:12 AM6/19/20
to hugin and other free panoramic software
By default Hugin creates 'cropped' TIFF files, where empty transparent
space around the pixel data is represented by offsets (it also does
this for PNG and EXR output). This really helps for big panoramas with
lots of empty space.

GIMP 2.10.8 here (yes, I ought to upgrade) applies these offsets with
multilayer TIFF files, ignores them with single layer TIFF files, and
asks about applying them for PNG files. Probably you are seeing this
fixed for single layer TIFFs in the latest GIMP.

The solution is to tell Hugin to not 'save cropped images', either in
the Stitcher tab -> Nona -> Options, or to do this for all new
projects: change the setting in Preferences -> Programs.

--
Bruno
--
Bruno
Reply all
Reply to author
Forward
0 new messages