DaVinci Resolve DCTL and OFX Plugins

Tags: #<Tag:0x00007f58bb3d3608> #<Tag:0x00007f58bb3d3428> #<Tag:0x00007f58bb3d3270> #<Tag:0x00007f58bb3d2f78> #<Tag:0x00007f58bb3d2e10> #<Tag:0x00007f58bb3d2d20> #<Tag:0x00007f58bb3d2b68>

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:

Hi Paul!

thanks for the answer. That makes total sense.
You are right, I’m referring to the Frequency Separation OFX that was described in the ACES TOOLS video.

But with the context around CUDA you provided, I’ll try and get a different configuration to check it out!

Thanks again!

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.

By LMT_PFE_OFX, do you mean the actual DCTL? If you want export a version with updated settings, you can simply copy the original and then manually change the values in the text file.

The ACES OFX plugin can export both DCTLs and 3D LUTs, but the plugin itself is only CUDA and CPU compatible. The export options are CPU driven only, so should still work on a non-CUDA Mac.

Read back over the whole thread (and the LiftGammaGain one) for further information.

I’m updated the ACES DCTL repository on GitHub with the newer set (that contains just the single ACES_LIB.h file), which is compatible with CUDA, OpenCl, and Metal.

The older versions of the ACES DCTL set can still be found in the EXTRAS repository.

1 Like

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?
thanx everyone

I’m not quite sure I understand what you’re asking. The custom LMT option in the OFX Plugin has slider parameters, and any adjustments made are written into the exported DCTL.

If you want to ‘bake’ in any adjustments to any of the individual OFX DCTLs, just simply overwrite the default value in the text file with your new value, and then save it.

1 Like

thanks a lot, this is exactly what I was looking for.
It seems you implemented the LMT academy fix highlight magic matrix into PFE dctl (acescct), it’s true? it looks in a very pleasant way.

1 Like

Is there a tutorial on how to install these plug ins?

1 Like

ACES OFX Plugin now works using Metal on macOS in DR15 and DR16 (though not comprehensively tested).

DR15

https://github.com/baldavenger/Extras/blob/master/ACES_OFX_macOS_DR15_METAL.zip

DR16

https://github.com/baldavenger/Extras/blob/master/ACES_OFX_macOS_DR16_METAL.zip

1 Like

Hello Paul:

Do you drop the cube onto the LUT folder in davinci?

Excellent work @Paul_Dore!

Made a few revisions to the ACES OFX Plugin. The various versions can be downloaded from here:

The updated source files can be found here:

I’ve updated my ACES DCTL set to ACES 1.2

The new options are available in ACES_LIB.h and ACES.dctl

I will update ACES_COMBO.dctl and ACES OFX Plugin in due course.

1 Like

The ACES COMBO DCTL (the one with the drop down menus) has also been updated to ACES 1.2

It contains most of (but not all) the ACES transforms. There are also now individual OFX DCTLs for the different transforms i.e IDT, ACES csc, LMT, ODT (which includes RRT, and inverse ODT and RRT), and RRTODT (which includes the inverse options).

The big COMBO DCTL can take a few seconds to load at the beginning, but after that the performance is pretty fast. The compartmentalised DCTLs don’t seem to have this initial lag.

1 Like

ACES OFX Plugin has been updated to ACES 1.2

https://github.com/baldavenger/BaldavengerPlugins/tree/master/ACESPlugin

Source files:

https://github.com/baldavenger/BaldavengerOFX/tree/master/ACESPlugin

Updated BaldavengerOFX macOS installer:

https://github.com/baldavenger/Extras/blob/master/BaldavengerOFX.app.zip

2 Likes

ACES 1.2 Matchbox Shader

https://github.com/baldavenger/Matchbox/blob/master/Baldavenger%20ACES%201.2%20Matchbox.zip

Specific ACES transform shaders (ACEScsc, IDT, LMT, RRT, ODT, and RRTODT) are available in the folder, as well as a master shader that contains the whole collection.

2 Likes

Hi @Paul_Dore,

First of all, I’ve been actively using your tools, and I believe they’re magnificent. Really great. Mainly LMT_GRADE and LMT_PFE.

I found a problem using the DCTLs in Resolve 15.3, 16.1.2 and 16.2, though. An important one, even a blocker for using them in certain workflows. I realized that if I export the project or I grab a still of a clip’s grade, then the DCTL and it’s configuration does not get saved.

I wonder if this has happened to you and whether you have a workaround for this. In some workflows sharing and communicating grades is very important. I was thinking of maybe exporting the database instead of the project, but in some cases this will be very inefficient.

Let me know your thoughts!

I haven’t come across this (I have’t down a lot of testing in this area), but perhaps others have. Are you exporting the project or still to another system that has the same DCTL in its LUT folder? If you save a project (and possibly still) in 15.3 and open it in 16.2, then there might be a compatibility issue. Same goes for saving in 16.2 and opening in 15.3.

This might be something worth approaching the actual developers of Resolve about.

@Paul_Dore after doing some further testings, I figured out the problem.

The problem is the same as when you load a LUT and the system can’t find it. The thing is: if you export a project with Stills and LUTs it will install the LUTs on the recipient’s computer. If you use this option resolve will collect the luts but it will bypass the DCTLs and won’t add them to the ‘collect’. Also, when opening the project Resolve won’t let you know that those DCTLs are missing or where they should be place.e

The solution is that the person sending either the project or still (drx) using this DCTLs needs to also send the folder containing the DCTLs on the grading system. The recipient needs to place it exactly on the same spot on their LUT folder. Then it will all work.

Hopefully this helps some users!

Best,

J

1 Like