Support

Yes on every version. On Resolve Free up to 21.0, DeckBridge installs a small bridge script into Resolve's own Scripts menu and transport, commands, pages and timecode all work. Resolve 21.1 removed scripting from the Free edition, so on Free 21.1+ DeckBridge instead reads Resolve's on-screen state directly: page, timeline and mixer (with default track names) update live, and keys and dials work fully.

The one gap on Free 21.1+ is the timecode display, which shows dashes - Resolve exposes no way to read the playhead position without scripting. Studio users are unaffected on every version. See the setup guide §6.

Almost always an out-of-date Stream Deck app: DeckBridge needs Stream Deck 7.1 or newer - the version that introduced the Node.js runtime it runs on - plus macOS 13+ or Windows 10+. Update the Stream Deck app first, then install DeckBridge again. If you downloaded the file in a browser rather than installing from the Marketplace inside the app, also check the Stream Deck app is signed in to the Elgato account you got DeckBridge with. Still stuck? Send us your Stream Deck app version and OS below.

Right after installing, a freshly loaded plugin's settings panel can open blank until the Stream Deck app restarts. Quit the Stream Deck app completely and relaunch it once, then select the tile again - the settings (MIDI ports, Reinstall default profiles, Diagnostics) will be there. You only need to do this once, straight after install. Also make sure you're on the Status key - that's the settings hub; the Timecode key has no settings of its own.

DeckBridge reads your active Resolve keymap, whatever it is - built-in presets, custom presets, any layout. Keys fire the binding Resolve itself has for that command, and follow along live when you rebind.

On macOS it adds two persistent IAC buses (DeckBridge Out / DeckBridge In) to the system MIDI configuration - after storing a timestamped backup of your pristine config in DeckBridge's data folder, kept until you uninstall and restorable from there at any time. If you delete that folder yourself the backup goes with it: uninstall still removes DeckBridge's own buses cleanly and leaves your devices untouched, but can no longer tell whether the IAC Driver was enabled beforehand, so it leaves it on. There's no Enable MIDI press on Windows: Windows keeps MIDI-loopback creation out of app reach, so DeckBridge can't add one for you - see the Windows MIDI setup question below. Faders and transport lights need it; everything else works without.

Windows doesn't let apps create MIDI loopbacks, so DeckBridge can't do what it does on macOS. Install a loopback tool once and create a pair - name it right and DeckBridge finds it on its own, no dropdown needed. Two options, either works:

• loopMIDI (free, from Tobias Erichsen, works on every Windows version today) - create two ports named exactly DeckBridge Out (A) and DeckBridge In (A)
• Microsoft's Windows MIDI Services tools (currently Release Candidate, so a separate install today; ships built into Windows 11 25H2, rolling out from around late 2026 - once it's in-box, this step should get simpler) - in the Settings app's MIDI panel, create two loopback pairs named DeckBridge Out and DeckBridge In, which get (A)/(B) appended automatically

Named them differently, or reusing an existing loopback? Just name them anything you like and select them yourself in DeckBridge's MIDI in/out dropdowns (Status key settings). Then set Resolve's Control Panels MIDI In/Out to the pair, crossed over: the (B) ends for Windows MIDI Services, or the (A) ends for loopMIDI. Restart Resolve once. This only affects the mixer/faders - transport, commands, page following and timecode all work without MIDI. Full steps are on the setup guide.

Yes - quit Resolve first. Enabling MIDI restarts the macOS MIDI service so your new buses appear, and a running Resolve can crash when that happens (most often with its Preferences window open), losing any Control Panels settings you hadn't saved.

That's why the deck shows Enable MIDI before Open Resolve, and why the setup guide has you press Enable MIDI with Resolve closed, then open Resolve and point it at the DeckBridge buses. It's only worth remembering if you come back and press Enable MIDI again later - enabling MIDI is a one-time step.

Quit and reopen Audio MIDI Setup, then look again under Window → Show MIDI Studio → IAC Driver. Its MIDI Studio window doesn't refresh when the configuration changes underneath it, so buses added while it's open stay invisible until you reopen it - they're already there and already working.

