Enfused panorama picture is too bright.

695 views
Skip to first unread message

Pawel Rozenek

unread,
Nov 23, 2013, 1:41:09 PM11/23/13
to hugi...@googlegroups.com
Hi All,

I have done about 20...30 360x180 panoramas in my life. I was always using Hugin 2012 version. Last night I tried to use a different lens and I had a problem with stitching all the pictures together (possibly the nodal point was not very well adjusted). Anyway, looking for help in internet I found that Hugin 2013 has recently been released so I downloaded and installed this version. To my surprise Hugin 2013 stitched all my 36 pictures without any problems!


Unfortunately the final panorama picture is very light, no contrast, very poor saturation whereas ALL MY component pictures ale quite nice and intense.

What wrong I have done?

My panorama and a few example pictures are here: http://www.rozenek.com/english,1147


Pawel Rozenek

unread,
Nov 23, 2013, 2:14:37 PM11/23/13
to hugi...@googlegroups.com

What wrong I have done?


I forgot to say that I used option panorama outputs: exposure corrected, low dynamic range  --> JPG
 all other options were unchecked


I am happy to keep my component pictures with unchanged exposition. Which options should I use?

Pawel Rozenek

unread,
Nov 25, 2013, 2:42:32 PM11/25/13
to hugi...@googlegroups.com

Guys, please help... I have tried all options and it still doesn't work :(


I am using already HDR component pictures because I prefer to use my favorite HDR software and then I only want to stitch them together.

Moreover, while Hugin is generating the panorama, I can view temporary tiff files and they look perfect! The problem appears on the enfused panorama.

What do I do wrong?

Carl von Einem

unread,
Nov 25, 2013, 5:24:51 PM11/25/13
to hugi...@googlegroups.com
Hi Pawel,

in the Advanced interface try to reset the photometric parameters to the
original EXIF values. Use the context menu (right mouse click).

The panorama is extremely oversaturated and I guess that's part of how
you process your raw images.

The zenith and nadir are missing. If you didn't shoot images for both
you might be able to either patch those areas it in your image editor,
or just set the viewing limits in pano2vr. Pano2vr has a cool feature to
excerpt those regions so you can easily edit them. Look for the "Patch"
video tutorial.

The panorama looks good at first sight but zooming in I see a lot of
errors. Enfuse did a nice job but you may invest some more time:
manually add some control points across the overlap regions and optimize
again.

Interestingly the area around your tripod doesn't look that bad, so the
set up wasn't that bad. BTW it's not a "nodal point", see
http://wiki.panotools.org/Nodal_Point

Cheers,
Carl

Pawel Rozenek schrieb am 23.11.13 19:41:

Pawel Rozenek

unread,
Nov 26, 2013, 1:59:50 AM11/26/13
to hugi...@googlegroups.com, ca...@einem.net
Carl, thank you very, very much for your answer. Could you please or anybody look at the DIFFERENT panorama below.



On Monday, 25 November 2013 22:24:51 UTC, zarl wrote:
Hi Pawel,

in the Advanced interface try to reset the photometric parameters to the
original EXIF values. Use the context menu (right mouse click).



I haven't tried this yet because I am going to work right now, however I tried to find this options and I couldn't. I will try harder when I come back home.

 
The panorama is extremely oversaturated and I guess that's part of how
you process your raw images.



I do not think so. If you look at the panorama:
http://www.rozenek.com/images/forum/panorama-ok.jpg - this is panorama made with Hugin 2013 and all is perfect!

The same components used in Hugin 2013 gives me a awful result here:
http://www.rozenek.com/images/forum/panorama-bad.jpg


You can look at two random frames (components) which I used to make these panoramas, I would like to say again: for both I used the same components made in HDR-MACCHINERY software.
http://www.rozenek.com/images/forum/frame-01.jpg
http://www.rozenek.com/images/forum/frame-02.jpg

 
The zenith and nadir are missing. If you didn't shoot images for both
you might be able to either patch those areas it in your image editor,
or just set the viewing limits in pano2vr. Pano2vr has a cool feature to
excerpt those regions so you can easily edit them. Look for the "Patch"
video tutorial.


Yes, the previous panorama had a problem with zenith and nadir because it was only a test shot. The today's panorama has no problem with zenith and still isn't ok with nadir - however I am not too fussy yet :)

 

