Thanks for the replies. Will check thoses documents
Ok I have just downloaded the profile and its working fine. Now I just tried something very simple to see if I understand the workflow, and again, looks like I don't.. I just took a simple colorbar and rendered it as srgb in an exr file. Then I import the render, switch Nuke to OCIO with the new profile. Set the colorspace in the exr to RAW Drop a OCIOColorSpace IN: Utility - Curve- sRGB OUT: ACES - ACEScg Viewer is sRGB D60 sim. (ACES) ShouldI be expecting the same result that I would have in a regular Nuke config? Is "Utility - Curve- sRGB" the right input for srgb color images? ________________________________ From: nuke-users-boun...@support.thefoundry.co.uk <nuke-users-boun...@support.thefoundry.co.uk> on behalf of Feli di Giorgio <fe...@earthlink.net> Sent: Friday, February 5, 2016 8:13 AM To: Nuke user discussion Subject: Re: [Nuke-users] Aces RRT vs ODT A related question. Here is an extract from the Nuke manual. In addition to the instructions that Harm-Pieter posted does the last step titled 'All Platforms' still apply or is this information in the Nuke manual outdated? thanks Feli NOTE: Nuke is bundled with a pre-compiled version of the OpenColorIO library and a suite of OCIO nodes. If you already have a pre-built version of the OCIO library on your system and your environment is not set up correctly for Nuke, you may encounter problems. For OCIO to work correctly, Nuke requires the compiled versions of PyOpenColorIO and libOpenColorIO to match. To override Nuke's pre-packaged version with your own custom version, follow the steps below: Linux: Manually replace the Nuke packaged versions of libOpenColorIO.so and PyOpenColorIO.so with your custom versions of these files. These can be found in the <NukeInstall> and <NukeInstall>/plugins directories respectively. Mac: Set your NUKE_PATH to the location of PyOpenColorIO.so and your DYLD_LIBRARY_PATH to the location of OpenColorIO.so. For example: export NUKE_PATH="/myOCIOLibraryLocation/" export DYLD_LIBRARY_PATH="/myOCIOLibraryLocation/" NOTE: Due to an Apple security update in Mac OS X 10.7 (Lion), DYLD variables can't be loaded from the environment.plist. See http://support.apple.com/kb/TS4267 for more information. OS X Lion v10.7.4, Security Update 2012-002: Global DYLD launch variables no longer loaded - Apple Support<http://support.apple.com/kb/TS4267> support.apple.com With OS X Lion 10.7.4 (or Security Update 2012-002 for Snow Leopard) installed, DYLD launch variables will not load from the ~/.MacOSX/environment.plist file. If an application depends on the presence of such a variable, it may not open after you install the OS X Lion v10.7.4 Update or Security Update 2012-002. Windows: Both OpenColorIO.dll and PyOpenColorIO.pyd must be in the same directory. You then need to set your NUKE_PATH to this directory. For example: set NUKE_PATH=\myOCIOLibraryLocation\ THIS SECTION BELOW (FELI) All Platforms: In addition to the steps above, you need to set the OCIO environment variable to point to your OCIO configuration file. This overrides the configuration file specified in Nuke's preferences (see Setting Preferences). For example: export OCIO="/myOCIOConfigLocation/config.ocio" The OCIO nodes in Nuke are compiled against a specific version of the OCIO libraries (for the current version, see Third-Party Libraries and Fonts). If you're using your own custom libraries, recompile the OCIO nodes against your versions of the libraries. Failure to follow these steps may result in errors when adding OCIO nodes or modifying OCIO options in the preferences. ____________________________________________________ www.felidigiorgio.com fe...@earthlink.net
_______________________________________________ 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