The reliable check is the deck itself: the Status key goes green once Resolve is wired to the buses.

Greyed means "this can't act right now, and pressing won't pretend otherwise": Resolve is closed, no timeline is open, or that command has no binding in your keymap yet - assign one in Resolve's Keyboard Customization and the key lights up by itself within seconds.

Press Stop - it always resyncs. With MIDI connected, the key follows Resolve's real transport state on the Cut, Edit and Fairlight pages. The Color and Fusion pages are different: Resolve doesn't report play state there at all, with or without MIDI and on Free and Studio alike, so on those pages the key always works the way it does without MIDI.

Without MIDI the deck has no way to hear Resolve, so it assumes your press did what you asked. If playback was already started or stopped from the keyboard, or Resolve ignored the key, that assumption drifts out of step. Enabling MIDI fixes it properly. Fast-forward and rewind never show a false state, because multi-speed shuttle is never guessed at.

No, and it fixes itself. Restarting the Stream Deck app also restarts DeckBridge, and on macOS the system MIDI service shuts down with it and takes a moment to come back. If DeckBridge starts during that gap it stops, and the Stream Deck app starts it again about ten seconds later with everything restored - your MIDI setup, buses and settings are untouched.

It's most likely on a Mac with little or no other MIDI equipment configured. If the keys stay blank for much longer than that, send us Copy Diagnostics.

Stream Deck +, MK.2, XL, Mini, Neo, Studio, + XL and Galleon 100 SD - each with curated starting profiles, one per Resolve page. Dial and touch-strip features (timecode, page and mixer dials) need a deck with dials: Stream Deck +, + XL, Studio or Galleon 100 SD. On Resolve Free 21.1+ the timecode dial shows dashes instead of a live readout - see the FAQ below.

If you connect a deck after installing DeckBridge, the Stream Deck app asks your permission before adding each of DeckBridge's page profiles - one prompt per page, the first time you visit it. That's the app's own confirmation, not an error: only you can approve a profile being added to your deck.

Accept them and the prompts stop for good on that deck. A deck that was already attached when you installed DeckBridge gets its profiles up front and never asks.

Update DeckBridge - this was a bug in builds before 0.2.24. On Resolve Free, DeckBridge periodically starts its bridge script for you, and if macOS's Automation permission was declined, older builds kept bringing Resolve forward every few seconds while the useful half of the automation was refused. Current builds check the permission first and never touch focus while it's denied.

To get automatic bridge start-up working, allow it under System Settings → Privacy & Security → Automation → Elgato Stream Deck → System Events - DeckBridge picks the grant up within seconds, no restart needed.

It lives in the settings panel of two actions: Status (a key) and, on decks with dials, Page & Settings. If neither is on your deck, drag either one from the DeckBridge action list onto any empty slot, open its settings, run the cleanup, then remove the tile again - it doesn't have to stay.

Do this while the plugin is still installed. Removing the plugin first leaves the button unreachable, because the Stream Deck app gives a plugin no chance to clean up on its way out. If you've already removed it, the manual's uninstall section lists the steps, including deleting the two DeckBridge buses in Audio MIDI Setup.

Delete the profile in the Stream Deck app's profile editor (right-click it in Edit Profiles → Delete), then switch to that mode in DaVinci Resolve - or switch to another page and back. DeckBridge loads each mode's profile as you visit it, so a deleted profile reinstalls automatically the next time you're on that mode, with the current default layout.

The Stream Deck app asks you to approve the install once - there's no button to press. An installed profile is never overwritten in place, so deleting it first is what lets the fresh copy come in.

No - an update never touches an installed profile, so your customizations always survive. The flip side: when an update ships an improved default layout, your installed profiles keep the old one.

To adopt the new layout for a mode, delete that profile in the Stream Deck app's profile editor, then switch to that mode in Resolve - DeckBridge reloads the fresh default automatically the next time you visit it. See the changelog for what's new in each release.

