Grab the latest, 1.0.3, OCIO config. This includes a D65 sRGB Output
Transform.
HP
On Wed, Apr 19, 2017 at 2:51 PM Rich Bobo wrote:
> OK, here’s a dumb question for those who have spent some time with an ACES
> color workflow…
>
> Is there any easy or recommended way to use
i 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
>
> +44 (0) 7977 456 197
>
> On 28 Oct 2016, at 18:38, Haarm-Pieter Duiker <l...@duikerr
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,
Hey,
When bringing in plates from a different space, you want the destination
space to be 'ACES - ACEScg' as ACEScg is the working space. You can convert
to 'ACES - ACES2065-1' and then to 'ACES - ACEScg', but there's really no
need to go to the 'ACES - ACES2065-1' space in this case.
For the
Hi,
I'm the author the OCIO config. People call me HP. I don't work for Hewlett
Packard.
We went through a fair amount of testing and discussion before arriving at
the role settings for the ACES OCIO config. If you're linearizing a plate,
you should use the OCIO Colorspace node to go between the
The RRT and ODT are two separate components that aren't exposed at the user
level. To the user, they are combined to form an ACES Output Transform for
a specific class of display, like Rec. 709, Rec. 2020, sRGB, P3-D60, P3-DCI
and so on.
To borrow from Alex Fry's short description from the other
You probably want the 'Utility - sRGB - Texture' for the In colorspace.
That will apply the 'sRGB to linear' mapping that you're probably familiar
with as well as map from the sRGB gamut to the ACES gamut.
Still, the results won't exactly match, but that's intended. Think of the
ACES Output
I asked off-list about others' experience with the issue. Here's the
response from Kevin Wheatley of Cinesite:
"
nuke does not support the chromaticity attributes at all and strips them
out on reading and has no support for writing them.
Just like most apps don't.
"
If you can configure RV to
If the built in SphericalTransform doesn't work, give this BlinkScript
node a shot
http://www.nukepedia.com/blink/transform/environmenttransform
HP
On Friday, August 21, 2015, Deke Kincaid d...@thefoundry.co.uk wrote:
Any reason why you can't use the supported sphericalTransform node? Also
There's a Blink script implementation of SphericalTransform here.
http://www.nukepedia.com/blink/transform/environmenttransform
Might help.
HP
On Sun, Oct 12, 2014 at 11:49 AM, Michael Garrett michaeld...@gmail.com
wrote:
I'm using SphericalTransform in Nuke 8.0v5 on Windows 7 and it's
I took maths for the angular map transform (latlong to angular, I
think) from an old Debevec Siggraph paper or something, or maybe the book
he wroteso maybe that was yours too! Since I know you worked with him
on all that interesting stuff.
On 25 August 2014 03:17, Haarm-Pieter Duiker l
Hey,
This also works as a workaround.
float acosWorkaround(float x)
{
return 3.14159f/2.f - asin(x);
}
Seems to be a little more reliable.
HP
On Mon, Jun 16, 2014 at 2:37 PM, Mads Lund madshl...@gmail.com wrote:
A little headsup for people doing blink-scripts.
The implementation of Acos
Hey,
That environment blur script has the start of what you need for a panorama
transform node. That script defines the function 'spherical_tex2dir' that
maps UV coordinates to directions. Define the inverse of that, mapping a
direction back to UV coordinates and you have what you need for the
13 matches
Mail list logo