I hate to even suggest it but could they have recorded Rec709 instead of LogC? Or perhaps someone rendered LogC to Rec709 between when it was shot and when it got to you. Either way, awkward.
Sent from my iPhone On Oct 28, 2016, at 13:41, Neil Scholes <n...@uvfilms.co.uk<mailto:n...@uvfilms.co.uk>> wrote: thanks really appreciate it I can’t send a pic unfortunately - just signed the NDA etc etc….. thanks for the snippet - yes they have exactly the same effect - negative numbers in super brights interestingly when i change the incoming primary to sRGB rather than AlexaV3LogC - i get rid of the negatives and the image looks about natural Which makes me think that there is defo something weird about the plate - like the tone mapping is correct but the colours are not…. Anyway - thanks for your help - ill stick with normal nuke for these shots - ACES is great if the plates are spun out properly me thinks. N Neil Rögnvaldr Scholes Director | VFX Supervisor www.neilscholes.com<http://www.neilscholes.com> +44 (0) 7977 456 197 On 28 Oct 2016, at 20:08, Haarm-Pieter Duiker <l...@duikerresearch.com<mailto:l...@duikerresearch.com>> wrote: Here's a little script to compare the default Nuke colorspace result and the OCIO config result. Looks pretty similar... HP set cut_paste_input [stack 0] version 10.0 v1 Constant { inputs 0 channels rgb format "1024 1024 0 0 1024 1024 1 square_1K" name Constant1 selected true xpos 1519 ypos 280 } Expression { expr0 x/(width-1) expr1 x/(width-1) expr2 x/(width-1) name Expression1 selected true xpos 1519 ypos 352 } Dot { name Dot1 label "LogC data" selected true xpos 1553 ypos 400 } set N4d458970 [stack 0] OCIOColorSpace { in_colorspace "Input/ARRI/Input - ARRI - V3 LogC (EI800) - Wide Gamut" out_colorspace "ACES/ACES - ACEScg" name OCIOColorSpace1 selected true xpos 1445 ypos 438 } push $N4d458970 Colorspace { colorspace_in AlexaV3LogC primary_in AlexaV3LogC name Colorspace1 selected true xpos 1577 ypos 438 } On Fri, Oct 28, 2016 at 11:18 AM, Neil Scholes <n...@uvfilms.co.uk<mailto:n...@uvfilms.co.uk>> wrote: Hey yes I do have raw checked…. double checked…… crazy negative values weird one I’m having to resort to standard nuke and use the basic colorspace node to convert from Arri LogC - shame really as i’d prefer ACES. I think its either a bug or the plate. Neil Rögnvaldr Scholes Director | VFX Supervisor www.neilscholes.com<http://www.neilscholes.com/> +44 (0) 7977 456 197<tel:%2B44%20%280%29%207977%20456%20197> On 28 Oct 2016, at 18:38, Haarm-Pieter Duiker <l...@duikerresearch.com<mailto:l...@duikerresearch.com>> wrote: Hey, Do you have 'raw data' checked on the read node? If you don't, Nuke apply it's own linearization when the data is read in, at which point the data flowing through the graph is no longer LogC encoded. Not checking that box could lead to problems like you're describing. HP On Friday, October 28, 2016, Neil Scholes <n...@uvfilms.co.uk<mailto:n...@uvfilms.co.uk>> wrote: Hi So I’m looking at supposed ARRI LogC footage - dpx's In ACES (1.0.1) converting from ARRI V3 LogC (EI800) Wide Gamut to ACEScg gives me horrible negative values …..big ones So I’m wondering - is there a bug with ARRI V3 LogC and ACES currently?, or is it likely that the plate is not actually LogC ? Thanks for any pointers N Neil Rögnvaldr Scholes Director | VFX Supervisor www.neilscholes.com<http://www.neilscholes.com/> +44 (0) 7977 456 197<tel:%2B44%20%280%29%207977%20456%20197> _______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk<mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/<http://forums.thefoundry.co.uk/> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> _______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk<mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/<http://forums.thefoundry.co.uk/> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> _______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk<mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/<http://forums.thefoundry.co.uk/> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> _______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk<mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com ---------------------------------------------------------------------------------------
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
