Nobe Color Remap plugin can work in CUDA, OpenCL and Metal (macOS only) GPU mode. It can also work in CPU mode but the plugin is designed to work on the GPU processor and in CPU mode will be simply slow.
There are a couple of settings that control the plugin processing pipeline.
- DaVinci Resolve GPU settings (Auto/CUDA/OpenCL/Metal)
- OpenFX plugin settings (CPU/GPU)
- GPU mode setting in the plugin’s options (Auto/CUDA/OpenCL)
DaVinci Resolve GPU settings
The GPU mode option in DaVinci Resolve settings controls how the program works internally and will control the way the image is processed by the plugin within Resolve during playback and generally in the Overlay Mode.
The available options here are OpenCL, CUDA, Metal and Auto:
The only thing that we can change here is to force the CPU processing of the plugin in the OpenFX section using the drop-down setting:
GPU settings in the plugin options
The Settings window accessed through the Options menu shows GPU mode as well. This option controls how the plugin works in Window Mode only. When the plugin is used in this mode the processing is independent from Resolve and can be set differently (For example DaVinci Resolve can be working in OpenCL mode and the plugin in CUDA mode). Setting this option to Auto will use the same processing mode DaVinci Resolve uses (set DaVinci Resolve in GPU settings).
Advanced GPU settings
OpenCL device ID can be specified in the config file manually in case the wrong device is selected (multi GPU systems).
The config file can be located:
- Windows: C:\Users\USERNAME\Local\NobeColorRemap\config.json
- macOS: /home/users/USERNAME/Library/Application Support/NobeColorRemap/config.json
The OpenCL device entry is called opencl_device and it should be added to the config file like this:
DaVinci Resolve 16+
When upgrading from earlier versions of Resolve the Color Distribution graph can suddenly disappear.
To fix it make sure the below config option in the plugins’ settings (overlay mode) is disabled:
Please note that the above option will cause major slow downs, when unchecked on older versions of Resolve (14 and 12.5).
So as a general rule please use the following:
- Direct Frame Access enabled in DaVinci Resolve 12.5, 14,
- Direct Frame Access disabled in DaVinci Resolve 15, 16, 16.1+.