When DaVinci Resolve won’t import an MP3, AAC or M4A file, the first question is where it broke. Did the file fail before it reached the Media Pool, or did it import fine and only go silent later? An item that never shows up in the bin points to file access, protection, codec support or a damaged file. A clip that appears normally and plays no sound is a different problem, and the DaVinci Resolve no-audio signal path covers it.
For a real import failure, work in this order: make the file fully local, play it outside Resolve, identify the actual audio stream with MediaInfo, check protection and platform support, and only then convert one duplicate to uncompressed PCM WAV if the compressed source keeps misbehaving. Leave the extension alone, and don’t batch-convert a folder until one test file has shown you the cause. The Resolve troubleshooting hub covers the wider set of problems.
| Symptom | First check | Likely branch |
|---|---|---|
| The file is missing from the import browser | Confirm it is downloaded locally and the path is accessible | Cloud placeholder, permission, disconnected storage, or file filter |
| Resolve rejects the file or nothing happens | Play the original elsewhere and inspect it with MediaInfo | Unsupported stream, protected media, incomplete download, or malformed file |
| The clip appears but duration, waveform, or channels are wrong | Compare MediaInfo duration and channel count with Resolve | Damaged header, unusual encoding, or partial decode |
| The audio imports on Windows or macOS but not Linux | Identify the codec, then verify support for that Resolve build | Platform-specific AAC or compressed-audio limitation |
| The file imports and meters move but speakers are silent | Follow track, bus, monitor, and output-device routing | Playback and monitoring, not import |
Make Sure the Audio File Is Actually Local
A filename in Finder or File Explorer doesn’t prove the whole media file is on your computer. iCloud Drive and OneDrive can show a placeholder while the actual bytes stay in cloud storage. Resolve may refuse that item, get an incomplete path or lose access when the sync client changes state.
On a Mac, inspect the iCloud status icon. Apple’s iCloud Drive status guide distinguishes downloaded items from files that remain in iCloud. Download the problem file, wait for the transfer to finish, then copy it to a short local folder such as Movies/Resolve Import Test. Keep the original name for now.
On Windows, right-click a OneDrive item and choose Always keep on this device when the test must remain local. Microsoft’s Files On-Demand documentation explains the cloud-only and locally available states. Wait for the solid availability indicator before importing.
Play the local copy in another trusted player and scrub near the start and the end. A clean playback there doesn’t prove Resolve has the same decoder. A failure outside Resolve, though, is strong evidence that the source is incomplete or damaged. If the local copy works and the cloud copy doesn’t, keep the working media in managed project storage and stop editing straight from an on-demand folder.
If Resolve knew the clip before and now reports a missing path, go to the Media Offline and relinking guide. This article is about a new audio file that Resolve won’t accept in the first place.
The Extension Does Not Identify the Audio Stream
MP3 usually names both the familiar extension and the compressed audio format. M4A is only a container extension, and it can hold AAC, Apple Lossless or media with a protection history. An AAC stream can also sit inside MP4 or MOV. Renaming `.m4a` to `.mp3` leaves the audio exactly as it was, and renaming anything to `.wav` won’t transcode it or create PCM.
The difference matters because Resolve reads the stream and the container structure, and the filename promises nothing. Two `.m4a` files from different places can behave differently. One may be plain AAC exported by a recorder. Another may be an Apple Lossless purchase, a third may be tied to an Apple Music subscription, and a fourth may be a cloud download that never finished.
Open the file in MediaInfo from MediaArea and switch to Text or Tree view. Read the audio section itself; the general container name tells you far less. Note these fields:
- Format and codec ID: identifies MP3, AAC, ALAC, PCM, or another stream.
- Duration: exposes a zero-length, truncated, or implausibly short file.
- Sampling rate: commonly 44.1 kHz for music and 48 kHz for video production.
- Channels and channel layout: confirms mono, stereo, or a multichannel arrangement.
- Bitrate mode and bitrate: useful when comparing a failing file with a working file from the same source.
- File size and stream size: helps spot a placeholder or incomplete transfer.
Compare the failing report with a small file that imports fine on the same computer. If both streams match and only one fails, suspect file integrity, tags, an unfinished transfer or a parser edge case. If the codecs differ, check the actual codec against your operating system, Resolve edition, and build on the Blackmagic Design Support page.
Variable bitrate alone tells you nothing. A normal VBR MP3 can import fine, while one malformed file with a broken header or a bad duration table fails. The evidence worth having is that this particular file reports odd values, breaks near the end or behaves differently from another file made by the same tool.
Check Apple Music Protection Before Converting M4A
An Apple Music download isn’t automatically a plain, portable AAC file. Subscription content can be protected and tied to playback in Apple’s authorized apps and your account. A purchased or independently encoded unprotected M4A is a separate case, even when the two files share an extension.
Apple’s support material on protected and unprotected music describes the difference between older protected purchases, iTunes Plus purchases, and other library items. Check the song’s source and file information in the Music app. If the item is subscription-protected, obtain a licensed production source from the rights holder, your own original recording, or a legitimate unprotected purchase or download.
Never use a converter to get around DRM. A player being able to play the song gives Resolve no right to a reusable decoded source and gives you no permission to put it in a video. Importing into Resolve and licensing the content are two separate questions, and you need a valid answer to both.
If the M4A is unprotected and MediaInfo shows AAC or ALAC, move on to platform support and file-integrity checks. If it’s protected, a new container or extension won’t make it ordinary production audio.
Linux AAC Needs an Early Platform Check
A file that imports on macOS or Windows can fail on Linux, because Resolve’s media support differs by platform. AAC is the long-running Linux exception. Blackmagic forum guidance in the Linux AAC discussion reports that the Linux builds discussed there decoded AAC in neither Free nor Studio, and reports about the current 21 builds still describe the same gap.
Still, read that as evidence about specific versions, and keep an eye on future releases. Check your exact Resolve version and build, the current support notes from Blackmagic and the MediaInfo report for the source. When the decoder is missing, buying Studio, moving AAC from MP4 to MOV or renaming an extension is no guaranteed fix.
If AAC is the only blocked stream and the source plays correctly in an authorized external tool, create an uncompressed PCM WAV copy for the edit. For a video whose picture works while its embedded AAC is blocked, extract or transcode the audio without touching the camera original, then sync the replacement and check it. The DaVinci Resolve for Linux guide covers installation, GPU and media planning beyond this one codec.
Repair One Bad MP3 Without Converting the Whole Library
When most MP3 files import and one won’t, Resolve has already shown it can read ordinary MP3 on that machine. The Resolve manual lists MP3 and AAC (M4A) among its compatible audio formats, so put your attention on the failing source.
- Copy the file to a local folder and preserve the original unchanged.
- Play from the first seconds through the end in a second player.
- Read duration, sample rate, channels, bitrate mode, and file size in MediaInfo.
- Compare those fields with a known-good MP3 from the same recorder, downloader, or export application.
- Create one PCM WAV test copy and import it into a new empty Resolve project.
A test project takes timeline routing, old database state and project-specific media paths out of the picture. If the WAV imports and the original MP3 doesn’t, the trouble is the compressed source or the way its container and metadata were written. If neither imports, look at local access, file permissions and storage health, and check whether every known-good audio file also fails in that Resolve build.
Don’t strip tags, rewrite headers and run three converters against your only copy. Every repair step should write a new file with a clear suffix such as `_pcm48k.wav`. Hang on to the original until the project and the final delivery are done.
Create a Safe PCM WAV Edit Copy
For video work, uncompressed PCM WAV at 48 kHz is the cautious replacement: it skips another compressed-audio decoder and matches the usual production sample rate. Keep the source channel count unless you deliberately want a new layout. A mono interview shouldn’t turn into fake stereo, and a multichannel source deserves a listen and a written note before anyone collapses it.
A tool such as Shutter Encoder can convert audio to WAV. Other trusted audio applications can do the same. The settings matter more than the brand of converter:
- Output container: WAV
- Audio codec: uncompressed Linear PCM
- Sample rate: 48,000 Hz for a normal video timeline unless the project requires something else
- Bit depth: 24-bit when the source and workflow justify it; do not claim that raising bit depth restores lost MP3 or AAC detail
- Channels: preserve the source layout unless a documented downmix is required
- Normalization, noise reduction, EQ, speed, and loudness processing: off during a compatibility conversion
Convert one file first. Then re-import it and verify:
- The duration matches the source.
- The waveform covers the expected program and is not cut off.
- The channel count and left/right content are correct.
- The beginning and end play without gaps or truncation.
- When replacing embedded audio, sync remains correct at the start, middle, and end.
A 44.1 kHz source doesn’t need “improving” through conversion. The 48 kHz copy exists for predictable project compatibility. It can’t bring back frequencies or detail that MP3 or AAC compression already threw away. Keep the original as the source record and label the WAV as an edit copy derived from it.
Re-Import Before You Touch Playback Settings
Bring the WAV into the Media Pool first, look at its metadata and open it in the Source Viewer. If Resolve shows the expected duration and the clip meter moves, the import problem is solved. Only then cut it into a timeline.
If the clip is there and you still hear nothing, stop changing codecs. Work through the no-audio guide: clip enable state, source-channel mapping, track mute and solo, faders, bus assignment, monitor selection, output device and the operating system’s app volume. Re-encoding a clip Resolve already decodes won’t unmute a bus.
If the problem file came from an MP4 and Resolve sees the audio but no picture, use the MP4 audio-only import guide. That one checks the video stream and source patching. An audio-only article is the wrong tool for a missing H.264, H.265 or other video decoder.
Fixes That Usually Waste Time
- Renaming `.m4a` to `.mp3` or `.wav`: the encoded stream and protection remain unchanged.
- Buying Studio before identifying the codec: edition changes do not repair a damaged file or guarantee Linux AAC decode.
- Deleting every cache folder: import rejection happens before render cache can make the source decodable.
- Resetting all audio preferences: device and bus settings do not make a rejected file appear in the Media Pool.
- Converting an entire music library: prove the workflow with one duplicate and inspect the result first.
- Using an online converter for protected or confidential media: it can create rights, privacy, and retention problems without solving the underlying license issue.
Fast MP3 and AAC Import Checklist
- The complete file is downloaded locally. A cloud-only placeholder doesn’t count.
- The original plays from beginning to end outside Resolve.
- MediaInfo shows plausible duration, size, codec, sample rate, and channels.
- An M4A from Apple Music is checked for protection and source rights.
- The exact stream is compared with the reader’s operating system, Resolve edition, and build.
- Linux AAC gets checked early, before anyone assumes Studio or MOV will fix it.
- One duplicate is converted to PCM WAV at a project-appropriate rate.
- The WAV is checked for duration, channels, waveform, end-of-file integrity, and sync.
- Playback routing is diagnosed only after the file imports normally.
MP3 and AAC Import FAQ
Why does my MP3 play in VLC but not import into Resolve?
Players and editors can use different decoders and tolerate different file errors. Make sure the file is local, check its stream and duration in MediaInfo, compare it with an MP3 that works, then test a PCM WAV copy. Leave the original untouched.
Does DaVinci Resolve support M4A?
The Resolve manual lists AAC (M4A) as a compatible audio format, but the extension alone doesn’t settle it. Find out whether the file holds AAC, ALAC, another stream or protected subscription media. Support also depends on the platform and the Resolve build. An unprotected file with a supported stream is a different case from an Apple Music subscription download.
Should I convert MP3 to WAV before editing?
Not automatically. If the MP3 imports and behaves, converting it won’t bring back quality already lost to compression. A PCM WAV copy earns its place when the source is malformed, unreliable or unsupported where you edit.
Why does AAC fail only on DaVinci Resolve for Linux?
Resolve’s media support differs by platform, and Blackmagic forum guidance documents AAC decode limits in the Linux builds discussed there. Check your exact build and the source stream. If AAC still won’t decode, create a legitimate unprotected PCM WAV edit copy and check the sync.
Can I import a song downloaded from Apple Music?
A subscription download can be protected, and it isn’t an ordinary production audio file. Use a licensed, unprotected source you have permission to include. Don’t rename the file or run it through a converter to get around the protection.
