# GPU Configuration and Troubleshooting

Nobe Color Remap supports GPU processing in **CUDA**, **OpenCL**, and (on macOS) **Metal**.

CPU mode is also available, but it is much slower and intended only as a fallback.

Processing behavior depends on three settings layers:

* DaVinci Resolve GPU mode (`Auto` / `CUDA` / `OpenCL` / `Metal`)
* OpenFX plugin processing mode (`CPU` / `GPU`)
* Nobe Color Remap settings for Window Mode (`Auto` / `CUDA` / `OpenCL`)

## DaVinci Resolve GPU Settings

Resolve GPU mode controls how Resolve processes frames internally and affects plugin processing in **Overlay Mode**.

Available options include OpenCL, CUDA, Metal, and Auto:

![](https://timeinpixels.com/wp-content/uploads/2018/10/resolve_gpu_settings.jpg)

You can also force plugin CPU processing in the OpenFX controls:

![](https://timeinpixels.com/wp-content/uploads/2018/10/ofx_gpu_settings.jpg)

## GPU Settings in Plugin Options

The plugin Settings window also has a **GPU mode** option.

This setting applies to **Window Mode only**. Window Mode processing runs independently from Resolve, so it can use a different backend.

Example: Resolve can run in OpenCL while the plugin dialog runs in CUDA.

If set to **Auto**, Window Mode follows the GPU mode currently used by Resolve.

![](https://timeinpixels.com/wp-content/uploads/2018/10/plugin_gpu_settings.jpg)

## Advanced GPU Settings

On multi-GPU systems, you can set the OpenCL device manually in `config.json` using `opencl_device`.

Typical config file locations:

* Windows: `C:\Users\USERNAME\AppData\Local\NobeColorRemap\config.json`
* macOS: `/Users/USERNAME/Library/Application Support/NobeColorRemap/config.json`

Add or edit the `opencl_device` value in the config file:

![](https://timeinpixels.com/wp-content/uploads/2018/10/config_file.png)

## DaVinci Resolve 16+ Notes

When upgrading from older Resolve versions, the Color Distribution graph may disappear.

If that happens, make sure the option shown below is **disabled** in plugin settings (Overlay Mode):

![](https://timeinpixels.com/wp-content/uploads/2019/08/Screenshot-2019-08-30-15.30.14.png)

On older Resolve versions (12.5 and 14), disabling this option can cause large slowdowns.

Recommended legacy setup:

* Resolve 12.5 and 14: **Direct Frame Access enabled**
* Resolve 15, 16, 16.1+: **Direct Frame Access disabled**

## Collecting Logs for Bug Reports

Include plugin logs when reporting issues. Use the **Logs** button in the utility app:

![](https://timeinpixels.com/wp-content/uploads/2019/08/Screenshot-2019-08-30-15.19.13.png)

![](https://timeinpixels.com/wp-content/uploads/2019/08/Screenshot-2019-08-30-15.12.41.png)

## Image/Viewer Issues Checklist

If viewer image issues appear, or if Color Distribution is missing in Overlay Mode, try:

* Disable **Enhanced Color Picker** in Options > Settings
* Enable **Fetch RGBA Texture** in Options > Settings
* Disable **Use optimized image transfers for viewers** in Resolve
* Disable **Direct frame access** in plugin settings

![](https://timeinpixels.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-25-at-23.26.08.png)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.timeinpixels.com/nobe-color-remap/guide/gpu-configuration-and-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.