-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
high dynamic range loses info #5
Comments
I second this issue. It isn't a limitation to the model, but an issue with the colorspace conversion inside the gizmo. The gizmo uses an OCIOColorSpace Node to convert Input from linear to sRGB (and vice versa at the end of the gizmo's nodetree). Somehow the OCIOColorSpace sRGB conversion seems to be non-floating. If you want to stick to the OCIOColorSpace Conversion node, you should select sRGBf (f=float) for the input and output conversion. Otherwise simply use the nuke Colorspace Node and convert from linear to sRGB. There's no visual difference between those two options. Here is a quick fix:
Workaround tested in Nuke 15.0 |
Thanks for reporting this @frueter and thanks to @manwhosoldthew for providing the solution. |
I just had a quick play with this comparing it to a very troublesome retime I had on my last shot. It's looking great, thank you so much for sharing!

I just noticed that in overexposed areas (e.g. white striped shirt in direct sun light) the results were clamped at 1.30831.
Easy workaround is to stop the plate down for retime which solved that issue.

I assume this is a limitation with the model?!
Great to have this in the toolbox!
The text was updated successfully, but these errors were encountered: