Re: [Nuke-users] Input Process not concatenating
Right, I was going to add that maybe "concatenate" is too Shake-eque a descriptor when referring to colour. The key thing I meant is "passes through the full float value". On 17 October 2016 at 21:51, christoph manz wrote: > On 10/17/16 at 3:32 AM, michaeld...@gmail.com (Michael Garrett) wrote: > >> Operationally Nuke wont concatenate any colour ops, only transforms. >>> >> >> Er, are you sure about that? ;D >> > > I guess it depends on the definition of "concatenate", but if you use it > in the way shake used it, according to the foundry, nuke won't... > from: > http://help.thefoundry.co.uk/nuke/9.0/content/comp_environme > nt/transforming_elements/node_concatenation.html > "Color nodes do not concatenate because Nuke works in a 32-bit float, > which is enough to avoid banding and visible round-off errors in color." > > I seem to remember that they also said that their 32bit engine is so much > faster then shake that it's not worth it. > > chris > > > > ___ > 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 > ___ 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
Re: [Nuke-users] Input Process not concatenating
On 10/17/16 at 3:32 AM, michaeld...@gmail.com (Michael Garrett) wrote: Operationally Nuke wont concatenate any colour ops, only transforms. Er, are you sure about that? ;D I guess it depends on the definition of "concatenate", but if you use it in the way shake used it, according to the foundry, nuke won't... from: http://help.thefoundry.co.uk/nuke/9.0/content/comp_environment/transforming_elements/node_concatenation.html "Color nodes do not concatenate because Nuke works in a 32-bit float, which is enough to avoid banding and visible round-off errors in color." I seem to remember that they also said that their 32bit engine is so much faster then shake that it's not worth it. chris ___ 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
Re: [Nuke-users] Input Process not concatenating
Well, it's an OCIO CDLTransform going into a Vectorfield. When they are connected in the node graph, the colour concatenates as expected. Or "passes through the full float value" - whatever you want to call it. But if the CDL Transform is an IP and the Vectorfield is a viewerProcess, then concatenation breaks. I did not exhaustively check all Viewer options, but I did toggle between GPU and non-GPU. GL Buffer depth set to half float. I figure anything but byte will work. IP is set before viewerProcess. Operationally Nuke wont concatenate any colour ops, only transforms. Er, are you sure about that? ;D Anyway, I've moved on for now but if anyone has a solution, I'd be interested to revisit this. On 17 October 2016 at 20:01, Tahl wrote: > and it went to the list ! > > > > -- > *From:* nuke-users-boun...@support.thefoundry.co.uk < > nuke-users-boun...@support.thefoundry.co.uk> on behalf of Tahl < > tahlni...@hotmail.com> > *Sent:* Tuesday, 18 October 2016 12:01:02 AM > *To:* Nuke user discussion > *Subject:* Re: [Nuke-users] Input Process not concatenating > > > Replying offlist. > > > typical. I am on a PC and dont have nuke installed. > > > Order of operation should be Image->CDL->display LUT. So unless there is > something in the CDL that is restricting the data being passed to the > display, I would say the issue is caused by the display buffer and what is > being passed to that > > what is your viewer bit depth set to ? > > Operationally Nuke wont concatenate any colour ops, only transforms. > However it does sound like you might be applying the second operation to a > display buffer with reduced colour depth ?! > > > So Nuke might actually be rendering the Data to an 8bit buffer as part of > the INPUT_PROCESS then applying the vLUT on top ? > > > > > -- > *From:* nuke-users-boun...@support.thefoundry.co.uk < > nuke-users-boun...@support.thefoundry.co.uk> on behalf of Michael Garrett > > *Sent:* Monday, 17 October 2016 10:33:36 PM > *To:* Nuke user discussion > *Subject:* [Nuke-users] Input Process not concatenating > > Not sure if this is common knowledge, but I'm guessing that it is: > I was looking into a workflow where I set the shot CDL as an input > process, with the show lut as a viewer process on top of that. > > Unfortunately, the input process and viewer process do not concatenate. I > end up with milky blacks and flattened highlights. So at this stage, it > looks like I will only burn the CDL into the dailies (sRGB, jpeg sequence > and h.264) as I can burn in the CDL and the show lut without concatenation > issues and all appears as it should. It would just be handy if the comp > artist had the ability to enable/disable the input process underneath the > show lut, to see the effect of the CDL. > > If anyone has any suggestions for how they do this, I'd be interested. Or, > maybe this is actually a bug, not a limitation? I'm on 10.0v4 Linux. > > Thanks, > Michael > > ___ > 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 > ___ 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
Re: [Nuke-users] Input Process not concatenating
and it went to the list ! From: nuke-users-boun...@support.thefoundry.co.uk on behalf of Tahl Sent: Tuesday, 18 October 2016 12:01:02 AM To: Nuke user discussion Subject: Re: [Nuke-users] Input Process not concatenating Replying offlist. typical. I am on a PC and dont have nuke installed. Order of operation should be Image->CDL->display LUT. So unless there is something in the CDL that is restricting the data being passed to the display, I would say the issue is caused by the display buffer and what is being passed to that what is your viewer bit depth set to ? Operationally Nuke wont concatenate any colour ops, only transforms. However it does sound like you might be applying the second operation to a display buffer with reduced colour depth ?! So Nuke might actually be rendering the Data to an 8bit buffer as part of the INPUT_PROCESS then applying the vLUT on top ? From: nuke-users-boun...@support.thefoundry.co.uk on behalf of Michael Garrett Sent: Monday, 17 October 2016 10:33:36 PM To: Nuke user discussion Subject: [Nuke-users] Input Process not concatenating Not sure if this is common knowledge, but I'm guessing that it is: I was looking into a workflow where I set the shot CDL as an input process, with the show lut as a viewer process on top of that. Unfortunately, the input process and viewer process do not concatenate. I end up with milky blacks and flattened highlights. So at this stage, it looks like I will only burn the CDL into the dailies (sRGB, jpeg sequence and h.264) as I can burn in the CDL and the show lut without concatenation issues and all appears as it should. It would just be handy if the comp artist had the ability to enable/disable the input process underneath the show lut, to see the effect of the CDL. If anyone has any suggestions for how they do this, I'd be interested. Or, maybe this is actually a bug, not a limitation? I'm on 10.0v4 Linux. Thanks, Michael ___ 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
Re: [Nuke-users] Input Process not concatenating
Replying offlist. typical. I am on a PC and dont have nuke installed. Order of operation should be Image->CDL->display LUT. So unless there is something in the CDL that is restricting the data being passed to the display, I would say the issue is caused by the display buffer and what is being passed to that what is your viewer bit depth set to ? Operationally Nuke wont concatenate any colour ops, only transforms. However it does sound like you might be applying the second operation to a display buffer with reduced colour depth ?! So Nuke might actually be rendering the Data to an 8bit buffer as part of the INPUT_PROCESS then applying the vLUT on top ? From: nuke-users-boun...@support.thefoundry.co.uk on behalf of Michael Garrett Sent: Monday, 17 October 2016 10:33:36 PM To: Nuke user discussion Subject: [Nuke-users] Input Process not concatenating Not sure if this is common knowledge, but I'm guessing that it is: I was looking into a workflow where I set the shot CDL as an input process, with the show lut as a viewer process on top of that. Unfortunately, the input process and viewer process do not concatenate. I end up with milky blacks and flattened highlights. So at this stage, it looks like I will only burn the CDL into the dailies (sRGB, jpeg sequence and h.264) as I can burn in the CDL and the show lut without concatenation issues and all appears as it should. It would just be handy if the comp artist had the ability to enable/disable the input process underneath the show lut, to see the effect of the CDL. If anyone has any suggestions for how they do this, I'd be interested. Or, maybe this is actually a bug, not a limitation? I'm on 10.0v4 Linux. Thanks, Michael ___ 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
[Nuke-users] Input Process not concatenating
Not sure if this is common knowledge, but I'm guessing that it is: I was looking into a workflow where I set the shot CDL as an input process, with the show lut as a viewer process on top of that. Unfortunately, the input process and viewer process do not concatenate. I end up with milky blacks and flattened highlights. So at this stage, it looks like I will only burn the CDL into the dailies (sRGB, jpeg sequence and h.264) as I can burn in the CDL and the show lut without concatenation issues and all appears as it should. It would just be handy if the comp artist had the ability to enable/disable the input process underneath the show lut, to see the effect of the CDL. If anyone has any suggestions for how they do this, I'd be interested. Or, maybe this is actually a bug, not a limitation? I'm on 10.0v4 Linux. Thanks, Michael ___ 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
