Recording File Audio Track Missing in Editor, VLC Has Sound? Track Mapping, Codec and Container Diagnosis Guide

2026-11-18 | GPU Repair | 44 minutes | HK GPU Fix Editorial Team

Recording File Audio Track Missing in Editor, VLC Has Sound? Track Mapping, Codec and Container Diagnosis Guide

Key Summary

A file that plays with sound in VLC but shows no audio track in an editor is not proof the file is broken, and not proof the editor is broken either. This guide uses MediaInfo, VLC's track menu, and the editor's track switches to separate a track-mapping fault from a codec or container fault, keeping the three different remedies apart.

The Shape of the Problem: Sound in the Player, No Track in the Editor

This guide is about one narrow shape, and the shape is the diagnosis. A recording is made — in OBS, in NVIDIA ShadowPlay, in the Xbox Game Bar, or in AMD ReLive — and played back in VLC it sounds exactly as it should: the game can be heard, the microphone can be heard, nothing is missing. Then that same file is opened in an editing program — Premiere Pro, Resolve, or something else — and there is no audio track on the timeline at all. The video track imports. The audio track does not. The file has sound, and the editor cannot see it.

Three details define the shape, and all three have to be present. First, the file plays with sound in VLC. A file that is silent in VLC as well belongs with a different guide. Second, the editor shows no audio track at all — not a silent track, not a track that drifts, but no track. A track that is present but silent, or present but out of sync, is a different shape. Third, the video track imports normally. A file whose video track also fails to import belongs with a different guide. Without all three, the diagnosis has no anchor, and the wrong road gets followed.

The most counter-intuitive fact about this shape has to be stated before anything else: "VLC plays it" and "the editor reads it" are two different tests, and passing one says nothing about the other. A player and an editor do different jobs. A player decodes in sequence and plays in real time, and it can drop a frame without anyone noticing. An editor has to jump to any frame on demand, decode several streams at the same time, and map each audio track onto a timeline track. A file that is easy to play can still be hard to edit, and a file that is hard to edit can still play perfectly. That is why the first conclusion most people reach — "the file must be broken, because the editor cannot see the sound" — jumps too far. It is equally possible that the file is fine and the editor is not reading it, or that the file has several audio tracks and the editor is only reading one of them, or that a single switch in the editor is turned off. The comparisons in this guide exist to tell those apart.

The shape also has to be separated from its neighbours at the start, because several of them look similar on a first viewing. One neighbouring shape is a recording file that has no audio track at all — MediaInfo shows no audio track, VLC is silent too — that is covered in the guide numbered 503, and its shape is a file with no sound to read. Another neighbour is a recording that starts with sound and goes silent halfway through — that is covered in the guide numbered 505, and the difference is decisive: in this guide the file has sound all the way through, in that guide the second half of the file is genuinely silent. A third neighbour is a recording whose sound drifts further and further out of sync with the picture — that is covered in the guide numbered 496, and its shape is a track that exists but is in the wrong place in time, not a track that is missing. A fourth neighbour is a finished edit whose sound is present but has changed pitch or speed — that is covered in the guide numbered 504, and its shape is a track that exists but sounds wrong, not a track that is absent. A fifth neighbour is a finished export that has sound but no picture — that is covered in the guide numbered 500, and it is the mirror image of this guide: a video track problem, not an audio track problem. Its conclusions must not be carried across to the audio layer. The boundary section near the end of this guide lists every one of these neighbours with the exact shape that belongs to it.

Before any test is run, write down the baseline: the recording tool and its version, the file format, the editing program and version, and the operating system. The operating system matters here, because one layer in this guide exists only on Linux.

What Is Inside a Video File

A video file is a container, and inside the container are several independent tracks: a video track and one or more audio tracks, each a separate stream of data, each with its own codec, its own time code, and its own data. MP4, MOV, and MKV are containers — the boxes the tracks are packed into. H.264, HEVC, AV1, AAC, and PCM are codecs — the methods used to compress and decompress the data. Two MP4 files can hold completely different codecs. The file extension says nothing about what is inside the box. The only way to know is to open the file in MediaInfo and read the track list.

