DeckBridge Gives Resolve a Smarter Stream Deck

For those who don’t know the tool: DeckBridge, operated by InspireX Ltd, builds application-aware plug-ins for Elgato Stream Deck hardware rather than static profile packs. Its Resolve plug-in sits between the deck and Blackmagic Design DaVinci Resolve, reading the active Resolve keymap, tracking page and timeline state through Resolve scripting, and optionally using MIDI for Blackmagic Design Fairlight mixer feedback.

It is not just a shortcut pack

DeckBridge for DaVinci Resolve is a native Stream Deck plug-in rather than a fixed profile pack. A conventional Stream Deck profile maps a button to a predetermined shortcut. DeckBridge instead keeps a live relationship with DaVinci Resolve, reads the active keyboard mapping and can react to application state.

The current Elgato Marketplace build is version 1.0.5, occupies 18.72 MB and requires Stream Deck 7.1 or later. DeckBridge provides profiles for Media, Cut, Edit, Fusion, Color, Fairlight, Deliver and Photo. They remain editable Stream Deck profiles, so operators can rearrange them, add pages and combine DeckBridge actions with other plug-ins rather than submitting to somebody else’s idea of the perfect Edit page.

491 commands and your own keymap

DeckBridge exposes all 491 keystroke-accessible commands in Resolve’s keyboard customisation inventory: 227 General, 198 Edit, 18 Color, 30 Fairlight and 18 Photo. A Command action stores the Resolve command identity rather than simply memorising the default shortcut. DeckBridge reads the active keymap, looks up the current binding and triggers that. Change the shortcut inside Resolve and the corresponding control follows without rebuilding the Stream Deck layout.

That is particularly useful for editors using Avid Media Composer-, Adobe Premiere Pro-, Avid Pro Tools-style or heavily customised mappings. Unbound commands appear greyed out. DeckBridge can also read exported Resolve .txt keyboard presets when automatic keymap discovery is unsuitable. Malformed presets are rejected rather than partially interpreted, which is reassuring. Partial shortcut maps are how Ripple Delete eventually becomes a personnel issue.

Ten actions cover more than buttons

DeckBridge ships ten Stream Deck actions: Transport, Command, Command Dial, Mixer, Timecode Dial, Page & Settings, Status, Timecode, Jog and Fader Pair. Transport handles playback and related commands. Command exposes the Resolve command inventory. Command Dial maps encoder movement to paired increment and decrement operations such as printer lights, stills, versions and node navigation, with an optional press command.

Mixer turns a dial-equipped Stream Deck into a compact Fairlight channel control. Rotation adjusts the fader, pressing toggles mute, and supported touch surfaces can expose mute, solo and record-arm controls. Resolve sends the channel value back over MIDI so the display can follow the mixer state rather than merely hoping it guessed correctly. The fader step is adjustable from 0.5 to 10 percent per encoder detent, with 2 percent as the default.

Timecode Dial combines timecode display with playhead jogging, while Page & Settings combines page information, connection state and timeline information with page switching and jogging. Button-only devices use alternatives such as Timecode, Jog and Fader Pair. On the Color page, selected controls can switch roles and address printer lights. A Stream Deck has therefore not become a grading panel, but it has stopped pretending every knob must do the same thing everywhere.

Profiles follow Resolve

DeckBridge associates its profiles with Resolve’s eight main pages and can switch the physical deck as the operator moves between them. Customisation stays local to each profile, so rearranging Color does not reshuffle Edit. DeckBridge can also remember which Stream Deck page was active inside a Resolve profile.

Plug-in updates leave customised profiles untouched. That prevents an update from redecorating a control surface minutes before a supervised session, although it also means newer default layouts are not injected automatically. Supported hardware includes Stream Deck +, MK.2, XL, Mini, Neo, Studio, + XL and Galleon 100 SD. Dial and touch-strip functions require devices that physically contain them, despite software’s long campaign against the laws of matter.

Fairlight adds bidirectional control

Most DeckBridge functions do not depend on MIDI. MIDI becomes relevant when Fairlight mixer state and transport illumination need to travel back from Resolve to the hardware. Resolve is treated as an MCU-compatible MIDI environment, allowing DeckBridge to receive fader and channel state as well as send control changes. That means the Mixer action can reflect the current Fairlight fader value together with mute, solo and record-arm state on supported hardware. Without MIDI, the keymap-aware commands, page handling and timecode functions remain available, while Fairlight feedback and related transport illumination are unavailable.

Free and Studio use different scripting paths

DaVinci Resolve Free and DaVinci Resolve Studio are intended to present the same DeckBridge functions to the operator, but they connect differently. Resolve Studio exposes external scripting, which DeckBridge can use directly. Resolve Free instead relies on an in-Resolve DeckBridge script. The difference matters mainly for deployment and troubleshooting rather than day-to-day operation. Once connected, the deck is intended to behave consistently across both editions.

Timecode occasionally has to improvise

DeckBridge distinguishes between exact and estimated timecode. During playback, Resolve does not always continue supplying exact timeline position through the API path DeckBridge uses. The plug-in then freeruns an estimate and identifies that state visually. When playback stops, it re-anchors to Resolve’s exact position.

Resolve Free adds a related limitation because its script host can be suspended during video-page playback. Playback indication also has a documented limitation on the Color and Fusion pages. If DeckBridge starts playback itself, it can infer that state. Playback initiated elsewhere may not update the deck’s illuminated indication until the next stop. The transport still works. The button is simply experiencing temporary uncertainty about objective reality.

Status is more than a green lamp

DeckBridge includes a Status action that reports whether Resolve, scripting and MIDI feedback are healthy rather than reducing troubleshooting to the traditional method of pressing the same button harder. Its diagnostics function can produce a local text snapshot containing version information, connection health, the active keymap, recent MIDI errors and recent log output. According to the developer, diagnostics do not include project contents or media and are not transmitted automatically.

Privacy stays local

DeckBridge states that the Resolve plug-in contains no telemetry, analytics, DeckBridge account system or DeckBridge network calls. Runtime logging remains on the workstation. Licensing is handled through the Elgato Marketplace EULA. DeckBridge uses no separate licence key or activation mechanism, while purchases, receipts and refunds are handled through Elgato. That removes at least one opportunity to discover at 08:57 on Monday that the licence belongs to somebody who left the company two years ago.

Compatibility needs one asterisk

DeckBridge documents Resolve Free and Studio 19 through 21 and requires Stream Deck 7.1 or later. Windows 11 is the documented Windows target, with older Windows configurations receiving more limited treatment depending on their available MIDI infrastructure.

There is one unresolved macOS discrepancy. DeckBridge lists macOS 12 or later, while Elgato’s current requirements state that Stream Deck 6.9 and later requires macOS 13 or later. Since DeckBridge itself requires Stream Deck 7.1 or later, those published requirements do not describe a consistent macOS 12 configuration.

https://deckbridge.io/