Feature Request: Add Option to Enable Metal Backend in macOS OFX Plugin

[felipeip182]

Describe the issue

I’m currently using Gyroflow’s OFX plugin in DaVinci Resolve on macOS (Hackintosh with full Metal 2 support). While version 1.3.0 of the plugin works flawlessly — and appears to use the Metal backend — all versions from 2.0 onward rely exclusively on OpenGL, which causes heavy artifacts when stabilizing certain files.

This issue happens consistently when processing H.265 10-bit 4:2:2 footage (from a Sony ZV-E1), and only under OpenGL. When Metal is used (like in v1.3.0), there are no artifacts and the performance is much better.

Expected behavior

I would like to be able to use the newer 2.x versions of the plugin, which include many improvements, while keeping the Metal backend active — either via:

A plugin parameter,

An environment variable like GYROFLOW_BACKEND=metal,

Or a custom build flag.

Attempts so far

I’ve already tried custom-building the plugin.

The backend logic seems abstracted (possibly into gyroflow_plugin_base).

I attempted to manually override strings in the .ofx binary to force Metal (e.g. replacing "OpenGL" with "Metal\0\0"), but this is not a sustainable solution.

Feature Request

Please consider adding a toggle for Metal backend rendering in macOS builds of the OFX plugin. Alternatively, if the backend logic is flexible in the codebase, I’d love a hint on where to force Metal as default.

I’d be happy to test builds or patches if needed.

System details:

macOS 10.15

DaVinci Resolve Studio 20

GPU: AMD RX 6600 (Metal 3 supported)

Gyroflow OFX v2.0.2.136 = OpenGL → artifacts

Gyroflow OFX v1.3.0 = Metal → no artifacts

Thanks so much for your amazing work!
Felipe Idrovo
📧 info@felipeidrovo.com
🌐 www.felipeidrovo.com

[AdrianEddy]

set NO_OPENCL=1 environment variable

[felipeip182]

Thanks, @AdrianEddy That command worked, but it completely disabled both OpenCL and Metal, forcing DaVinci Resolve to run on CPU only, which is extremely slow on my setup.

As a temporary workaround, I’m launching Resolve with this command:

NO_OPENCL=1 /Applications/DaVinci\ Resolve/DaVinci\ Resolve.app/Contents/MacOS/Resolve

However, I’m now looking for a permanent solution that disables only OpenCL while still allowing Resolve to use Metal rendering efficiently.

Any ideas or flags I can use to force Metal rendering while keeping OpenCL off?

Thanks again for your time and help!

[AdrianEddy]

NO_OPENCL should disable only OpenCL and leave Metal as default. What's in the log?
you can open the log directory from the gyroflow app -> advanced -> open data directory

[felipeip182]

Thanks, @AdrianEddy . In the standalone Gyroflow app I don’t have any issues selecting either Metal Render or OpenCL Render — everything works perfectly there.

The problem only appears with the latest OFX plugin inside DaVinci Resolve. When I set NO_OPENCL=1, instead of falling back to Metal, it ends up using only the CPU (super slow).

Also, I can't seem to access the logs via the plugin inside Resolve, and the logs folder doesn't get generated in the usual location (~/Library/Application Support/Gyroflow).

Any ideas?