This should be changed back to uppercase. I was running tests with the new Combo Box option and there was a conflict, but uppercase maintains compatibility with the ACES 1.1 plugin.
I forgot to add the 00 to the end of the function name. The function itself is a direct translation from the original CTL header, which was probably not intended for use within Resolve in its current form. It’s in the library purely for the sake of inclusion. The exp_factor is what is returning super high values (it’s 36 in the original CTL).
The ACES DCTL set should be used in Resolve YRGB, but the LMTs can be used in Resolve ACES (provided they included a conversion to and from ACEScct). In Resolve YRGB and Resolve ACES you can apply a DCTL as an input transform (pre node graph), within the node graph (clip level, and timeline), and as an output transform (post node graph). Fully modular. In Resolve ACES at the input level, the DCTL is applied before the conversion from ACES to ACEScct (or ACEScc), so an IDT DCTL can be applied here if not natively supported in Resolve.
Thanks to Nick Eason (over at LGG) I was able to precompile the full ACES transform library into a single header file, which can be included in a DCTL in both Metal and CUDA. The ACES_Sample option than was previously only available in CUDA is now available in Metal too. I tried OpenCL, but only the IDTs and some LMTs would work.
In a separate folder called ACES_DCTL_NEW I’ve added 3 files
ACES_LIB.h contains the full ACES transform library, ACES.dctl has a similar layout to ACES_Sample.dctl from the original ACES_DCTL set, and ACES_COMBO.dctl works in DR16 with the DCTL OFX Plugin.
Yes. The ARRIRAW IDTs should not be used in Resolve, as Resolve never presents the image data in its raw form, even if the source is ARRIRAW. It is already decoded. The value 36 is the multiplier from sensor linear to relative scene exposure at EI800. When that is incorrectly applied to image data which is already had EI gain applied, it will indeed produce ridiculously high values.
I converted the ACES transform library into a Matchbox Shader. It works in Flame, but I haven’t tested it in Baselight or Scratch (or any other app that can run these shaders).
It has a similar UI to the combo box DCTL in Resolve. There are a few options included in the drop down menus, but the entire library is included in the .glsl file so the remaining options can be added as required.
Thanks so much for the efforts you’ve put into this. It took me a while, the first time I came here I did not understand the scope of everything you had done. Now I get it and it’s amazing you’re dedicating the time to the community.
Having an exposure controller for resolve and this alternatives to keying are just amazing.
On aproblem note:I tried installing the Edge Detect on the ofx folder but it won’t show up! And I believe that, specially for HDR grading this is very, very interesting.
What could be causing the issue?
I have a MBP 2018 on macOS 10.14.6.
Using Resolve 16.0.0
It’s a specifically strange behaviour from the ADX10 IDT in the old ACES DCTL set. It works fine in the ACES OFX Plugin and the new ACES DCTL set. I recommend switching to the new set (with the single library file).
Most of the OFX Plugins are CUDA only, which rules out your MacBook (no Nvidia). There may be, in the future, updates to the plugins that add OpenCL or Metal compatibility.
On aproblem note:I tried installing the Edge Detect on the ofx folder but it won’t show up!
No Edge Detect plugin. Perhaps you mean the Convolution plugin (which has an Edge Detect option). The Convolution plugin is perhaps more a showcase tool than a practical one. You’re better off using Resolve’s native OFX Plugin instead.
This thread (and website) is specifically for ACES related inquires, whereas yours seem to be of a more general nature. Perhaps you should try a more appropriate channel instead:
Also, Paul, in playing with the LMT_PFE_OFX I get some great results. Thanks for that too!
I wonder if you have plans of adding the ability of exporting the LMT with adjusted settings as a dctl or as a cube.
Paul, I’m grading in AcesCct workflow on dr15 with your dctl scripts and plugins fully integrated in my company workflow.
the client (a huge vod streaming service) asks me for an exr ap0 graded dsm and a nam (non graded archival master) with the complete dctl set adopted to grade. this for long term archival storage purpose. they do not ask for the dr project, but just the luts/ctl/dctl package.
I know that plugins have the dctl script export option, but what about the parametric / slider-based dctl loaded in ofx --> dctl --> LMT.xxx.dctl?
the question is: is there a simple way to set the slider-param into the script? in other words, how can I export (or edit in the script) a fixed-dctl from a slider-based-dctl?