Hold the corner tiles (about a third of a second): Timecode, bottom-left, goes to the previous page of keys; Status, bottom-right, to the next - the chevrons on their outer edges show the direction, and both wrap around at the ends. A quick tap still does the tile's normal job (Timecode taps to the next Resolve page).

If the hold just flashes an alert, the current profile has only one page - add more with the app's + under the key grid.

In the Status key's settings panel - select the Status key in the Stream Deck app and the inspector shows the full settings home: setup state, MIDI ports, keymap import, the "Your keys" readout, Copy Diagnostics, Reinstall default profiles and the uninstall cleanup. It's the same panel the Page & Settings dial shows on dial decks.

If no Status key is placed, drag one from the DeckBridge action list onto any empty slot.

The strip's live state, straight from Resolve's Fairlight mixer: grey M is muted, green S is soloed, red R is record-armed. They appear in the fader's top-right corner whenever the state is active, and need MIDI connected - without it the deck can't hear the mixer.

Turn on Resolve's printer-light keys. On the Color page, DeckBridge's colour dials and printer-light keys press Resolve's printer-light shortcuts, which are numeric-keypad keys in Resolve's default keymap. Resolve only treats those keys as printer lights while its Printer Lights Enable mode is on - otherwise a keypad digit starts a timecode entry, so turning a dial types numbers into the viewer's timecode field.

