Prebaked LUTs of the ACES 2.0 CAMDRT Prototype from the ACES Output Transforms Architecture Virtual Working Group
This repo contains:
- a Nukescipt used to bake the LUTs.
- A dctl template to wrap them in a way Resolve will treat as a valid ACES ODT.
- A FilmLight Display Rendering Transforms intended for use in Baselight.
- OCIO configs, both for standard Linux/Windows environments, and Macs using EDR displays.
Inverse Transforms are now implemented for all platforms.
There is a cutdown OCIO config based on the current ACES 1.2 config. It includes all Input and Utility spaces, but a greatly reduced set of Output spaces.
There are two config variations:
-
A
_Limited.ocio
for general use in Nuke on Linux and Windows, and other generic OCIO applications. -
A
_DisplayP3.ocio
intended for use with Nuke 13 on a Mac with EDR support. This can be enabled via thePreferences -> Color Management -> Enable macOS HDR Color Profile
checkbox, and setting thegl buffer depth
tohalf-float
in the Viewer settings pane. -
And an
_All.ocio
config will both sets of transforms. (Useful, but can mean the View menu is a bit overloaded)
-
Copy all the files contained in
ACES2_Candidates_rev060
to the colourspace folder- Linux & Mac:
/vol/.support/etc/colourspaces
- Linux & Mac:
-
Restart Baselight
-
You should see three new custom DRTs in
Scene Settings -> Format & Colour -> Display Rendering Transform
-
Navigate to the
ACES Transforms
folder in Resolve's application support folder.- MacOS:
~/Library/Application Support/Blackmagic Design/DaVinci Resolve/ACES Transforms/ODT
- Windows:
C:\Users\<User>\AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\ACES Transforms\ODT
- Linux:
~/.local/share/DaVinciResolve/ACES Transforms/ODT
- MacOS:
-
Copy the
ACES2 Candidates rev060
folder into the ODT folder. -
Start Resolve.
There are two pathways for testing the candidate transform in Resolve.
Using a standard ACES mode project the OT candidates can be found under the ACES Output Transforms
submenu.
The only caveat here is that Resolve currently doesn not support output space tagging for custom DCTL transforms, so whilst they will work as expected with external monitors, they will no be picked up correctly if you use "Use Mac display color profiles for viewers" option, which in turn means EDR/HDR display will not work correctly.
You can also set you project to use the stock DaVinci YRGB
colour science mode.
And then drop an ACES Transform node at the timeline level.
The advantage of this method is that EDR display on the Mac will work properly, as will the ouput scopes.