Interestingly the area around your tripod doesn't look that bad, so the
set up wasn't that bad. BTW it's not a "nodal point", see
http://wiki.panotools.org/Nodal_Point


I made my bracket myselt just for my camera: http://www.rozenek.com/images/forum/bracket.jpg

 

Frédéric COIFFIER

unread,
Nov 26, 2013, 7:56:57 AM11/26/13
to hugi...@googlegroups.com, Pawel Rozenek
Hi Pawel,

Have you tried the enblend option --no-ciecam ?
https://bugs.launchpad.net/enblend/+bug/1157155

Regards,
Frederic

Pawel Rozenek

unread,
Nov 26, 2013, 7:59:53 AM11/26/13
to hugi...@googlegroups.com, Pawel Rozenek, frederic...@free.fr
Hi Frederic. Thank you for your answer. I haven't tried that. I am at work now and I will try in next few hours :) Thank you. :)

Pawel Rozenek

unread,
Nov 26, 2013, 1:29:03 PM11/26/13
to hugi...@googlegroups.com, Pawel Rozenek, frederic...@free.fr
Have you tried the enblend option  --no-ciecam ?
https://bugs.launchpad.net/enblend/+bug/1157155





How can I say thank you? It works!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Frédéric COIFFIER

unread,
Nov 27, 2013, 3:55:35 AM11/27/13
to Pawel Rozenek, hugi...@googlegroups.com
Hmm, you may subscribe to the bug report.
Maybe, one day, a developer will solve it.

Pawel Rozenek

unread,
Nov 27, 2013, 4:06:16 AM11/27/13
to hugi...@googlegroups.com, Pawel Rozenek, frederic...@free.fr

On Wednesday, 27 November 2013 08:55:35 UTC, Frédéric COIFFIER wrote:
Hmm, you may subscribe to the bug report.
Maybe, one day, a developer will solve it.
 
 
Frederic, thank you again so much. I was thinking about downgrading my Hugin to 2012 :)
 
Where can I do this report?

Harry van der Wolf

unread,
Nov 27, 2013, 9:52:26 AM11/27/13
to hugi...@googlegroups.com


2013/11/27 Pawel Rozenek <sq8...@googlemail.com>

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c93f1df2-4736-4c64-b4f0-ecf661db530a%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Tiemen Meerman

unread,
Dec 2, 2013, 3:30:58 PM12/2/13
to hugi...@googlegroups.com, Pawel Rozenek, frederic...@free.fr
Frederic,

Thanks from me, too! Got me out of a bind!

-T

Danny Chapman

unread,
Dec 14, 2013, 5:28:37 PM12/14/13
to hugi...@googlegroups.com

On Tuesday, 26 November 2013 12:56:57 UTC, Frédéric COIFFIER wrote:

Have you tried the enblend option  --no-ciecam ?
https://bugs.launchpad.net/enblend/+bug/1157155


At the risk of "me tooing" - many thanks from me too! I had spent maybe 6 hours trying to get my panorama to work. For some reason the first pano I did with this set of images was OK (but not aligned properly) - then after that I would get exactly the problem described here, except when I used a subset of the full set of photos.

I see there's a post saying using the profile is correct, and this isn't a bug. However, if so then the preview in Hugin should also use, as otherwise it's totally misleading. Also, I find it really odd that the problem only shows up on the full panorama - not when I process a subset. All images were processed in exactly the same way (from Canon EOS 60D, RAW processed using DPP, no changes in the area of colour management as far as I can remember). I'd imagine that this would trip up a reasonable number of people - even if it's not a bug as such, I would have thought it better/safer to use --no-ciecam by default, and let advanced users change this (though I'm a new Hugin user, so my opinion may be worthless!).

- Danny

Frédéric COIFFIER

unread,
Dec 18, 2013, 5:23:05 AM12/18/13
to hugi...@googlegroups.com, Danny Chapman
Hi Danny,

Do you still have the hugin project with this problem ?
Could you make an archive and send it to me ? I would like to reproduce it and to attach it to the bug report.
If you can generate a not so big archive (~10-20MB) with just a subset of your panorama, it will be easier for me.

Thanks,
Frédéric
Reply all
Reply to author
Forward
0 new messages