Press Ctrl+Alt+` on Windows or ⌘⌥` on macOS (Resolve's default for Printer Lights Enable) once on the Color page, and the dials start nudging the grade. It's a toggle, so press it once rather than every time. Resolve doesn't tell DeckBridge whether the mode is on, which is why DeckBridge can't turn it on for you.

If you'd rather have a button, put a Command key for Printer Lights Enable on your Color profile. If you've changed that shortcut in Resolve, use your own binding instead.

Timecode is a key for button decks: timecode, current page and health dots on one tile, with tap and hold gestures. Timecode Dial is for the touch strip on dial decks: a big dedicated readout whose dial jogs the playhead.

If you used an earlier build: the key was called Status before, and today's Status key was Setup & Status - same actions, clearer names, and your placed keys carry over unchanged. On Resolve Free 21.1+ both actions show dashes instead of a live readout - see the FAQ below.

Your network's security appliance is intercepting HTTPS and re-signing it with its own certificate. deckbridge.io enforces strict HTTPS (HSTS), so browsers refuse the substituted certificate outright rather than offering a proceed-anyway link - that refusal is the browser protecting you, and it's not something we can lift from our side.

Ask IT to either install the appliance's certificate on your machine or exempt deckbridge.io from TLS inspection; from home or a phone the site loads normally.

DeckBridge is sold on the Elgato Marketplace, so purchases, receipts and refunds are handled by Elgato under the Marketplace refund policy - request one from your Marketplace account, not by email to us. Unsure whether DeckBridge fits your setup? Ask us first and we'll tell you straight.

Resolve 21.1 removed the Free edition's scripting API, which is how DeckBridge used to read the exact playhead position. DeckBridge now reads page, timeline and mixer state (with default track names) straight from Resolve's own window instead, so keys and dials work fully - but nothing on Free 21.1+ exposes a readable playhead outside scripting, so the timecode display shows dashes rather than a guess. Page follow covers every Resolve page on Free 21.1+, including the Photo page.

The state dot is amber, not green, for as long as you're on Free 21.1+: amber means DeckBridge is using the accessibility reader, which is exactly what's happening and is expected, not a fault. Green is reserved for the full state feed (Resolve Studio, or Free up to 21.0 via the bridge script). Both gaps go away on Resolve 21.0 or earlier, or Resolve Studio.

Custom track names need Resolve's scripting API, which only Resolve Studio and Free up to 21.0 expose. On Free 21.1+ DeckBridge reads the mixer through the accessibility reader instead, so strips show Resolve's own default labels (Audio 1, Audio 2… Main) rather than your session's names.

Levels, mute, solo and record-arm all stay live regardless - only the label itself is generic. See the editions table for the full breakdown.

It holds your signed-in Cursor session so the meters can refresh every five minutes without ever showing you a browser window. It uses a dedicated profile that belongs to the plugin alone, opens a window only when you explicitly ask (sign-in, or holding a key to open the dashboard), and never touches your normal Chrome profile. Quit it fully and the meters simply can't refresh until you sign in again.

Free plans don't expose the per-model usage cards (Cursor Models, Other Models, Grok Bot) or on-demand spend on the spending dashboard, so there's no percentage to meter. DeckBridge recognises a free plan and shows the meters as FREE with your shared usage-reset countdown (e.g. RESET 30d), and marks on-demand as needing Pro - the connection still reads READY. The four live meters need a paid Cursor plan (Pro or above); upgrade and they fill in on the next refresh.

Because it doesn't - and that's deliberate. Sign-in happens in DeckBridge's dedicated Chrome profile, which has never met cursor.com, so Cursor runs its usual new-device verification even if you're signed in elsewhere. Your normal browser's session is intentionally never used or read - that isolation is the plugin's privacy promise. Complete the verification once; the dedicated session persists from then on and sign-in is rarely needed again.

No. You sign in to cursor.com yourself, in the dedicated Chrome window - DeckBridge never reads, enters or stores credentials. The keys show derived numbers only: percentages, reset countdowns and spend. Raw dashboard content, account identity, cookies and tokens are never cached, logged or sent anywhere. The privacy policy has the complete picture.

No - stale means honest. A routine check failed (network blip, laptop just woke, Cursor slow to respond), so the key keeps the last good value and says so instead of quietly posing as fresh. It usually heals on the next five-minute check; short-press any key to retry immediately.

Open any DeckBridge for Cursor action's settings panel in the Stream Deck app - it names the exact problem and offers the fix. The common one is an expired Cursor sign-in, which is just the two setup steps again: Sign in to Cursor, then Check sign-in. ERROR appears when three checks in a row have failed or something genuinely needs you; one-off blips only ever show STALE.

DeckBridge looks for Google Chrome in /Applications and in your user Applications folder (~/Applications). If Chrome lives anywhere else, move or reinstall it into one of those two locations. Chrome Beta, Canary, Chromium, Brave and Edge don't count - the plugin drives the regular Google Chrome application only.

When the dedicated Chrome process is fully quit, DeckBridge verifies any replacement process actually belongs to it before trusting it with your session. If Chrome restarted itself, DeckBridge reconnects automatically without opening a window. If no verified replacement exists, it fails safe and asks you to sign in again rather than guess - two key presses and you're back.

Your Cursor plan doesn't show that card on the spending dashboard, so there is nothing to meter - the connection itself is healthy and the other keys stay live. The settings panel says the same. If the card exists on your dashboard but the key disagrees, email us with your support code.

Yes. The dedicated Chrome session reads the dashboard in English regardless of your system language - the plugin sets that up itself. Your own browsing and your Cursor account settings are unaffected.

A random identifier generated on your machine, shown in every action's settings panel. Include it when you email us - it lets us correlate a conversation without you sharing anything sensitive. It contains no usage numbers, no account details, and is never uploaded anywhere by the plugin.

Not yet - DeckBridge for Cursor is macOS-only today (macOS 13 or later). Windows is on the roadmap after launch; join the launch list on the product page and you'll hear about it.

DeckBridge's dedicated Cursor Chrome session and its cached meter values - nothing else. Your normal Chrome profile, your Cursor account and your other Stream Deck plugins are untouched. It sits behind an explicit confirmation in every action's settings panel, and if anything about the request fails validation, the plugin refuses and keeps the session rather than delete the wrong thing.

DeckBridge for Cursor is sold on the Elgato Marketplace, so purchases, receipts and refunds are handled by Elgato under the Marketplace refund policy - request one from your Marketplace account, not by email to us. Unsure whether it fits your setup? Ask us first and we'll tell you straight.