I realise the node is probably just doing default (95-685, 0.6 nGamma) Just wondering how this all hooks together given that the docs refer to a 445-0.18 style workflow and from what I can see with the OCIO nodes in Nuke they are still similar to the old-style conversions ..... with warts and super blacks and negative linear values all that other stuff !?!
----------------------- Tahl Niran www.tahlniran.com From: [email protected] To: [email protected] Date: Mon, 8 Oct 2012 22:47:42 +0000 Subject: [Nuke-users] OCIO logLin and Middle Grey Hoping someone who has some experience with OCIO, espeically at Sony, can clarify this for me. I have been taking a look at the Sony OCIO docs and it all seems pretty clear, I notice that in spi-vfx they are equating 445 (lg10 value) with 0.18 (inf, inh value) which is great and I like. What I want to know is, are Sony pre-treating any of the the Film Log files (for example lg10) or using some specific scanning correction not common to the rest of us ? If I just take a nominal dpx log file for example, Marcie. Read that in as Raw Data, then apply an OCIO Log Convert. Then her 445 swatch is not returning a..... .18 more like .1493. Same if I use an OCIO to Colorspace or have I missed something ? ----------------------- Tahl Niran www.tahlniran.com _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
