Troubleshooting

Common issues and solutions

Plugin not appearing in Resolve

• Make sure the OFX plugin is installed. Open the Nobe LutBake menu bar popover and check the plugin status. Click Install OFX Plugin if needed.

• Restart DaVinci Resolve after installing the plugin.

OFX plugin is not loading

If the OFX plugin was previously working but has stopped, or DaVinci Resolve shows:

No parameter is exposed to user or OFX Plugin is NOT available.

Try clearing the OpenFX plugin cache:

macOS

1. Close DaVinci Resolve

2. Open a Finder window, select Go > Go to Folder... and paste: ~/Library/Application Support/Blackmagic Design/DaVinci Resolve/

3. Delete the OFXPluginCache.xml file at this location

4. Relaunch Resolve

Windows

1. Close DaVinci Resolve

2. Open File Explorer and go to: C:\ProgramData\Blackmagic Design\Davinci Resolve\Support\

3. Delete the OFXPluginCache.xml file at this location

4. Relaunch Resolve

Re-enabling a blacklisted plugin

When an OFX plugin causes a problem or crashes DaVinci Resolve, Resolve blacklists it and will not load it again — even after reinstalling the plugin.

To re-enable it:

1. Open DaVinci Resolve Preferences

2. Go to the Video Plugins section

3. Tick the checkbox next to Nobe LutBake

4. Click Save and restart DaVinci Resolve

Capture times out

• Make sure you are on the Color page in Resolve with a clip selected in the timeline.

• Confirm the HALD Generator node label matches the label configured in the app settings (default: HALD). On DaVinci Resolve 20+, nodes are discovered automatically — if you see this error, make sure at least one Nobe LutBake node exists in the node graph.

• Check that the LUT Generator node (second LutBake node) is in the active processing chain and not bypassed.

• If using System python3 (default), make sure it is installed and accessible from the terminal (python3 --version).

• If issues persist, enable Use fuscript (advanced) in Settings > General > Python Interpreter to test Resolve's bundled interpreter.

LUT looks wrong or has artifacts

• Ensure both HALD Generator and LUT Generator nodes use the same HALD level.

• Check that the source image resolution is at least as large as the HALD pattern (e.g., 512x512 for HALD level 8).

• Make sure no spatial, temporal, or texture effects are active between the LutBake nodes. Blur, sharpening, noise reduction, glow, grain, denoise, and similar tools will corrupt the HALD pattern and produce a LUT that does not match your grade. Disable or move these effects outside the capture range.

• Make sure no resize, crop, or pan operations are modifying the HALD region in the top-left corner of the image.

• Use YRGB color science in Resolve for the most accurate results.

LUT does not match my grade

If the captured LUT looks different from your graded image in the viewer, spatial or temporal effects in the capture range are the most common cause.

A 3D LUT can only capture color-to-color transforms. Any effect that depends on pixel position (blur, sharpening, keyers, windows), neighboring frames (denoise, motion blur), or adds texture (grain, glow, lens flares) will produce a LUT that diverges from the on-screen result.

How to fix it:

• Disable or bypass all spatial/temporal/texture effects between the HALD Generator and LUT Generator nodes before capturing.

• Move these effects to nodes outside the LutBake capture range so they still apply to your image but are excluded from the LUT.

• Re-capture the LUT after making changes.

Built-in safety features: LutBake includes three layers of protection against spatial corruption:

1. Reminders in the setup wizard and settings to disable spatial effects before capture.

2. Preflight scan that automatically detects spatial effects before each capture. On DaVinci Resolve 20+, it uses the GetToolsInNode() API to identify 40+ known spatial tools (blur, sharpen, grain, noise reduction, Power Windows, and more) with cross-graph scanning between your two LutBake nodes. Unknown or third-party plugins are flagged via heuristic keyword matching. On older Resolve versions, it falls back to node label matching.

3. Auto-disable & restore — when the preflight scan detects spatial effects on Resolve 20+, you can choose to auto-disable them for the duration of the capture. Your original grade is restored automatically afterward via version rollback.

4. Post-capture LUT validation that mathematically analyzes the extracted LUT data for spatial corruption signatures and shows a warning if problems are detected.

The preflight warning dialog includes a "Don't warn again this session" checkbox if you want to suppress repeated warnings until the next app restart.

You can configure these in Settings > General under "Spatial Effects Safety."

Coming from Resolve's Generate LUT? Resolve's built-in Generate LUT function automatically bypasses spatial effects in OFX plugins. LutBake does not — it captures the full signal path between the two nodes, including any spatial or temporal processing. This is by design (it gives you full control over what is captured), but it means you must disable or move non-LUT-safe effects yourself.

"No nodes found" error

• Make sure you are on the Color page in DaVinci Resolve.

• Ensure a clip is selected in the timeline.

• If using Group Pre-Clip or Group Post-Clip, make sure the clip is assigned to a Color Group.

Plugin does not save LUT

• Check that the LUT Generator node has a valid Output Path set (either via the plugin UI or through the trigger file).

• If using the menu bar app, make sure the output folder exists and is writable.

• Check the Console.app logs for any error messages from the app.

DRX export fails

• DRX export requires a Gallery album to be accessible. Make sure the Gallery is not in a locked state.

• Resolve adds its own suffix to DRX filenames — the file may be saved with a different name than expected.

Keyboard shortcut not working

• Make sure the app is running in the menu bar.

• Check System Settings > Privacy & Security > Accessibility — Nobe LutBake needs accessibility permissions to register global keyboard shortcuts.

• If the shortcut conflicts with another app, change it in Settings > Shortcuts.

Python interpreter issues

The app uses a Python interpreter to communicate with DaVinci Resolve's scripting API.

• System python3 (default) — Your system Python 3 installation (Homebrew, python.org, etc.).

• fuscript (advanced) — Resolve's bundled Python interpreter, available as an advanced compatibility option.

If captures fail silently (HALD node does not toggle), try switching the interpreter in Settings > General > Python Interpreter. If fuscript works but system python3 does not, verify your Python installation and PATH. If system python3 works but fuscript does not, your Resolve installation path may be misconfigured — verify the Resolve path setting points to the correct .app bundle.