# DaVinci Resolve Audio Going to the Wrong Output Device: The Fix

> **Quick answer:** DaVinci Resolve sends audio wherever its own Output Device dropdown points, in Preferences > System > Video and Audio I/O, not wherever your operating system's default device is set. Fix it there first, turn off Automatic Speaker Configuration if it keeps resetting, then check Fairlight's I/O Engine and Track Output bus if only the Fairlight page is affected.

*Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.*
*Updated 2026-07-23 · DaVinci Resolve 21.0.2 (July 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-monitor-audio-wrong-output-device*

You hit play. Sound comes out, just not from where you expected. Maybe it's your monitor's tinny built-in speakers instead of the studio monitors on your desk. Maybe it's dead silent through your headphones while your editing partner across the room can hear everything through the room speakers. Maybe Fairlight sounds fine but the Edit page has gone mute.

None of that means your project is broken. It means DaVinci Resolve is talking to a piece of hardware that isn't the one you're listening through, and that's a setting, not a mystery. Below is every place that setting lives, in the order most likely to fix it fastest.

## Why is DaVinci Resolve sending audio to the wrong device?

Because Resolve doesn't ask your operating system where to send sound. It has its own answer, stored in its own preferences, and that answer can drift out of sync with reality in a dozen small ways: a device you unplugged months ago, a monitor's HDMI audio channel, a Bluetooth headset that's paired but not actually on your head, or an audio interface that got reassigned a different name after a driver update.

Blackmagic Design's own manual is blunt about where this setting lives: the Output Device field **"lets you choose the audio output device from the hardware attached to your system,"** according to the [DaVinci Resolve manual's Video & Audio I/O section](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part124.htm). That single dropdown, and nothing your Mac's menu bar or Windows system tray shows you, is what actually decides where sound goes.

**Your computer's default sound device and DaVinci Resolve's output device are two separate settings that never automatically sync with each other.** You can switch your system output to headphones a hundred times and Resolve will keep playing through whatever it last had selected, because it isn't watching your system setting at all. This single fact explains most of the wrong-device reports that show up on the Blackmagic Forum, year after year, across every version of Resolve.

There's a second layer, too, and it only shows up once you're actually on the Fairlight page. Fairlight has its own routing on top of the system-level device: an I/O Engine choice, a Track Output bus assignment, and a Monitor section with separate Control Room and Studio circuits. Get the system-level device right and the Edit page usually falls in line. Fairlight can still be wrong on top of that, for reasons that have nothing to do with which speakers are plugged in.

## How do you change the audio output device in DaVinci Resolve?

Start here. This single setting fixes the majority of wrong-device reports, and it takes under a minute.

1. Open **Preferences** (the Resolve menu on Mac, the File menu on Windows).
2. Click the **System** tab in the left sidebar.
3. Select **Video and Audio I/O**.
4. Under **Speaker/Headphone Output**, open the **Output Device** dropdown.
5. Pick your intended device by name, your actual speakers, your headphones, or your audio interface.
6. Click **Save**.
7. Quit and restart DaVinci Resolve, since some audio hardware changes don't take effect until relaunch.

That's the whole fix for the most common version of this problem. If sound is still coming from the wrong place afterward, one of two things is happening: the dropdown didn't actually take, which the next section covers, or the problem isn't the system-level device at all, it's Fairlight-specific routing, which the section after that covers.

Here's what each of the surrounding settings on that same panel actually controls, since the names aren't always self-explanatory.

| Setting | What it actually does | When to touch it |
| --- | --- | --- |
| Output Device | Picks the exact hardware Resolve sends audio to | Always the first thing to check |
| Automatic Speaker Configuration | Lets Resolve auto-detect and use your workstation's built-in output | Turn off if it keeps overriding your manual choice |
| I/O Engine | Chooses which audio subsystem Resolve uses: System Audio, Desktop Video, Fairlight Audio Accelerator, or ASIO on Windows | Only matters if you have a Blackmagic capture card, a Fairlight Audio Accelerator, or a dedicated ASIO interface |
| Playback processing buffer size | Sets how much audio Resolve buffers ahead during playback | Affects crackling and latency, not which device is used |
| Record buffer size | Sets how much audio Resolve buffers during recording | Only relevant while recording in Fairlight |

