![]() Importing into Nuke just as a regular linear exr, I'm getting what looks like a visually identical or extremely similar image to what I see in the Resolve viewer when I set the colour space and gamma to Rec709 in the master settings. Render to OpenEXR (16 bit half), unscaled full range data. Using Resolve instead, this is what I've tried with some success so far:ĭNG Settings/Master Settings (I don't know Resolve that well and it seems I need to set the same thing in two separate locations? I'll have to RTFM):ĭecode using: Clip (counter intuitive when you don't want to clip any data) It does a good job but in addition to not being "BMD log-aware", the rawlib library it uses is not really aware of possible floating point values in an image above 1 (it outputs a 16 bit integer image under the hood), so it's creating an underexposed image. Basically I set colour space to "raw" (not srgb) and "blend highlites". ![]() Initially, to avoid adding Resolve into the mix, I tried importing directly into Nuke with J_Ops but probably because of the custom log curve which J_Ops doesn't know is applied to the footage, it's not giving me the same result as Resolve. ![]() Using "Shot 5" from the Afterglow DNG sequences, I'm attempting to import the full range of a DNG into Resolve Lite and export as a "scene-referred" high dynamic range linear float openexr image to read into Nuke. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |