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:
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 foun
upport.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
>
>
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
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