**"Automatic speaker configuration" checked sets DaVinci Resolve to output through your workstation's built-in audio, overriding whatever external device you picked.** That single checkbox is the most common reason a manual device selection appears to get ignored, and it's easy to miss because it sits quietly above the dropdown you just changed.

## Why does DaVinci Resolve keep resetting to the wrong output device on launch?

This one has a name on the Blackmagic Forum, and it isn't rare. A user posted a thread called **["Default audio setup"](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=192247)** describing exactly this: every time they launched Resolve, it picked what looked like a random device instead of remembering their MacBook Pro's built-in speakers, forcing them to reopen Preferences and reselect the right one every single session.

The reason traces back to something you can't fix from inside Resolve's own preferences panel at all. Resolve leans on your operating system's own default audio device at launch, more heavily than most editors expect, and if your OS-level default isn't pinned down, Resolve has nothing stable to lock onto.

**A device you manually select inside Resolve's Preferences can still lose out to a stale operating-system default the next time you launch the app.** The fix that actually holds, according to the same forum thread, is to go a layer deeper than Resolve's own settings:

- **On macOS**: open **Applications > Utilities > Audio MIDI Setup**, right-click your preferred device in the source list, and choose **Use This Device for Sound Output**. This sets it as the actual system default, which is what Resolve checks on launch.
- **On Windows**: open **Sound settings**, and under **Output**, set your preferred device as the default, or right-click it in the classic Sound control panel and choose **Set as Default Device**.

Do that once, confirm the same device is also selected inside Resolve's Preferences, and the reset-on-launch behavior stops for most people. It's a two-layer fix for what looks like a one-layer problem, which is exactly why it trips people up.

If you regularly switch between two legitimate setups, say, studio monitors at your desk and headphones when you travel with a laptop, know that **DaVinci Resolve doesn't remember more than one output configuration at a time.** You'll be resetting the device manually every time you switch environments no matter how well you pin down your OS default, because there's currently no per-location profile for audio output the way some other creative apps offer.

## What if the Output Device dropdown won't change, or only shows the wrong device?

A different, uglier version of this problem shows up on the Blackmagic Forum under the title **["Cannot change Output Device in Video and Audio I/O"](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=163983)**. Some editors report the dropdown only lists an HDMI monitor as an option, with their actual speakers or interface nowhere in the list at all, no matter how many times they reopen Preferences.

Two fixes surface repeatedly in that thread and in related ones:

**Switch the I/O Engine, not just the Output Device.** One user resolved the identical error by changing the **I/O Engine** from **System Audio** to **Desktop Video** in the same Video and Audio I/O panel. If you have any Blackmagic capture hardware installed, even if you're not actively using it for anything, Resolve sometimes defaults to routing through it instead of your system's native audio path, and the fix is telling Resolve explicitly which engine to use rather than leaving it on Automatic.

**Unplug, reselect, restart, replug.** When a specific interface refuses to show up or won't hold a selection, the workaround that's worked for multiple forum members is: unplug the problem device entirely, select a different one that does appear, restart your computer, then plug the original device back in. Resolve re-scans its device list on the next launch and, in most reports, the missing hardware reappears where it should be.

There's also a documented error message worth knowing by name if you've seen it: **["Audio Output - Selected device not found"](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=120517)**. This fires when the specific device Resolve has stored in its preferences no longer exists on your system, whether because it was unplugged, renamed by a driver update, or was a Bluetooth device that's currently out of range. Reselecting a device that's actually connected right now clears it every time. It's not a corruption warning and it doesn't mean anything is wrong with your project.

**A device that Resolve remembers by name can vanish from the list the moment a driver renames it, even if the physical hardware never moved.** This is common after audio interface firmware updates and after macOS or Windows major version upgrades, both of which have been known to rename USB audio devices slightly, just enough that Resolve treats the new name as a different device entirely.

## Why does Fairlight play audio through a different device than the Edit page?

This is where a lot of editors get genuinely stuck, because it feels like a bug: the Edit page sounds fine, but the moment you switch to Fairlight, either the sound is gone or it's coming from somewhere else entirely.

