@scionti_design@ali_kdot What does this setup return as an open domain exr? Does UE multiply the values to fit back into the float range? What slider determines what this multiplication is?
@scionti_design@ali_kdot Got it. So you're doing all that setup to find where the "sunny 16" grey should sit at.
Then in the second part you use a camera with f stop of 2.8 kind of invalidating the diffraction and critical focus width of the "sunny16"
@scionti_design@ali_kdot I'm not following I'm afraid.
Say I shot a picture with a camera, considering nothing clipped&no sensor noise, sun returned 75k, sky 3.5k If I divide those by 10k to fit them into my monitor, I get 0.75 and 0.035. Ratio is the same, as if I put an ND filter.
What's the catch?
@Jam2go Open camera on Android is free and can do full sensor video recording at various binned resolutions. It's great. Wider video from the same lens/sensor.
@gleb_alexandrov@Utrax3D Do it in the viewport monitoring section. Not as a node, it will run *100 faster too. Always keep your compositing pipeline linear.
Onio
Testing out my new photogrammetry rig, experimenting with roughness map extraction.
2 sets of 75 images. Total time spent 60 minutes (capturing, processing, cleanup. Except this render)
#b3d
@gleb_alexandrov@gleb_alexandrov I'd be super interested to chat to you on the workflow that you're about to propose so that it demystifies color "management" a bit further for the reach you got.
@gleb_alexandrov There's no real way of matching Eary's AgX(default blender) in Resolve (without fusion OCIO) other than baking a LUT via ociobakelut, or a sophisticated recreation of Eary's AgX as a DCTL.
Hope that you're not resorting to ACES.
I wonder how you're handling it?