That distinction — container against codec — is the first of three pairs of concepts this guide keeps apart, because mixing them is how this diagnosis goes wrong. A container problem and a codec problem are different layers, and they are tested in different ways. If the container is the problem — for example, an MKV holding a combination the editor does not accept, or a raw bitstream file with no container at all — then re-wrapping the tracks into a different container, without re-encoding them, is the comparison that tests it. If the codec is the problem — for example, an audio codec the editor cannot decode — then re-wrapping changes nothing, and only a transcode to a codec the editor accepts will show the difference. Changing the file extension is neither of those things. Renaming a file from .mov to .mp4 does not change the codec inside it, and it does not repair a damaged stream. A guide on umatechnology.org states this plainly: look at the actual codec and the file location, do not judge by the extension alone, and use MediaInfo to read the container, the video and audio codecs, the frame rate, the sample rate, and the channel layout.

The second pair is a missing track, against a track the editor does not read. MediaInfo showing no audio track means the file layer: the sound was never written into the file, and the road is the guide numbered 503. MediaInfo showing an audio track that the editor does not display means the reading layer: the sound is in the file, and something between the file and the timeline is failing to read it. The first fork in this guide exists to tell those two apart, and it has to be run before anything else is changed, because every step after it depends on which side of the pair the file falls on.

The third pair is a track switch, against a decoding failure. If the source viewer in the editor plays sound but the timeline shows no audio track after the clip is dragged in, the fault is in the track switches — the timeline track targeting. If the media pool already shows no audio track, the fault is in the decoding or import layer. The two are tested in different places, and they cannot be treated as the same thing. The third fork in this guide is built around exactly this pair.

Players and Editors Do Different Jobs

A player such as VLC has one job: decode in sequence and play in real time. VLC carries its own built-in decoders, so it does not depend on the system, and it plays only one audio track at a time by default — usually the first track. "VLC plays it" therefore proves exactly one thing: that the first track can be decoded by VLC's own decoders. It proves nothing about the other tracks, and it proves nothing about whether an editor can read the file.

An editor has a harder job. It has to jump to any frame on demand, which means decoding from the nearest keyframe. It has to decode several streams at the same time. And it has to map each audio track onto a timeline track. Many editors rely on system decoders rather than carrying their own — especially for HEVC, which involves patent licensing — so a file that VLC decodes with its own decoders can still be unreadable to an editor that depends on the system. A guide on xconvert.com describes this division clearly: a player works in sequence, in real time, and a dropped frame goes unnoticed, while an editor needs random access and has to decode several streams at once; and for HEVC, editing programs often rely on system decoders. That guide describes video streams, and the audio layer has to be handled with care when the same reasoning is used, but the division of labour between player and editor is the same.

Multi-Track Recording: What OBS Actually Writes

OBS can record up to six audio tracks at once. Track 1 is usually the full mix — a safety net — and Track 2 onwards each isolate one source: the microphone, the game sound, the music, and so on. But three limits decide what the file actually contains. First, FLV holds only one audio track; only Hybrid MP4, available in OBS from version 30.2 onwards, and MKV hold six. Second, VLC plays only the first track by default, so the other tracks have to be tried one by one in VLC's audio track menu before anyone can say what the file contains. Third, an editor may merge the tracks on import, and the merged tracks have to be separated again — in Premiere, through Modify, then Audio Channels. A guide on obs-versions.com describes this structure directly, and its test method is the one this guide uses: in VLC, open Audio, then Audio Track, and each track from Track 1 to Track 4 should play a different sound. A guide on obsbot.com makes the same point from the other side: a player that only plays Track 1 does not prove the other tracks are missing.

There is one more structural fact worth stating plainly, because it is the source of the most confusion in this shape. When an editor imports a multi-track file and shows only one audio track, there are two completely different explanations: the file may hold only one track, or the file may hold several tracks and the editor may only be reading the first. MediaInfo tells the two apart in one reading. Without it, the diagnosis is guessing.

The Deciding Forks: Three Comparisons That Narrow the Field

Everything in this guide hangs on three comparisons, run in order before anything is adjusted. Each comparison takes a whole group of possibilities off the table, and adjusting something too early wipes out the evidence that comparison was meant to give.

Fork One: Does MediaInfo Show an Audio Track at All?

The first fork is the MediaInfo comparison. Open the recording file in MediaInfo and look at what tracks it contains. If there is no audio track at all, the sound was never written into the file, and the fault is in the file layer — the road is the guide numbered 503, not this one. If there is an audio track, the sound is in the file and the editor is not reading it, and the investigation stays with this guide. If MediaInfo cannot read the file at all, the file structure itself is damaged, which points at the corruption road described in the final section of this guide, not at a settings problem. This fork is the one that decides whether the problem is "no track" or "track not read", and it has to be run first, because every step after it depends on the answer.