It isn't really one system. Robbie Carman, a working colorist and finishing editor who writes for Mixing Light, put his finger on why this feels so disorienting when Blackmagic overhauled Fairlight years ago: **"The integration of Fairlight and the rejiggering of audio in the general sense in Resolve 14 has left a lot of longtime users frustrated (rightly so) and has interrupted many people's button-downed workflows,"** he wrote in [Mixing Light's guide to multi-channel output in DaVinci Resolve](https://mixinglight.com/color-grading-tutorials/re-revisiting-multi-channel-output-in-davinci-resolve-part-1/). Fairlight brought a full audio-post routing model into an app that used to have much simpler audio handling on the Edit page, and that added flexibility is exactly what creates extra places for a setting to point at the wrong device.

There are three separate links in the chain, and Fairlight-specific problems usually come from one of the last two:

1. **The system-level Output Device**, the same setting covered above, which affects every page equally.
2. **The I/O Engine**, which decides which audio subsystem handles Fairlight's real-time processing: System Audio, Desktop Video, Fairlight Audio Accelerator, or ASIO on Windows. If your Edit page uses one path and Fairlight's engine is set differently, they can genuinely be talking to different hardware.
3. **Track Output bus assignment inside Fairlight itself.** Fairlight uses a bussing system called FlexBus, and each track routes its output to a specific bus before that bus reaches your monitor output. A track that's been assigned to the wrong bus, or a bus that isn't patched to your monitor output, produces silence or misrouted sound that has nothing to do with your Output Device dropdown at all.

