Use a fixed 6500K value for the white balance during the capture.
Put your HDRI in Blender and start the render.
Calculate the EV of one of the bracketed exposure photo using the EXIF data. Input that value in the Photographer add-on and see if the render brightness matches the reference photo. If not, adjust the exposure of the HDRI in Photoshop or other photo editing software.
Thanks @joemoehobo for starting porting over to 2.8, thanks @hypersomniac for the viewport update trick.
Changed context.user_preferences to context.preferences (API change)
Little cleaning.
Warnings:
There are still some registration errors for the addon preference, so you can get errors when enabling / disabling / re-enabling the addon during the same Blender session. Ignore the error and click again to enable the addon.
To avoid breaking the autosave, I re-introduced a āApply all settingsā button. If you changed Resolution, Color management Curves or Depth of Field default blender settings, they will override the Photographer settings. You can use that button to reapply the Photographer settings all at once.
Both issues were already present in 2.79 so there is no regression there.
I think itās pretty unacceptable to break the autosave, so I fixed 2.79 version as well with version 1.2.3.
Same warnings as the 2.8 version, I think itās not too much of a problem to have to reapply the settings in rare situations.
This is awesome addon. Glad to see this addon in 2.8. I have a question about the functionality of this addon with EEVEE. EEVEEās Depth of Field and Motion Blur still have got limitations. They are not feature-complete yet. Could this addon solve the problem a bit? Thanks!
The add-on is only an interface layer on top of the rendering options that already exist in Blender, so unfortunately, it wonāt fix EEVEEās limitations.
I am personally still working everyday on 2.79 because some add-ons I use havenāt been ported yet, so Iām not fully aware of EEVEEās limitations at the moment. If you can write them down to me, it would help me understand the issues and how we could work around them, or nag Clement to fix them
Perhaps this is beyond the scope of this plugin, but what would the chances be of adding lens presets, so you can pick from a variety of real-world lenses, to go along with the other camera settings of being able to pick from a variety of real-world cameras.
I imagine that would automatically set up the focal length and DOF and such.
It is out of scope in terms of lens visual signature (vignetting, sharpness, distorsion, chromatic abberation, bokeh shape) because these can only be done in compositing at the moment, and even then, I find the compositing tools to be pretty limited (and slooooowwwww). This would also require to do some lens tests and recordings (not all of this information is available online unfortunately).
So it would only be a limit on the Aperture range (like f/2.8-f/22) and a focal length preset (like 50mm, or 24-105mm), and I donāt think it makes much sense to only have that? Or is it just me?
That being said, having a list of different Lens Post-Processes in the Compositor is totally doable. Unfortunately the nodes are bit limited and donāt have a way to manage a list of values from Presets (AFAIK), but you could always append a specific lens node group.
UI improvements based on @William 's suggestions, thanks a lot for your help!
The UI should now be less ājumpyā, enabling or disabling settings instead of hiding them.
Relevant information is visible even when collapsing panels. I prefer to keep this kind of info visible as I tweak the settings rather than in a different panel.
I would personally recommend doing it using Blender scenes system to keep it consistent with the way Blender works Changing World HDRI per camera wouldnāt be hard, but if you want to use different light rigs, scenes is definitely the right way to do it.
Hey, Iāve installed the add on. I mightnāt just be able to see the wood for the trees but I canāt seem to find it on the properties panel. Iām on the build that went out on 06/05.