R&D: Converting DCTLs into native OFX plugins + Direct MIDI control in Resolve (Concept & Feedback)

Hi everyone,

I’ve been experimenting with a couple of workflow ideas for DaVinci Resolve around custom color tools and tactile control, and I wanted to share this concept with the community to get some thoughts.

The first part is about turning DCTLs directly into native OFX plugins. DCTL is wonderful for building looks and color transforms, but having those same tools running as clean, standalone OFX plugins is often much more practical for daily use and sharing. I have been testing a simple way to take standard DCTL files and automatically convert them into fully functional OpenFX plugins with their own sliders in the Inspector. The idea is to keep the code neat and protected, while keeping the exact same playback performance and GPU speed as the original DCTL.

The second part is about physical control. When adjusting OFX plugins or custom tools in the Color page, we usually have to rely on the mouse to move sliders in the Inspector. Instead of using tools that simulate mouse clicks or read the screen, I’ve been prototyping a way to connect standard USB MIDI controllers, like simple knobs and faders, directly to the plugin controls. The sliders move natively inside Resolve, normal Undo (Cmd+Z) works as expected, the mouse stays completely free, and it works even in full screen.

I’m curious to see how this resonates with people grading day to day. Would this kind of setup be useful in a real post-production environment, and is there a favorite MIDI controller that comes to mind for this?

Thanks for any feedback!
 
On the first thought, a number of Paul Dore's tools are avb as both DCTL and OFX , i go to the OFX option first, faster as the OFX are sorted, and the DCTL's are a PITA to sort through to find the one i want

on the second thought...
before i put the BMD mini on a shelf it had direct control of a limited number of sliders for OFX, works well as expected, but getting to the menu was slow to the point it was faster to grab a mouse / pen and tweak there

now running tangent elements, streamdecks and tangent warper tp control OFX.sliders, my day goes faster with this setup

but ten years ago I used the DJ Twister running through Bome MIDI to control Resolve via command -to-mouse
the twister surface is built like a vault, paired it with Xkeys and Artist color & transport
Bome was the weak link....
Screen Shot 2026-10-29 at 11.45.48 PM copy.jpg

my Twister's are still on a shelf waiting for someone to come up with workable mapping
 
Last edited:
Thanks for the feedback, Dermot.

On the DCTL side, I already have a self-service DCTL-to-OFX builder running with built-in IP protection. Testing and deployment are at an advanced stage, and I plan to open a sandbox soon so anyone interested can test their own files and help catch edge cases.

Regarding MIDI, I don't own a Midi Fighter Twister yet, though I know other colorists are in the exact same situation with theirs. I actually ended up building my own custom MIDI hardware controller just to develop and test this. The PoC is already working: it drives the OFX parameters directly without touching the mouse, and best of all, I can adjust multiple sliders simultaneously, which is something mouse-emulation wrappers cannot do.

I will keep this thread updated as development progresses. I'll definitely need help testing on different hardware setups, so if you're interested in trying an early prototype with your Twisters, I'd be glad to send it over when ready.
 
please send it over when it's the right time!

i'll pull one of the twisters out of storage next week, looks pretty sitting on the desktop - even if it does nothing for now;-)
 
Hi Magno,

Interesting thinking about porting DCTLs to OFX. I have done the same with some of mine. In my own workflow, though, I find a place for both. Some of my DCTLs are very simple by design, so porting them wouldn’t make much sense, they would take up too much space in the OFX column. But I definitely see the idea if you plan on selling and sharing. The ability to encrypt DCTLs is great, but also a bit limiting for license management.

I’m toying around with a similar workflow, controlling OFX's via MIDI. I’m planning on getting a MIDI Fighter Twister at some point. it seems like the most polished and established choice. At the moment I’m controlling it with a Stream Deck that sends MIDI through a plugin. I would love to test your implementation.

How did you get the viewer to refresh when a parameter changes via MIDI? In my tests, Resolve accepts the new value from the OFX, but the viewer doesn’t re-render until I interact with the UI. I can get around it with an eksternal script, but it would be nicer with a cleaner method.
 
Hi Jonas,

I agree that not every utility DCTL needs to be ported. The main problem in Resolve's UI is having every DCTL buried inside that single dropdown menu, which makes them slow to find.

My solution is a self-service builder. If you have a specific DCTL that you use frequently, you can convert it with a single command. That moves the tool out of that long dropdown list and turns it into a native OFX plugin with built-in encryption to protect your core code. It also generates binaries for both macOS and Windows from the same source, whether you want to distribute it for free or manage licenses commercially.

Regarding the Viewer refresh issue with MIDI, I ran into the exact same limitation early on. Solving that cleanly without relying on external scripts or workarounds was the most complex part of the PoC. The implementation makes Resolve register incoming parameter changes as a legitimate state update, keeping the Viewer rendering in real time while preserving native Undo history.

Using a Stream Deck to send MIDI events is a solid test case, especially for step increments and resets alongside continuous encoders like the Twister.

I am still closing a few gaps in the implementation, and I would like to count on you soon to evaluate the solution on your setup.
 
Hi everyone, dropping by for a quick update on the ongoing tests.

I recorded a short screen capture showing real-time parameter response:

Direct Parameter Control (No Mouse Hijacking)
The main detail to notice in the video is that the parameters update smoothly while the mouse cursor moves freely across the screen. There is no GUI automation, synthetic mouse drag, or coordinate injection capturing the OS pointer. Communication happens directly under the hood without interrupting user interaction in Resolve.

MIDI Inheritance from DCTL to OFX
An important architectural point: any DCTL converted into a native OFX automatically inherits this entire MIDI control layer. This means sliders, dropdown menus, and checkboxes become immediately controllable via external hardware out of the box.

Hardware Integration (Midi Fighter)
Communication is mapped for several controllers, with primary calibration currently focused on the Midi Fighter (Twister), taking advantage of its continuous rotary encoders and bank switching.

Current Build Status
The implementation is currently in a near-final build. Current efforts are centered around stress testing, stability during active timeline playback, and fine-tuning edge cases.
 
Back
Top