Why Audio Goes Missing in DaVinci Resolve
Silent playback in DaVinci Resolve almost never means your files have vanished. It means one link in a fairly long chain has quietly broken. That chain runs from the media file on disk, through a decoder, onto a timeline track, through the mixer, out to an output device, and finally into your speakers or headphones. Any single broken link produces the same symptom: you see waveforms or you see nothing, you hit play, and the room stays quiet.
Understanding the chain matters because it tells you where to look. Editors who panic and start re-installing the application usually waste an hour fixing a problem that a single drop-down menu would have solved. Editors who methodically walk the chain from content to hardware typically locate the fault in under five minutes.
Here are the most common causes, roughly in order of how often they appear:
- A track or clip is muted, or a solo state is stuck on a different track.
- The clip attributes have audio channels mapped incorrectly, so a stereo file plays only the empty channel.
- The track output is routed to a bus that does not exist or is not connected to the main output.
- The operating system switched its default output device — often to a Bluetooth headset that has since disconnected.
- The media file uses an audio codec or channel layout the current decoder handles poorly, especially in containers like MKV or in variable frame rate screen recordings.
- The application is locked to a sample rate that conflicts with the interface the operating system is using.
- A cache, database, or preferences file has become corrupted.
- A driver update for an audio interface or GPU introduced a conflict.
Notice that only one or two of those are genuine "broken file" problems. The overwhelming majority are configuration, routing, or environment issues. That is why the fastest path to a fix is always diagnosis before repair.
It also helps to know when the problem started. Did audio work yesterday and stop after a driver update? Did it disappear only in one project? Only in one timeline? Only when a particular clip is under the playhead? Only after you connected a monitor through HDMI? Each answer narrows the search space dramatically.
The Two-Minute Triage Checklist
Before touching any advanced setting, run a short triage pass. The goal is not to fix anything yet — it is to classify the failure as content-level, timeline-level, application-level, or system-level.
Check the obvious mutes first
Look at the Mixer and the track headers on the Edit page. Confirm no track is muted, no solo button is engaged on an unrelated track, and the main output fader has not been pulled to negative infinity. In Fairlight, check that monitoring is enabled and that the monitor path is assigned. It sounds trivial, but a stuck solo on a music track is one of the most frequently reported causes of "missing" dialogue.
Confirm the file actually has audio
Drag the clip into a fresh timeline and watch the waveform area. If Resolve never drew a waveform, the decoder may not be reading an audio stream at all. Open the clip's attributes and inspect the channel count. If it reports zero channels, the problem is upstream of the timeline and no routing change will help.
If you are unsure whether the file has audio, play it in a plain media player outside the editor. If the player produces sound, the file is fine and the issue is inside your project or your environment. If the player is also silent, your file or your system output is the culprit.
Test the system audio path
Play any music or video in a browser. If you hear nothing there either, the problem has nothing to do with your editing software. Close the editor, fix your OS output device, then return. This single test saves more time than any other step in this article.
Isolate the scope
Ask four questions in sequence: Does it affect one clip or every clip? One track or all tracks? One timeline or the whole project? One project or every project? The pattern you get determines which section below applies to you.
Diagnosing the Timeline: Clips, Tracks, and Link States
Once you know the failure is inside the application, the timeline is the first place to look. Resolve layers several independent audio behaviors here, and they can conflict in confusing ways.
Clip attributes and channel mapping
Right-click a clip and open Clip Attributes. Pay attention to the Audio tab. A stereo source assigned as two mono channels, or a multi-channel source mapped to a single channel, can result in silence on the channels actually being monitored. If a clip has embedded multi-channel audio — common with camera originals that carry four or eight tracks — the default mapping may point the timeline at empty channels.
A useful test is to switch the mapping to a different channel pair and play again. If audio suddenly appears, you found the issue. Rebuild the mapping deliberately rather than leaving it on a lucky accident.
Track-level mute, solo, and output routing
Each track has its own output assignment. If a track is routed to a submix that is itself muted, or to a bus you deleted during a cleanup, the track appears active while producing nothing. Open the track's output menu and confirm it points to the main output or to a submix that is actually connected to the main output.
Also check the track format. A mono track fed by a stereo clip may only carry one side, which can sound like partial audio loss rather than total silence — but when the empty side is the one you are monitoring, the result is indistinguishable from a dead track.
Linked selection and the detached audio trap
When linked selection is enabled and you move a video clip, its audio moves with it. If the link was broken at some point — often after a paste operation or a timeline restructure — audio can end up parked somewhere else on the timeline, far from the picture. Scrub through the whole timeline with the waveform view enabled. It is not unusual to find a chunk of dialogue sitting alone thirty seconds later, completely out of sync.
If you find detached audio, re-link it deliberately. Select the video and audio, then use the link command, or nudge the audio back into place and re-establish the link so the problem does not recur.
Media Pool and File-Level Problems
When a clip shows no waveform at all, the issue is usually the file itself or the decoder's handling of it. This is the category where transcoding becomes relevant.
Codec and container issues
Some containers and codec combinations are handled inconsistently. Matroska files, certain fragmented MP4 recordings, and screen captures that use compressed audio inside a video container are frequent offenders. The video decodes perfectly while the audio stream is either ignored or decoded into silence.
A quick diagnostic is to export the audio stream out of the file and import it separately. If the extracted audio plays fine as a standalone file, you have confirmed the container is the problem — not the recording itself.
Sample rate and bit depth mismatches
If your project is set to 48 kHz and the source was recorded at 44.1 kHz in an unusual layout, some workflows will attempt a real-time conversion that fails silently. Setting the project sample rate to match the dominant source material, then re-importing, resolves this surprisingly often.
Variable frame rate and long-recording artifacts
Screen recorders and phone cameras frequently write variable frame rate files. These are notorious for causing both sync drift and audio dropouts after a certain duration. The fix is almost always a constant frame rate transcode before editing. Treat variable frame rate as a known hazard and convert on import rather than fighting it on the timeline.
Corrupted or partially written files
If a recording was interrupted — a crashed capture, a battery that died mid-write — the container may be intact while the audio stream is truncated. No editor setting will recover that. Re-record, or restore from a backup, and consider using a capture tool that writes recoverable containers.
Playback, Output Devices, and the System Audio Chain
The application does not talk to your speakers directly. It hands audio to the operating system, which hands it to a driver, which hands it to hardware. Several of the most confusing "missing audio" reports live entirely in this layer.
Preferences and monitoring settings
Open the audio preferences and confirm the output device selected is the one you are actually listening on. It is common to have an HDMI monitor selected as the output while the editor is wearing headphones plugged into a different interface. The application is playing correctly — into a screen that has no speakers, or into a device nobody is monitoring.
Also verify that the monitor path is enabled rather than bypassed, and that any "mute during playback" or scrubbing-related monitoring option is not suppressing output in the mode you are working in.
Bluetooth, USB interfaces, and device switching
Bluetooth headphones are convenient and hostile to editing. When they disconnect, some operating systems silently move playback to the next available device instead of pausing. The editor keeps playing; you keep hearing nothing. If you edit on Bluetooth, get into the habit of checking the output device any time audio vanishes.
USB interfaces introduce a related failure mode: the interface is enumerated by the OS but the application still holds a stale reference to a previous device. Unplugging and reconnecting the interface while the editor is open can either fix it or make it worse. Prefer closing the application, reconnecting the device, then reopening.
Sample rate conflicts between application and system
If your interface is locked to 44.1 kHz by a control panel application while your project runs at 48 kHz, some drivers will simply refuse to open the stream. The symptoms range from total silence to crackling to audio that works only while the timeline is paused. Set one rate everywhere — interface, OS, and project — and keep it consistent across the session.
Restart, Cache, and Project-Level Resets
The classic first-line fix is a restart, but a careless restart accomplishes nothing. Do it properly.
The clean restart sequence
Save your project, close the application completely, and confirm the process has ended in your system's task manager. Then disconnect and reconnect the audio interface. Restart the machine. Reopen the application and load the project from the project manager rather than from a recently opened shortcut if possible. This clears stale device handles that survive a simple window close.
Clearing cache and rebuilding the database
Cache files can become inconsistent after crashes or after moving media between drives. Clearing the cache for the affected project and letting it regenerate often restores waveform drawing and playback. If your project database lives in a location that has been moved or synced by a cloud service, that is a strong candidate for the underlying fault — cloud sync tools and media databases do not mix well.
If one project is broken and others are fine, create a new project, import the media, and rebuild a short timeline. If audio works there, the original project file is suspect. You can then migrate timelines selectively to isolate the damaged element.
Creating a diagnostic project
Keep a tiny test project with one stereo music file and one stereo dialogue file. When audio misbehaves, open the test project first. If audio works there, the problem is project-specific. If it fails there too, the problem is environmental — device, driver, or application configuration. This one habit eliminates half the guesswork in audio troubleshooting.
Transcoding and Rewrapping: When Conversion Beats Repair
Transcoding gets a bad reputation because it is slow and creates large files. But it is also the single most reliable fix for decoder-level silence, and the time it costs is usually less than the time spent troubleshooting a hostile format.
Rewrap versus transcode
Rewrapping changes the container without re-encoding the streams. It is fast, lossless, and worth trying first when only the container is problematic. Transcoding re-encodes the audio, which is what you need when the stream itself decodes into silence or contains unusable channel layouts.
Decision criteria:
- The audio plays fine in another player → try a rewrap first.
- The audio does not play anywhere → transcode the audio stream to a standard 48 kHz PCM or AAC file.
- The audio plays but drifts out of sync over time → transcode both video and audio to constant frame rate and a consistent sample rate.
- The audio plays with crackles → check sample rate alignment before transcoding anything.
Choosing a mezzanine format
For editing, choose a predictable target: constant frame rate video with uncompressed or lightly compressed audio at 48 kHz, stereo or a defined multi-channel layout. Consistency matters more than compression efficiency. A project where every file shares the same frame rate, sample rate, and channel layout will produce almost no audio surprises.
Building a batch workflow
Create a watch folder. Every time new media arrives — from a camera, a phone, a screen recorder, or a client — run it through the same conversion recipe before importing. This is not glamorous, but it converts an unpredictable troubleshooting problem into a boring, predictable pipeline step. Boring pipelines ship projects.
Rebuilding Audio: Nesting, Compound Clips, and Fusion
Sometimes the audio exists but the timeline will not play it. In those cases you can rebuild the audio path rather than repairing it.
Nesting to force re-detection
Select a problematic sequence of clips and create a compound clip or nest. This forces the application to rebuild the internal audio graph for those items. If the nested clip plays audio correctly while the original does not, you have worked around a corrupted timeline structure. Keep the nest as a permanent solution or use it as a bridge while you rebuild the sequence.
Extracting audio separately
Extract the audio from the source file into its own file, then place it on its own track aligned to the picture. This decouples the audio from whatever is wrong with the container or the clip's embedded stream. It costs a step, but it gives you a clean, independent audio layer that behaves predictably for the rest of the edit.
Using Fairlight as a diagnostic layer
Fairlight exposes routing that the Edit page hides. Open the mixer and trace the signal path from clip to track to bus to main output. If a signal is present at the clip level and absent at the main output, you have localized the fault to routing. Fairlight also shows meter activity, which is a fast way to distinguish "no audio is being generated" from "audio is being generated but not monitored."
When to rebuild instead of repair
If a timeline has accumulated broken links, orphaned audio, and inconsistent routing, repairing it can take longer than rebuilding it. Export what works, start a clean timeline, and repopulate it from the media pool. Editors often resist this because it feels like losing progress, but a clean timeline pays for itself in the first hour of mixing.
Hardware, Drivers, and OS Conflicts
Environmental faults are the hardest to diagnose because everything inside the application looks correct.
Audio interface and driver versions
Check that your interface driver matches your operating system version. A driver that was fine before a system update can become the source of silence afterward. Roll back if the problem began immediately after an update, and check the manufacturer's release notes for known conflicts with editing software.
Exclusive mode and sample rate locking
Many operating systems allow an application to take exclusive control of an audio device. If two applications fight over the same device, one of them loses. Closing browsers, communication apps, and music players before editing eliminates a whole class of intermittent audio failures — especially the kind that appear only when a notification sound plays.
GPU driver side effects
GPU drivers sometimes install audio components for HDMI output. These can hijack the default device or introduce conflicts with dedicated audio hardware. If audio problems began after a graphics driver update, that is not a coincidence. Reinstall the audio component or explicitly select your interface as the default device and disable the HDMI audio device when it is not needed.
Power management and USB ports
Aggressive power saving can suspend USB audio devices mid-session. If audio drops out after periods of inactivity and returns when you interact with the machine, look at power management settings for USB devices. Prefer powered hubs and direct motherboard ports over unpowered front-panel extensions.
Prevention Checklist and FAQ
Most audio emergencies are preventable with a small amount of discipline at the start of a project.
Prevention rules worth adopting
- Standardize on one sample rate and one frame rate across the entire project before importing anything.
- Convert variable frame rate and unusual container formats on ingest, not after problems appear.
- Back up audio separately from video, even if the source file carries both.
- Keep a test project for quick environmental checks.
- Record room tone and scratch audio for anything critical.
- Document your routing once and reuse that project template.
- Avoid switching output devices mid-session; if you must, verify monitoring afterward.
Frequently asked questions
Why does audio work in the source monitor but not the timeline? That pattern usually points to track routing or a muted track rather than the media. Check the track output assignment and any solo state before touching the file.
Why is only one channel silent? Look at channel mapping in Clip Attributes and the track format. A stereo clip on a mono track, or a mismatched channel assignment, produces exactly this symptom.
The waveform is missing entirely. Is the file damaged? Not necessarily. The decoder may be failing to read the stream. Test the file in an external player and try a rewrap or transcode before assuming damage.
Audio plays but drifts out of sync over time. This is the classic signature of variable frame rate media. Transcode to a constant frame rate and re-link the audio.
Everything was fine until I updated a driver. Roll the driver back or reinstall it. Keep a note of the version that worked so you can return to it quickly.
Should I just reinstall the editing software? Only after you have ruled out device selection, routing, sample rate, and cache corruption. Reinstallation is a legitimate step, but it is rarely the first one that should be taken.
How do I know if the problem is my project or my machine? Open your test project. Working audio there means the project is at fault; silence there means the environment is.
Missing audio is frustrating precisely because the symptom is identical no matter which link in the chain failed. Treat it as a diagnostic puzzle rather than a disaster: verify the system output, verify the file, verify the timeline routing, then work outward toward drivers and hardware. With a consistent ingest pipeline and a small test project on standby, most silent-timeline emergencies turn into five-minute fixes instead of lost afternoons.
