> > When one loads images into Hugin, it will attempt to compute an exposure > value. This only works if EXIF data in available in the image. If not, the > exposure value will default to 1. Except if another image is already loaded > in the panorama. If that is the case, and it is the same size (and if the > same make and model and focal length), then the exposure value from that > image is copied to this one. To me, this seems like madness. I can > understand what one may be wanting to acomplish with but...that small voice > inside of me is saying "danger, Will Robinson, danger!" >
I think this case is very rare, because this one works only if the second image has some EXIF data (make, model, focal length) to make the comparision. But in this case the chances are high, that also the exposure time and f-stop can be read from EXIF. So this one happens probably only when the image contains corrupt EXIF data. > Why does hugin deal with absolute values of exposures of images? > > Can we bring in all of the images with an exposure of zero and then just > apply exposure compensation instead? > When using LDR output (enblend, enfuse) relativ or absolute exposure should make no big differences. But when output HDR images you get a other output with an ev values of e.g. 13 than with ev 0. But I don't know which output is preferred. Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