Fork Two: How Many Tracks Does VLC Find?

The second fork is the VLC track comparison. Open the file in VLC, go to Audio, then Audio Track, and try each track in turn, writing down what each track plays. If there is only one track, the fault is in the codec or container layer — the editor cannot decode that one track. If there are several tracks, the fault is in the track mapping layer — the editor is reading only one of them, or merging them. VLC plays only the first track by default, so a file that "plays with sound in VLC" may be playing only Track 1, and the other tracks may hold different sounds entirely, or may be silent, or may not exist. A guide on obsbot.com states this directly: hearing only Track 1 does not prove the other tracks are missing. And a guide on obs-versions.com gives the test method: each track from Track 1 onwards should play a different sound when selected in VLC's track menu.

Fork Three: Source Viewer Against Timeline

The third fork is the editor's own comparison. Play the clip once in the editor's source viewer, then drag it onto the timeline and look at what appears. If the source viewer has sound but the timeline has no audio track, the fault is in the track switches — the timeline track targeting. If the media pool already shows no audio track, the fault is in the decoding or import layer. A guide on davinciresolveclub.com describes this pair for the video direction: a source viewer that shows picture and sound, but a timeline that receives only audio, points at the V1 source track switch being off. That guide describes a video track failing to arrive on the timeline — the mirror image of this guide's shape — so its method is used and its direction is stated as reversed. The same pair, in the audio direction, is what this fork tests.

ForkComparisonResult AResult B
MediaInfo comparisonOpen the file in MediaInfo and list its tracksNo audio track — file layer, follow the guide numbered 503Audio track present — reading layer, follow this guide
VLC track comparisonVLC, Audio, Audio Track, try each track in turnOne track only — codec or container layerSeveral tracks — track mapping layer
Source viewer comparisonPlay the clip in the editor's source viewer, then drag it onto the timelineSource viewer has sound, timeline has no audio track — track switch layerMedia pool already has no audio track — decoding or import layer

The Five Suspicion Layers

The five layers below are the whole map of this symptom. They are ordered by the cost of testing them, not by how likely they are, and the order itself is part of the diagnosis. The MediaInfo comparison is first because its result decides whether the problem is in the file itself. The VLC track comparison is second because its result decides whether the problem is one track or several. The source viewer comparison separates the track switch layer from the decoding layer, and the two sides lead to completely different next steps. And the three remedies in this guide — changing a track setting, separating the audio tracks, and transcoding — belong to three different layers, and they must never be presented as one generic fix. Each one is tested only after its layer has been identified.

LayerWhat it isDecisive test
First layer: track mappingThe editor's timeline track switches are off, or the editor merged several tracks on import and only shows the firstSource viewer against timeline; Modify, Audio Channels in Premiere
Second layer: audio codecThe audio track uses a codec or a setting the editor cannot decode, for example AAC in Resolve on Linux, in both the free version and Studio, or a multi-track PCM combination from FFmpegMediaInfo audio codec, sample rate, and channel layout against the editor's support list
Third layer: containerThe file is an MKV or FLV or a raw bitstream with no container, in a combination the editor does not acceptMediaInfo container format; OBS Remux Recordings to MP4, then compare
Fourth layer: multi-track mappingOBS recorded several tracks, but the editor reads only the first, or the source was assigned to a track that holds silence or nothingMediaInfo track count; VLC track menu, each track in turn; OBS track assignment table
Fifth layer: file and cacheThe file structure is damaged, or the editor's cache is stale and the import result is wrongMediaInfo cannot read the file; clear the cache and re-import; transcode to H.264 plus AAC and compare

First Layer: Track Mapping

This is the layer the source viewer comparison tests. In Premiere, the V1 and A1 columns at the top of the timeline tracks have to be lit at the same time — or both unlit — or dragging a clip onto the timeline will not bring its audio with it. That is the finding of an Adobe Community thread about the V1 and A1 switches, which also notes that clearing the media cache has to be done by hand, outside the program, by deleting the cache folder. That thread does not state which version it describes, so this guide never writes its finding as a guarantee about the current version. In Resolve, the V1 source track switch has to be on, or the timeline receives no track from the source viewer.

