Yep, my posting and example weren't about RAW processing. The bracketing file was obtained from a 16-bit tiff, not from RAW. There was no processing of the image after bracketing at all before enfuse. And the result was pretty satisfying.
So, let me return to original idea. It is belong RAW conversion. If we have RAW from a modern camera, it is naturally a HDR image itself because of close to 12 bits dynamic range of modern cameras at lowest ISOs. When we convert it to some format (16-bits tiff is the best choice) in our favorite converter (I prefer darktable), _the_resulting_ image contains enough data to restore shadows. So, if we take properly exposed tiff (or even jpg), make required exposure correction (+EV) in some software and feed that images to enfuse as a set of bracketed images, it produces nice result with compressed global contrast and preserved local one. One can say it could be better to use real bracketing, but it is not always possible on one hand and the result can be satisfactory on another. If enfuse could internally make a in-memory copy of a single picture with given (via a option) exposure compensation and threat that images as a exposure stuck that can make it a nice tonemapping program. I guess that is the simplest solution requiring minimum efforts - if an option is used, instead of loading second image just create it in memory from the first one and apply given exposure compensation. On 1 апр, 10:13, kfj <[email protected]> wrote: > On 21 Mrz., 18:27, Alexander Rabtchevich > > <[email protected]> wrote: > > So the feature request is to implement internal tonemapping algorithm > > from one file for enfuse without the need to produce several input > > files with different exposures. The adjustment parameter can be a > > value of exposure compensation. > > I'd like to point out that if I look at the initial posting, I think > this is not directly about raw processing. It is a feature request for > processing a single image with enfuse rather than having to produce > several different versions of the image and feed them to enfuse. The > conversion of the initial raw image into a format enfuse can read is, > I'd say, not a problem and can be achieved easily using any of a > number of raw processing tools. The requested feature should work just > the same with a single 16 bit TIFF and might even do some good to 8 > bit and even JPEG material. Being able to feed in a raw image might be > nice-to-have, but I think this isn't the point of the request, really. > Kay With respect, Alexander Rabtchevich -- 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
