"For his invisible attributes, namely, his eternal power and divine nature, have been clearly perceived, ever since the creation of the world, in the things that have been made. I hope that many nifty panoramas and exposure fusions can be created from this plugin. So far I've been using the plugin for awhile and I feel it's at a good enough state in which I can now share with the community. The process has been rewarding so far and I hope to continue to work on adding additional features and resolving bugs that I run into along the way. Although an exposure fusion plugin for lightroom already exists, as Hugin and Enfuse are open source tools, I believe it would be appropriate to create an alternative open source plugin that would allow other photographers to freely create exposure fusion images or stich panoramas quickly from Lightroom. HuginEnfuse was written as an excuse to learn Lua and because I simply got tired of having to export pictures from Lightroom, setup Hugin options and run the optimizations, then wait for the stitch to finish, and then reimport into Lightroom.
#USING LR ENFUSE CODE#
The code is licensed under the BSD 3-Clause license to encourage developement of this plugin and to act as a starting point to enable others to create similar plugins for other photography related open-source applications. This project uses the Hugin Panoramic tools both for automatically stitching panoramas and for basic exposure fusion using enfuse. This is where your work now starts, deciding how you want to best process that into a final picture.A lua plugin to access basic panorama (hugin) and exposure fusion (enfuse) capabilities directly from Lightroom. A "problem" scene where the camera sensor would have struggled, now becomes a no-problem scene. That's why it initially doesn't look like much.īut once you start to play with Exposure, Contrast etc the sheer depth of information that it contains, compared with a single Raw file, starts to become apparent. There is no point in considering those things before merging since they have been basically ignored up to this stage.
![using lr enfuse using lr enfuse](https://i.ytimg.com/vi/xQ6R8TtjUII/maxresdefault.jpg)
when you use LR or Aperture to convert RAW files you never know if the results are. But this is not in the form of a bitmap and such things as WB and the contrast curve and highlights etc that you want pictorially, are still available to be changed. I like LR/Enfuse because it fits my Lightroom workflow quite well.
#USING LR ENFUSE FULL#
One which combines (after aligning if necessary) the full exposure range that was represented in the source images. Apart from adjustment tweaks.īy contrast, Lightroom's HDR produces something that looks and behaves, like a really nice camera Raw which has not yet been processed. The net output is something which looks and behaves, like a really nice camera JPG which has (substantially) already been processed.
![using lr enfuse using lr enfuse](https://i0.wp.com/www.wolfnowl.com/wp-content/uploads/2011/10/DSCF29707-blend.jpg)
And a new bitmap is made that shows and combines whichever best representations (not too overexposed, not too underexposed) can be found in the whole set, each one darkened or lightened according to an algorithm so as to sit properly in the overall tonal scale. Then each intermediate after aligning if necessary, is analysed (including referring to EXIF metadata) for the "quality" of representation that it includes, of each part of the subject. If the plugin LR/Enfuse is being used, that manages these intermediates. So it is necessary to consider these things BEFORE submitting the images to Enfuse. This includes whatever WB is set, highlight recovery, NR / capture sharpening etc.
![using lr enfuse using lr enfuse](https://tuxoche.com/wp-content/uploads/2014/03/lr-enfuse.jpg)
Lightroom's HDR and Enfuse operate in completely different ways and produce different forms of output.Įnfuse requires bitmap intermediates, so LR Raw conversion settings / adjustments are at that point committed into pixels.