Play the clip in the source viewer, then drag it onto the timeline, and write down what each step shows. Then open a new blank project, import the same file, and compare — a blank project removes any effect from the original project's plug-ins or settings. If the source viewer has sound and the timeline does not, that is the track switch layer. Changing a track setting is the remedy for this layer only.

Second Layer: Audio Codec

This is the layer the support-list comparison tests. An audio track can use a codec or a setting the editor cannot decode, and the editor will then show no audio track at all, without any error message that names the codec. The clearest documented case is platform-limited: DaVinci Resolve on Linux has an AAC decoding gap, and it affects the free version and Studio alike. A guide on davinciresolveclub.com, working from Blackmagic's support list for Resolve 21.1 dated September 2026, states that on Linux the AAC decoding is marked as unsupported, with no exception for the Studio version, and that Linux is the strictest platform in the list. A guide on awaketake.com states the same gap from the other side: in the free version of Resolve, an MP4 file with AAC audio will not work, and the AAC audio will not even appear on the timeline.

The platform limit has to be stated plainly, because it is the easiest fact in this guide to get wrong. The AAC gap is a Linux limitation. No source consulted for this guide says Windows or macOS has the same gap, and on those systems the same file may import completely normally. Read the MediaInfo result against the editor's support list, separately by system, version, and free version against Studio. Transcoding to H.264 plus AAC is the comparison test for this layer, not a repair in itself: if the transcoded file imports and the original does not, the original file's codec layer is the fault.

Third Layer: Container

This is the layer the remux comparison tests. A file can be in a container the editor does not accept — an MKV, an FLV, or a raw bitstream file with no container at all, such as a .hevc file. A guide on xconvert.com lists four kinds of import block: a raw bitstream with no container, a codec that works but a container that does not, a "Media Offline" result that usually means Windows is missing a decoder, and a 10-bit 4:2:2 profile problem. That guide describes HEVC video streams, and the audio layer has to be handled with care when the same list is used, but the container against codec distinction is the same.

Read the container format in MediaInfo, then use OBS Remux Recordings to re-wrap the file into MP4, and compare the import result. If the re-wrapped file imports and the original does not, the container layer is the fault. Remuxing is a comparison test for this layer only. Remuxing changes the box, not the codec. FLV holds only one audio track, so a multi-track recording made into FLV never had more than one track to lose.

Fourth Layer: Multi-Track Mapping

This is the layer the VLC track comparison tests. OBS can record up to six audio tracks, and an editor may read only the first of them. An Adobe Community thread about a multi-track clip that Premiere read as one track describes a user who recorded a multi-track stream video with OBS 26.0.2, confirmed six tracks in VLC with a different audio source on each, and found that Premiere 14.6 read only the first track. That is a real user report about old versions — Premiere 14.6 and OBS 26 — and this guide never writes the finding as current-version behaviour.

Read the MediaInfo track count, try each track in turn in VLC's audio track menu, and compare the result against the OBS track assignment table. If MediaInfo shows several tracks, VLC plays a different sound on each, and the editor shows only one, that is the multi-track layer. Separating the audio tracks — demuxing them out, for example into WAV files — is the remedy for this layer only. An Adobe Community thread describes captured audio channels mixed together that had to be demuxed before import into Premiere; that thread describes audio truncated to about a quarter of the file, not audio missing entirely.

Fifth Layer: File and Cache

This is the layer the re-import comparison tests. A recording interrupted by a crash, or never finished properly, can leave a file whose structure is damaged, and an editor's cache can go stale and make the import result wrong. The two are different faults: a damaged file shows up in MediaInfo, which cannot read it at all, while a stale cache shows up when clearing the cache and re-importing changes the result. Clearing the cache is the remedy for a stale cache only, and it must not be presented as a remedy for a codec fault.

Clear the cache and re-import, and transcode a test copy to H.264 plus AAC and compare the import result. If the transcoded file imports and the original does not, the original file's decoding layer is the fault — not necessarily file damage. Only a MediaInfo failure proves the file structure.

The Seven Diagnostic Steps

Work through the steps in the order they are given. Every step is a single comparison, and every comparison should leave a written note behind. Change only one thing per step — change two at once, and the result cannot be read, because there is no way to tell which of the two changes did it.