**A track routed to the wrong bus in Fairlight produces silence that looks identical to a wrong-device problem but has nothing to do with your hardware settings at all.** If you've confirmed the Output Device and I/O Engine are both correct and Fairlight is still misbehaving, open the **Mixer** (Fairlight menu > Mixer) and check each channel strip's **Bus Output** assignment, and confirm the receiving bus itself is patched through to your monitor output via **Fairlight > Patch Input/Output**, per the [DaVinci Resolve manual's section on setting up tracks, busses, and patching](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part3523.htm).

## What do the I/O Engine options actually mean?

The I/O Engine dropdown, tucked into the same Video and Audio I/O panel, is one of the least explained settings in Resolve, and picking the wrong one is a quiet, common cause of misrouted audio that has nothing to do with the Output Device field sitting right next to it.

| I/O Engine option | What it uses | Pick this if |
| --- | --- | --- |
| System Audio | Your computer's native audio path (Core Audio on Mac, WASAPI or DirectSound on Windows) | You have no Blackmagic capture hardware or dedicated interface |
| Desktop Video | Blackmagic capture card or converter hardware (UltraStudio, DeckLink) | You have Blackmagic I/O hardware installed, even if it's for video only |
| Fairlight Audio Accelerator | A dedicated Fairlight Audio Accelerator card | You've installed Blackmagic's Fairlight-specific accelerator hardware |
| ASIO | Third-party ASIO drivers (Windows only) | You're on Windows with a professional audio interface that ships ASIO drivers |

The manual describes the field plainly: I/O Engine **"lets you choose the audio hardware that DaVinci Resolve uses to process audio,"** per the [Video & Audio I/O section of the DaVinci Resolve manual](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part124.htm). The trap is that most editors never open this dropdown at all, since Resolve picks something on install and rarely calls attention to it, and if it happened to default to Desktop Video on a machine with a capture card that isn't actually plugged into your monitoring chain, your audio can end up trying to leave through hardware you never intended to use for sound at all.

**Installing a Blackmagic capture card for video capture can silently change which audio engine DaVinci Resolve defaults to, even if you never use that card for sound.** If you have any DeckLink, UltraStudio, or similar Blackmagic device connected, and your audio is misbehaving specifically in ways the Output Device fix doesn't resolve, check this dropdown next.

## Why is audio only coming out of your TV or monitor speakers?

This specific version of the problem shows up constantly enough that it has its own recurring thread on the Blackmagic Forum, titled **["Audio is only playing through TV speakers"](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=201095)**. It's almost always one of two things, and they stack in a particular order.

**Your GPU driver enabled HDMI audio.** Modern graphics cards can carry an audio signal over the same HDMI or DisplayPort cable as your video, and when they do, Windows and macOS both treat that monitor as a legitimate audio output device, right alongside your actual speakers. If your GPU driver update or a fresh Windows install turned this on, your system's default output can silently switch to your monitor without you touching a single setting yourself. Nvidia driver updates specifically have been reported to enable HDMI audio and disable other outputs in the same pass, catching people off guard right after a routine GPU driver refresh.

**Resolve's own Output Device dropdown followed that system change, or never matched it in the first place.** Once your monitor is a valid audio device at the OS level, it's one more entry in Resolve's Output Device list, and if Resolve's stored preference happened to point there, or Automatic Speaker Configuration grabbed it as your workstation's default output, that's where your sound goes, regardless of whether you actually want a $2,000 monitor doubling as a speaker.

The fix has two parts, and skipping either one leaves the problem half-solved:

1. In DaVinci Resolve's **Output Device** dropdown, explicitly select your actual speakers or headphones by name, not the monitor.
2. At the operating system level, either set your speakers as the default output device, or go into your GPU control panel (Nvidia Control Panel on Windows, or the equivalent for AMD or Intel) and disable HDMI audio output entirely if you never intend to use your monitor's speakers for anything.

**A monitor with built-in speakers is a legitimate audio output device as far as your operating system and DaVinci Resolve are both concerned, whether or not you ever intended to use it that way.** Nothing about this is a bug. It's your hardware correctly reporting a capability you didn't ask for.

## What's different if you're on Windows?

Windows adds one wrinkle that Mac users never see: DaVinci Resolve lists devices using their WASAPI names, and the same physical device can show up more than once, under confusingly similar labels.

**Devices are listed using their WASAPI names, and if you see multiple entries for the same device, choose the one labeled (Speakers) rather than (Loopback),** according to [Hollyland Store's guide to DaVinci Resolve audio fixes](https://store.hollyland.com/blogs/creator-hub/davinci-resolve-can-t-hear-audio). A Loopback entry captures whatever's already playing on that device, useful for recording system audio, not for hearing it. Pick the wrong one and Resolve appears to have audio selected correctly while producing no sound at all, because a loopback endpoint isn't meant to output anything on its own.

A few other Windows-specific patterns worth knowing:

- **RealTek onboard audio and USB headphones.** A workaround reported for Windows 10 machines with RealTek audio chipsets is to fully quit Resolve, plug in your headphones first, and only then relaunch the app. Plugging headphones in while Resolve is already running doesn't always trigger a re-scan.
- **Exclusive mode conflicts.** If another application, a DAW, a streaming tool, or even a browser tab, has exclusive control of your chosen output device, Windows can block Resolve from using it simultaneously. Check your device's Properties in Windows Sound settings and, under the Advanced tab, uncheck "Allow applications to take exclusive control of this device" if you regularly run Resolve alongside other audio software.
- **ASIO on Windows only.** If you use a dedicated audio interface with its own ASIO driver, RME, Focusrite, and similar brands all ship one, set the I/O Engine to ASIO rather than System Audio. ASIO bypasses the Windows mixer entirely and talks to your hardware directly, which sidesteps a whole category of device-selection confusion, though it also means you configure channels and levels in the manufacturer's own control panel, not inside Resolve.

## What's different if you're on macOS?

Mac users don't deal with WASAPI naming or ASIO, but they run into a different set of quirks tied to Core Audio and how macOS manages device defaults.

- **Audio MIDI Setup is the real source of truth.** As covered above, setting a device as your default there, not just inside Resolve's own dropdown, is what stops Resolve from resetting to the wrong device on launch. It's in Applications > Utilities.
- **Microphone permission affects more than recording.** If Resolve hasn't been granted microphone access under System Settings > Privacy & Security > Microphone, some users report broader audio device detection issues, not just missing input. Granting the permission and restarting Resolve is worth trying even if you're only chasing an output problem.
- **Multi-Output and Aggregate Devices confuse Resolve.** If you've built a Multi-Output Device in Audio MIDI Setup, common among editors who also monitor through a separate app or use software like Loopback or BlackHole to route audio between applications, Resolve can end up pointing at that virtual aggregate device instead of your physical speakers. If your setup includes any virtual audio device, check whether it's the one selected in Resolve's Output Device dropdown before assuming your physical hardware is at fault.
- **Sleep and display changes can reset the default.** Waking a MacBook from sleep, or connecting and disconnecting an external display with its own speakers, can shift macOS's system default output without any action on your part, and Resolve's launch-time detection inherits whatever that default happens to be at the moment.

DaVinci Resolve's own platform note is worth keeping in mind here too: on Mac, Resolve **"supports audio monitoring and audio input using the audio of a supported Blackmagic Design I/O device, your macOS workstation's on-board audio, or any Core Audio-compatible third party audio interface."** Any Core Audio device is fair game for the Output Device list, which is exactly why a virtual routing tool you installed for an entirely different purpose can quietly end up in that dropdown.

## What if you're using a Blackmagic capture card, UltraStudio, or DeckLink?

If you edit with a Blackmagic Design I/O device, an UltraStudio for external monitoring, a DeckLink card for capture, or a similar box, you're running an extra layer of audio hardware on top of everything above, and it changes where you need to look first.

The I/O Engine dropdown becomes the deciding factor. Set to **Desktop Video**, Resolve routes audio through your Blackmagic device's own outputs, meaning your speakers need to be physically connected to that hardware's audio out, not to your computer's headphone jack or a USB DAC. If your speakers are plugged into your computer directly but Resolve's I/O Engine is set to Desktop Video, you'll get silence through your speakers even though everything else looks correctly configured, because Resolve is sending sound to a physical output your speakers aren't connected to.

**A Blackmagic capture device changes not just what video path Resolve uses, but which physical jack your audio needs to be plugged into.** This trips up editors who've just added external monitoring hardware for the first time far more than it trips up anyone else, since the mental model shifts from "my computer's headphone jack" to "my capture device's audio output" without any obvious prompt from Resolve to make that switch.

If you only use your Blackmagic device for video monitoring and want audio to stay on your computer's own hardware, set the I/O Engine back to **System Audio** explicitly. Leaving it on Automatic, when Automatic is available, is what tends to route you somewhere unexpected the moment a capture device is detected.

## Can Bluetooth headphones cause this specific problem?

Yes, and it's one of the sneakier versions because it can look intermittent instead of consistently wrong.

Bluetooth devices only exist as a valid audio output while they're actively connected. If your headphones were the selected device in Resolve, then you took them off, they auto-disconnected after a timeout, or your computer connected to a different Bluetooth device in the meantime, Resolve's Output Device dropdown can still be pointed at headphones that are no longer reachable. The symptom is total silence, not a wrong-but-audible device, which throws people off since they expect to at least hear something coming from somewhere.

There's a second issue even when Bluetooth is working correctly: latency. Bluetooth audio introduces noticeably more delay than a wired connection, often 100 to 200 milliseconds depending on the codec your headphones and computer negotiate. **Bluetooth headphones add enough audio latency that they're a poor choice for any task where you're syncing sound to picture by ear, even when they're routed correctly.** If you're fine-tuning a cut against dialogue timing or checking lip sync, wired headphones or speakers will serve you better regardless of whether the device-selection problem is present.

If Bluetooth headphones are your regular setup, reconnect them before launching Resolve rather than after, confirm they're selected in both your OS-level sound settings and Resolve's Output Device dropdown, and expect to reselect them any time your computer reconnects to a different paired device in between editing sessions.

## Is this actually a wrong-device problem, or something else?

Wrong-device routing and a handful of other Fairlight audio problems produce symptoms that overlap just enough to send people down the wrong troubleshooting path. Here's how to tell them apart before you spend twenty minutes on the wrong fix.

| Symptom | Likely cause | Where to look |
| --- | --- | --- |
| Total silence, every page | Output Device pointed at a disconnected or wrong device | Preferences > System > Video and Audio I/O |
| Sound on Edit page, silent on Fairlight | I/O Engine or Track Output bus mismatch | Fairlight menu > Mixer, and Patch Input/Output |
| Audio comes from monitor or TV speakers | HDMI audio enabled at the GPU driver level | GPU control panel and OS sound settings, then Resolve's Output Device |
| Crackling, popping, or stuttering (device is otherwise correct) | Sample rate mismatch, small buffer size, or GPU/CPU overload | Project Settings > Fairlight, and Preferences > System > Video and Audio I/O buffer size |
| Resets to the wrong device every launch | Stale OS-level default, not just a Resolve setting | macOS Audio MIDI Setup or Windows Sound settings |
| Works, then goes silent mid-session | Bluetooth disconnect, or another app took exclusive control | Reconnect device, check Windows exclusive-mode setting |
| "Selected device not found" error | Stored device name no longer matches connected hardware | Reselect the currently connected device manually |

**Crackling or stuttering audio through the correct device is a completely different problem from silence through the wrong device, and they need different fixes.** If your speakers are unmistakably the ones producing sound but that sound is breaking up, you're not looking at a routing issue at all, you're looking at a sample rate mismatch or a buffer that's set too small, which our [guide to DaVinci Resolve audio crackling and popping](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-audio-crackling-and-popping-during-playback) covers in full, including the exact buffer sizes to try and when to blame your GPU instead of your audio settings.

If you're setting up a recording session rather than troubleshooting playback, the routing fundamentals here still apply, patching, arming, and monitoring are all covered from the ground up in our guide to [recording a podcast in DaVinci Resolve using Fairlight](https://tryuncle.com/learn/davinci-resolve/how-to-record-a-podcast-in-davinci-resolve-fairlight). And if audio and video are landing at the wrong device correctly but out of sync with each other, that's a different fix entirely, one our guide to [syncing audio in DaVinci Resolve](https://tryuncle.com/learn/davinci-resolve/sync-audio) walks through method by method.

## Has Blackmagic fixed any of this in a recent update?

Some of it, at least on the playback-quality side. DaVinci Resolve 20.2.2, released in October 2025, **resolves jittery playback in Fairlight**, according to release coverage from [AlternativeTo](https://alternativeto.net/news/2025/10/davinci-resolve-20-2-2-improves-color-management-and-audio-playback). That's a playback smoothness fix, not a device-routing fix, and it's worth knowing the difference: a jittery or stuttering Fairlight timeline on an otherwise correctly selected device is a separate class of problem from audio going to the wrong device entirely, and recent Resolve releases have been actively chipping away at the former.

The device-selection quirks covered throughout this guide, the launch-time reset, the Output Device dropdown losing track of renamed hardware, the I/O Engine defaulting somewhere unexpected when capture hardware is present, remain largely unchanged as of DaVinci Resolve 21.0.2. If you're on an older version and haven't updated in a while, it's still worth doing, since Blackmagic ships frequent point releases and audio playback has clearly been an active area of work. Just don't expect an update alone to fix a device that's misconfigured; that part is still on you, every time.

**No version of DaVinci Resolve automatically detects which output device you actually want to use. It only remembers, imperfectly, the one you told it last.**

## What if you're still stuck after trying all of this?

Every fix above lives in a menu you have to find on your own, and DaVinci Resolve's preferences aren't laid out in a way that makes the relationship between Output Device, I/O Engine, and Fairlight's own bus routing obvious at a glance. That's the real reason this specific problem generates so many forum threads over so many years: not that the fix is hard, but that knowing which of three or four separate settings is the culprit takes real trial and error.

TryUncle is the on-screen assistant for DaVinci Resolve on macOS — ask in plain words and Uncle points at the exact control on your screen. If you've worked through this guide and you're still not sure whether your problem is the Output Device dropdown, the I/O Engine, or a Fairlight bus assignment, you can ask Uncle directly, by voice or by typing, and it draws a box around the exact setting on your actual screen rather than making you match a screenshot from an article to your own version of the interface. It doesn't change any settings for you. It's a paid macOS app, currently in founder pricing, and it's worth comparing honestly against the alternatives: tools like Sottocut, PremiereCopilot, heyeddie.ai, and cutagent.ai focus on automating edits or answering chat questions about your footage, while Uncle's job is narrower and more literal, showing you where a control lives inside Resolve itself, live, while you're stuck on it.

If you'd rather keep troubleshooting on your own, that's a completely reasonable choice too. Everything in this guide works without any additional software, and the free version of DaVinci Resolve has every setting you need to fix this.

## The verdict

Start with Preferences > System > Video and Audio I/O every time. Set the Output Device manually, turn off Automatic Speaker Configuration if it's fighting you, and restart Resolve. If that doesn't hold, pin your preferred device as the actual operating system default, not just Resolve's internal preference, since Resolve leans on that default more than most editors realize. If the Edit page is fine but Fairlight isn't, stop looking at the Output Device entirely and check the I/O Engine and each track's Bus Output instead.

Wrong-device audio in DaVinci Resolve is never random, even when it looks that way after the third time it resets. It's a small, fixed set of settings, spread across your operating system and two different layers of Resolve's own preferences, and once you know where all three live, this stops being a mystery and starts being a thirty-second check.

## FAQ

### Why is DaVinci Resolve playing audio through the wrong device?

Because DaVinci Resolve routes sound through its own Output Device setting in Preferences > System > Video and Audio I/O, and that setting is completely separate from your operating system's default sound device. Resolve can keep pointing at a monitor, a disconnected interface, or a Bluetooth device long after you've changed your system's default elsewhere, since the two never sync automatically.

### How do I change the audio output device in DaVinci Resolve?

Open Preferences (Resolve menu on Mac, File menu on Windows), click the System tab, select Video and Audio I/O, and use the Output Device dropdown under Speaker/Headphone Output to pick your speakers, headphones, or interface. Click Save and restart DaVinci Resolve for the change to take full effect.

### Why does DaVinci Resolve keep resetting to the wrong output device every time I open it?

This is a documented behavior reported on the Blackmagic Forum, where Resolve appears to pick a somewhat random device on launch instead of remembering your last choice, especially on machines with more than one audio output. Setting your preferred device as the actual system default in macOS Audio MIDI Setup or Windows Sound settings, not just inside Resolve's own dropdown, is what stops the reset for most people.

### Why is my audio only coming out of my TV or monitor speakers?

Almost always because your GPU driver enabled HDMI audio output and either your operating system or Resolve's own Output Device dropdown picked that HDMI channel instead of your actual speakers or headphones. Check Resolve's Output Device dropdown first, then your system sound settings, and disable HDMI audio at the driver level if you never intend to use it.

### Why does Fairlight play audio through a different device than the Edit page?

The Edit page and the Fairlight page can each be affected by a different link in the audio chain: the system-level Output Device, the I/O Engine choice (System Audio, Desktop Video, ASIO, or Fairlight Audio Accelerator), and Fairlight's own Track Output bus routing. A mismatch in any one of those three, not a bug specific to one page, is what produces sound in one page and silence or the wrong device in the other.

### Do I need DaVinci Resolve Studio to fix output device routing?

No. Every setting that controls where audio plays, the Output Device dropdown, Automatic Speaker Configuration, the I/O Engine choice, and Track Output bus assignment, is available in the free version. Studio adds Fairlight FX plugins and immersive audio mixing tools, not the underlying playback routing.

### Is there an app that helps you while you're actually using DaVinci Resolve to fix settings like this?

TryUncle watches your DaVinci Resolve screen and points at the exact control, including the Output Device dropdown in Preferences or the Track Output menu in Fairlight, if you're not sure where to look. Tools like Sottocut, PremiereCopilot, and cutagent.ai automate edits or answer chat questions about your project; Uncle doesn't touch your timeline, it just shows you where the fix lives on your own screen, live.

### Can Bluetooth headphones cause DaVinci Resolve to play through the wrong device?

Yes. If your Bluetooth headphones were ever the selected device and you take them off or they disconnect, Resolve's Output Device dropdown can still point at them, sending audio nowhere you can hear it. Bluetooth audio also runs at higher latency than a wired connection, so even when it is working, it's a poor choice for anything you're trying to sync by ear.

## Sources

- [Blackmagic Forum: Default audio setup](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=192247)
- [Blackmagic Forum: Resolve ignores my system audio device](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=130124)
- [Blackmagic Forum: Cannot change Output Device in Video and Audio I/O](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=163983)
- [Blackmagic Forum: Audio is only playing through TV speakers](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=201095)
- [Blackmagic Forum: error message, Audio Output - Selected device not found](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=120517)
- [DaVinci Resolve Manual: Video & Audio I/O (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part124.htm)
- [DaVinci Resolve Manual: Monitor Section (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part3868.htm)
- [DaVinci Resolve Manual: The Fairlight Page (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part58.htm)
- [DaVinci Resolve Manual: Setting Up Tracks, Busses, and Patching (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part3523.htm)
- [Mixing Light: Re-Revisiting Multi-Channel Output In DaVinci Resolve, Part 1, by Robbie Carman](https://mixinglight.com/color-grading-tutorials/re-revisiting-multi-channel-output-in-davinci-resolve-part-1/)
- [DaVinci Resolve Can't Hear Audio? Here Are the Fixes That Actually Work (Hollyland Store)](https://store.hollyland.com/blogs/creator-hub/davinci-resolve-can-t-hear-audio)
- [DaVinci Resolve 20.2.2 improves color management and audio playback (AlternativeTo)](https://alternativeto.net/news/2025/10/davinci-resolve-20-2-2-improves-color-management-and-audio-playback)
- [DaVinci Resolve - Fairlight (Blackmagic Design product page)](https://www.blackmagicdesign.com/products/davinciresolve/fairlight)