StepWhat to doWhat the result means
Step 1: Record the baselineWrite down the recording tool and version, the file container and codec, the editing program and version, and the operating systemWithout a baseline, "the editor cannot see the sound" is a guess, and the rest of the diagnosis has no evidence
Step 2: MediaInfo comparisonOpen the file in MediaInfo and list its tracks, codec, sample rate, channel layout, container, and frame rate modeNo audio track means the file layer, follow the guide numbered 503; an audio track means the reading layer, follow this guide
Step 3: VLC track comparisonVLC, Audio, Audio Track, try each track in turn and write down what each one playsOne track only means the codec or container layer; several tracks means the track mapping layer
Step 4: Source viewer comparisonPlay the clip in the editor's source viewer, then drag it onto the timelineSource viewer has sound, timeline has no audio track means the track switch layer; media pool already has no audio track means the decoding or import layer
Step 5: Codec and container comparisonCompare the MediaInfo result against the editor's support list by system, version, and free version against Studio; remux or transcode a test copy and compare the import resultA transcoded file that imports while the original does not points at the codec or container layer
Step 6: Multi-track comparisonCompare the OBS track assignment table against the MediaInfo track count; import the same file into a new blank project and into a different editorA blank project or a different editor that reads the tracks points at the original project's settings or the first editor's reading
Step 7: Stop lineDecide whether the layers have been separatedIf the seven steps cannot separate the layers, or the file comes with a crash or a file MediaInfo cannot read, stop and bring the records for inspection

Step 1: Record the Baseline

The first step is to describe the fault precisely. Which recording tool is it — OBS, ShadowPlay, the Xbox Game Bar, or AMD ReLive? What is the file container and what is the audio codec? Which editing program is it, and which version, and on which operating system? And which track in VLC has the sound — the first track, or a later one, and how far does it play? Write down the baseline: the recording tool and version, the file format, the editing program and version, and the operating system. The operating system has to be in the baseline, because one of the layers in this guide — the Resolve AAC gap on Linux — exists only on Linux.

Step 2: The MediaInfo Comparison

Open the recording file in MediaInfo and look at what tracks it contains. Note the audio track count, the audio codec, the sample rate, the channel layout, the container format, and whether the frame rate is fixed or variable. If there is no audio track at all, the sound was never written into the file, and the fault is in the file layer — stop following this guide and follow the guide numbered 503. If there is an audio track, the sound is in the file and the editor is not reading it, and the investigation stays with this guide — move to step three. If MediaInfo cannot read the file at all, the file structure itself is damaged, and the fault belongs with the corruption road, not with a settings problem.

Step 3: The VLC Track Comparison

Open the file in VLC, go to Audio, then Audio Track, and try each track in turn, writing down what each track plays. If there is only one track, the fault is in the codec or container layer — move to step five. If there are several tracks, the fault is in the track mapping layer — move to step six. VLC plays only the first track by default, so a file that "plays with sound in VLC" may be playing only Track 1. This step is a comparison, not a repair: it decides which of the three remedies in this guide is even in play.

Step 4: The Source Viewer Comparison

Play the clip once in the editor's source viewer, and write down whether it has sound. Then drag it onto the timeline and write down whether an audio track appears. If the source viewer has sound and the timeline has no audio track, check the track switches: in Premiere, the V1 and A1 columns at the top of the timeline tracks have to be lit at the same time; in Resolve, the V1 source track switch has to be on. If the media pool already shows no audio track, the fault is in the decoding or import layer — move to step five.

Step 5: The Codec and Container Comparison

Compare the MediaInfo result from step two against the editor's support list, reading the list separately by system, by version, and by free version against Studio. Then make a test copy and compare the import result: use OBS Remux Recordings to re-wrap the file into MP4, and transcode a second test copy to H.264 plus AAC, and import both. If the re-wrapped file imports and the original does not, the container layer is the fault. If the transcoded file imports and the original does not, the codec layer is the fault. These are two different tests for two different layers, and they must not be run as one generic "try converting it" step.

Step 6: The Multi-Track Comparison

Compare the OBS track assignment table in the advanced audio properties against the MediaInfo track count from step two. Then import the same file into a new blank project, to remove any effect from the original project's plug-ins or settings, and import the same file into a different editor — Premiere against Resolve, for example — and compare the results. If a blank project reads the audio track and the original project does not, the original project's settings are the layer. If a different editor reads the tracks and the first editor does not, the first editor's reading is the layer.

Step 7: Stop Line

If all seven steps have been run and the layers still cannot be separated, or if the file comes with a crash, or MediaInfo cannot read the file at all, stop testing and bring the full record for inspection. The written record is what makes the inspection useful: the recording tool and version, the file container and codec, the editing program and version, the operating system, the MediaInfo track list, the VLC track results, and the result of every comparison, all with the date the fault started attached.

Six Misconceptions That Mislead This Diagnosis

1. "VLC plays it, so the file must be fine."

Wrong. VLC plays only the first track by default, and it uses its own built-in decoders, while editing programs often rely on system decoders. "VLC plays it" proves that the first track can be decoded by VLC. It proves nothing about the other tracks, and it proves nothing about whether an editor can read the file. Use MediaInfo to count the tracks, and try each track in turn in VLC's track menu, before saying anything about the file.

2. "Renaming .mov to .mp4 is the same as converting."

Wrong. Changing the file extension does not change the codec inside the file, and it does not repair a damaged stream. A real conversion re-encodes the data, and a real re-wrap moves the same data into a different container. Renaming does neither.

3. "Clearing the cache will fix it."

Wrong. Clearing the cache can only deal with stale or damaged cache data. It cannot make an unsupported codec become supported. Clear the cache only when the comparison points at a stale cache — a re-import after clearing that changes the result.

4. "Transcoding to H.264 plus AAC fixes it."

Wrong. Transcoding is a comparison test, not a repair. If a transcoded file imports and the original does not, the test proves the original file's codec layer is the fault — and the transcoded file may already have lost the original multi-track structure. Treating the transcoded file as though nothing happened hides the loss. Transcoding, demuxing, and changing a track setting are three different remedies for three different layers, and they must never be presented as one generic fix. The layer has to be identified first, and only then is the remedy for that layer in play.

5. "Resolve on Linux cannot read AAC, so no platform can."

Wrong. The AAC gap is platform-limited to Linux, and it covers the free version and Studio alike on that platform. A guide on davinciresolveclub.com, working from Blackmagic's support list for Resolve 21.1 dated September 2026, states that Linux is the strictest platform in the list, with AAC decoding marked as unsupported and no exception for the Studio version. A guide on awaketake.com states the same gap for the free version on Linux. Neither source says Windows or macOS has the same gap, and on those systems the same file may import completely normally. The platform and the version have to be written down in the baseline, and the gap must never be written as a rule for all platforms.

6. "Premiere only reads the first track."

Wrong as a statement about the current version. The claim comes from old forum threads — an Adobe Community thread describing Premiere 14.6 with OBS 26, where a user confirmed six tracks in VLC and found Premiere reading only the first. That is a real user report about old versions, and it is the direct evidence for the multi-track layer, but it cannot be written as current-version behaviour. The current version has to be checked against the current support list, not against an old thread.

Comparison Table: What Each Result Points At

ObservationLayer indicatedNext test
File plays with sound in VLC, editor shows no audio trackMediaInfo comparison, step 2MediaInfo comparison, step 2
MediaInfo shows no audio trackFile layerFollow the guide numbered 503
MediaInfo shows an audio track, editor shows noneReading layerVLC track comparison, step 3
VLC finds only one audio trackCodec or container layerCodec and container comparison, step 5
VLC finds several audio tracks, editor shows only oneTrack mapping layerMulti-track comparison, step 6
Source viewer has sound, timeline has no audio trackTrack switch layerTrack switch check, step 4
Media pool already has no audio trackDecoding or import layerCodec and container comparison, step 5
Re-wrapped MP4 imports, original MKV does notContainer layerRemux comparison, step 5
Transcoded H.264 plus AAC file imports, original does notCodec layerTranscode comparison, step 5
Blank project imports the audio track, original project does notOriginal project settingsMulti-track comparison, step 6
File cannot be read by MediaInfo, or the recording was interrupted by a crashFile corruption roadStop and bring the record for inspection

What the Sources Disagree About

The sources for this guide do not all say the same thing, and the disagreements have to be written out rather than settled silently.

Which remedy should be tried first? Three different remedies appear in the sources, and they belong to three different layers. Transcoding to H.264 plus AAC appears in guides in the xconvert.com and davinciresolveclub.com style, and it is the remedy for the codec layer. Demuxing the audio tracks out into separate files appears in an Adobe Community thread, and it is the remedy for a mixed-track fault. Changing the editor's track settings appears in an Adobe Community thread about the V1 and A1 switches and in the davinciresolveclub.com guide about the V1 source track switch, and it is the remedy for the track switch layer. None of the three is a general fix: the layer has to be identified first.

How much does "VLC plays it" prove? An Adobe Community thread treats "sound in VLC but no sound in Premiere" as a sign of mixed audio — that is, as evidence pointing at the file layer. Guides on obsbot.com and obs-versions.com say the opposite in one respect: VLC plays only the first track, so hearing sound in VLC does not prove the other tracks exist. The two are not in conflict, once the distinction is stated. The first is about the comparison itself: a file that plays in VLC but not in the editor is a meaningful contrast, and it points somewhere. The second is about what VLC proves on its own: the first track plays, and nothing more. This guide writes both, and keeps them apart: the VLC-against-editor contrast is evidence, and the VLC track menu is the test that reads what the contrast means.

How strict is Resolve on Linux? A guide on davinciresolveclub.com, working from Blackmagic's support list for Resolve 21.1 dated September 2026, states that on Linux the AAC decoding is marked as unsupported, with no exception for the Studio version — so the gap covers the free version and Studio alike. A guide on awaketake.com states the same gap for the free version on Linux, and advises recording into MOV with MPEG4 video and PCM audio for direct compatibility, or transcoding to ProRes MOV with PCM audio.

Boundary: Shapes This Guide Does Not Cover

SituationWhich guide to followWhy it is not this guide
Recording file itself has no audio track at allThe guide numbered 503, recording file silentMediaInfo shows no audio track, the file layer
Recording file starts with sound, goes silent halfway throughThe guide numbered 505, mid-file silence roadThe second half of the file is genuinely silent, not unread by the editor
Recording file audio track exists but drifts out of syncThe guide numbered 496, variable frame rate driftThe audio track exists, it is in the wrong place in time
Finished edit sound present but changed pitch or speedThe guide numbered 504, sample rate roadThe sound exists, only its pitch or speed is wrong
Finished export has sound but no pictureThe guide numbered 500, video track roadA video track problem, the mirror image of this guide
Editor cannot find the graphics card, the renderer has no GPU selectedThe guide numbered 407, renderer roadThe fault is before the audio track import step
Timeline preview stutters, finished export is normalThe guide numbered 474, preview and proxy roadA preview problem, not an audio track import problem
No sound can be heard at all, live or recordedThe guide numbered 170, HDMI and DisplayPort playback chainA playback chain problem, not an import problem
Recording file has sound, but it crackles and breaks upThe guide numbered 311, game audio crackling and breaking upThe sound is degraded, not missing from the editor

When to Stop Testing

Stop testing and bring the records for inspection if any of the following apply. All seven steps have been run and the layers still cannot be separated. The recording was interrupted by a crash, or MediaInfo cannot read the file at all — that is the corruption road, not a settings problem. The file has no audio track at all, which belongs with the guide numbered 503. The file starts with sound and goes silent halfway through, which belongs with the guide numbered 505. The sound drifts out of sync rather than disappearing, which belongs with the guide numbered 496.

What to Bring for Inspection

Bring the machine itself if you can manage it; if not, the written record will do. What matters here is the figures, not the conclusions: the recording setup, tool and version included, the file's container and codec, and the editing program with its version; the operating system too, because one layer in this guide only exists on Linux; the MediaInfo reading — how many audio tracks are in the file, and each one's codec, sample rate, and channel layout; and what each comparison showed — the VLC track results, the source viewer against the timeline, the codec and container checks, and the multi-track check — with the step each one came from named. The published three-tier inspection and repair pricing for this service is HK$400–2,800, and the exact tier depends on what the inspection finds; no price is quoted before the inspection, because the fault has not been located yet. The shop is at Room 1209, Dali Plaza, Shek Mun. The telephone number is 2186 8010, and the WhatsApp number is 6558 6806. There is no shop in Mong Kok, and there is no on-site service.

Frequently Asked Questions

1. VLC plays my recording with sound, but Premiere shows no audio track. Is the file broken?

Not necessarily. A player and an editor do different jobs, and passing one test says nothing about the other. VLC carries its own built-in decoders and plays only the first track by default, while an editor has to jump to any frame on demand, decode several streams at once, and map each audio track onto a timeline track, often relying on system decoders. The first step is the MediaInfo comparison: open the file in MediaInfo and check whether it has an audio track at all. If it does, the sound is in the file and the editor is not reading it.

2. How do I check how many audio tracks my file actually has?

Open the file in MediaInfo and read the track list: the audio track count, the audio codec, the sample rate, and the channel layout. Then open the file in VLC, go to Audio, then Audio Track, and try each track in turn, writing down what each one plays. MediaInfo says how many tracks the file holds; VLC says what each track contains. The two have to be read together.

3. How do I try each audio track in VLC, one by one?

In VLC, open Audio, then Audio Track, and select each track in turn, writing down what each one plays. If there is only one track, the fault is in the codec or container layer; if there are several, the fault is in the track mapping layer. Try every track: VLC plays only the first track by default, so hearing the first track proves nothing about the others — neither that they exist nor that they are missing.

4. My source viewer has sound but the timeline has no audio track. What does that mean?

It means the fault is in the track switches, not in the decoding. In Premiere, the V1 and A1 columns at the top of the timeline tracks have to be lit at the same time, or dragging a clip onto the timeline will not bring its audio with it. In Resolve, the V1 source track switch has to be on. That finding comes from an Adobe Community thread, which does not state which version it describes, so it cannot be written as a guarantee about the current version. Check whether the two columns are lit together, then try importing the same file into a new blank project. If the media pool already shows no audio track, the fault is in the decoding or import layer instead.

5. What is the difference between a container problem and a codec problem?

A container is the box — MP4, MOV, MKV — and a codec is the method used to compress and decompress the data — H.264, HEVC, AAC, PCM. Two MP4 files can hold completely different codecs. A container problem means the editor does not accept the box the tracks are packed into, and re-wrapping the tracks into a different container is the comparison that tests it. A codec problem means the editor cannot decode the data inside, and re-wrapping changes nothing — only a transcode to a codec the editor accepts will show the difference. Changing the file extension is neither: renaming a file does not change the codec inside it.

6. Why does Resolve on Linux not read my AAC audio?

Because the AAC gap is a Linux limitation, and it affects both the free version and Studio on Linux: on Linux, Resolve cannot decode AAC, and an MP4 file with AAC audio will not show its audio on the timeline. A guide on davinciresolveclub.com, working from Blackmagic's support list for Resolve 21.1 dated September 2026, states that on Linux AAC decoding is marked as unsupported, with no exception for the Studio version. A guide on awaketake.com states the same gap for the free version on Linux. No source says Windows or macOS has the same gap, and on those systems the same file may import completely normally.

7. Will renaming .mov to .mp4 make my editor recognise the audio track?

No. Renaming a file changes only its name: the codec inside stays exactly as it was, and a damaged stream is not repaired. A real conversion re-encodes the data. The extension is only a label on the box; what codec is packed inside cannot be changed by changing the label. When an import fails, look at the actual codec first, not the extension.

8. Should I transcode the file to H.264 plus AAC?

Not as a first step, and not as a fix on its own. Transcoding is a comparison test for the codec layer: if a transcoded file imports and the original does not, the test proves the original file's codec layer is the fault.

9. Should I just demux the audio tracks out into WAV files?

Only if the layer has been identified as a mixed-track fault. Demuxing is the remedy for the multi-track layer: OBS can record up to six audio tracks, with Track 1 usually the full mix and each track from Track 2 onwards isolating one source, and an editor may read only the first of them. An Adobe Community thread describes captured audio channels mixed together that had to be demuxed before import into Premiere. But that thread describes audio truncated to about a quarter of the file, not audio missing entirely, and the claim that Premiere reads only the first track comes from an old thread — Premiere 14.6 with OBS 26 — not current-version behaviour. Demuxing is not a general fix: an FLV file holds only one track, so there is nothing to demux, and a codec-layer fault is not helped by demuxing either.

10. When should I stop testing and bring it in for inspection?

When all seven steps have been run and the layers still cannot be separated, when the recording was interrupted by a crash, or when MediaInfo cannot open the file at all. Bring everything written down so far: the recording setup and versions, the operating system, the MediaInfo track list, what each VLC track played, and the outcome of every comparison. The published three-tier inspection and repair pricing is HK$400–2,800, depending on what the inspection finds. The shop is at Room 1209, Dali Plaza, Shek Mun, telephone 2186 8010, WhatsApp 6558 6806.

Sources

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: