Exported Video Has Audio but No Picture? Encode, Mux & Video Track Diagnosis Guide

2026-11-17 | GPU Repair | 40 minutes | HK GPU Fix Editorial Team

Exported Video Has Audio but No Picture? Encode, Mux & Video Track Diagnosis Guide

Key Summary

The export finishes without an error, but the finished file plays sound with a black screen and no picture at all. This guide separates a missing video track from a playback decoding fault, using MediaInfo and a player comparison to find which layer the picture belongs to. Work through the five layers in order, changing one setting at a time.

The Shape of the Problem: Sound, No Picture, Export Finished

This guide covers one specific shape, and the shape itself is the whole diagnosis. The export runs to completion. There is no error message, no stop halfway, and no failed render. The finished file is opened, and the sound plays normally from start to finish — voices, music, and effects are all there, and the timeline position moves forward as expected. But there is no picture at all. The screen stays black from the beginning to the end, or shows nothing where the picture should be, while the sound carries on as if nothing were wrong.

Three details define the shape, and all three have to be present. First, the export finished. The process did not fail, did not stop, and did not report an error. Second, the sound is normal. It plays all the way through, at the right places, which shows that the file is not empty and the player is reading part of it correctly. Third, the picture is completely absent — not damaged, not flickering, not partly there. A file with a broken picture, with coloured blocks, a torn image, a flash, or a single black frame, is a different shape. A file that never exported at all is a different shape again. And a file whose picture was already missing in the preview is a different shape too.

That combination is what makes this symptom different from its neighbours. One neighbouring shape is an export that fails partway through — an error message, a stop, or a render that never finishes. That shape is covered in the guide numbered 476, and it is not this one: here the export completed. Another neighbouring shape is a finished file with a broken picture — green blocks, a torn image, a flash, or a black frame — where the picture is there but damaged. That shape is covered in the guide numbered 493, and it is not this one: here there is no picture at all. A third neighbour is a protected video that plays with a black screen and sound, covered in the guide numbered 438 — that is a playback protection handshake for streamed content, not an editing export, and the file in that shape was never made by an editor. A fourth neighbour is the exact mirror image: the preview itself is damaged, with a green or purple screen, while the finished file comes out normal. That shape is covered in the guide numbered 488. And a fifth neighbour is a finished file whose picture is present but whose colours are wrong, covered in the guide numbered 499 — there the picture exists and only the colour has shifted. Each of those guides has its own shape, and this guide starts from a different one: export finished, sound normal, picture completely absent.

The first conclusion most editors reach is that the whole file is damaged, or that the player is broken. Both conclusions jump too far. Sound and picture live in separate streams inside the same file, and sound working proves only that the audio stream is sound — it proves nothing at all about the video stream. The video track can be missing entirely while the audio track plays perfectly, and a player can fail to decode a video track that is present in the file while still playing the audio track without any trouble. The rest of this guide is about testing which of those two situations applies, instead of assuming the file is destroyed or the player is at fault.

One practical distinction has to be settled before anything else, because two things that sound alike are not the same. A completely black picture and a completely missing video track are two different things. A black picture can mean the encoding went wrong and the video frames were written as black. A missing video track means there is no video stream in the file at all for any player to decode. The tool that separates them is MediaInfo, described in step two, and no conclusion about the file should be drawn before it has been run. Also note, before any testing begins, whether the picture is missing from the very start to the very end, or only in some places. A picture missing from start to finish points at a missing video track or a failed encode, while a picture missing only in some places points at file damage or an encode that went wrong partway through. That time pattern should be written down before the first test is run.

How a Video File Holds Sound and Picture Apart

To understand why a file can have sound and no picture, it helps to know what a video file actually is. A video file is a container, and inside the container sit several independent tracks. The video track and the audio track are separate streams of data. They are written separately, stored separately, and decoded separately. The audio track working only proves that the audio stream was written correctly and can be decoded. It says nothing at all about the video stream.

The video track can go missing for three reasons. First, it may never have been written during encoding — the export settings were wrong, the renderer was not set correctly, or an effect or a composite on the timeline produced no picture for the encoder to write. Second, it may have been encoded but never written into the container — the encoder produced the picture, but the step that packs the streams into the file, called muxing, failed to include the video track. Third, the file itself may be damaged or unfinished — the export was interrupted by a power cut, the disk filled up, or the program closed before the file was properly finished, so the video track cannot be recognised even though some of its data may be present.

That separation is the counter-intuitive core of the whole problem: sound does not mean there is a picture. The audio track and the video track are two independent streams, and the audio track working only says that the audio stream is sound. An editor who hears the sound and concludes the file is fine has tested the wrong stream. An editor who sees no picture and concludes the file is destroyed has also jumped too far, because a video track that is present but undecodable looks exactly the same on screen as a video track that is missing — black, with sound — and only MediaInfo can tell the two apart.

A second concept has to be kept separate from the first: the container is not the codec. MP4, MOV, and MKV are containers — the box that holds the streams. H.264, HEVC, AV1, and ProRes are codecs — the methods used to compress and decompress the picture. Two MP4 files can hold completely different codecs inside them, and a player that can decode one codec may not be able to decode another. A file with the extension MP4 does not necessarily contain an H.264 video track. The extension says what box the file is in; it says nothing about what is inside the box. That is why the file must be inspected with MediaInfo rather than judged by its extension.

A third concept matters for the decoding layer. A video track can be present in the file and still not play, because the player cannot decode it. That can happen because the codec is not supported on that system — HEVC, for example, needs an extension on some Windows installations before it can be decoded — or because hardware decoding has gone wrong, or because the video track has been disabled or hidden in a multi-track file. In each of those cases the data is in the file, and a different player with its own built-in decoders may show it perfectly. That is why the player comparison in this guide uses VLC, which carries its own decoders and does not depend on the system codecs: a file that plays in VLC but not in another player is pointing at the decoding layer, not at the file.

The timeline adds a further layer. An effect, a composite, or a plug-in on the timeline can produce no picture for the encoder — a frame that renders as nothing, or a section of the timeline that the renderer cannot process. If that happens, the encoder has nothing to write for those frames, and the video track can come out empty or damaged. The same applies to the export settings: if the video track has been switched off in the export settings, or the wrong format or codec has been chosen, the file can be written with sound and no picture by design, without any error being reported. That is why the settings check in step three comes before any re-export, and why no re-export should be run before the settings have been read.

The Deciding Forks: Three Questions That Narrow the Field

The whole guide turns on three forks. Each fork is a comparison, and each comparison removes a whole set of possibilities. They should be done in order, before any setting is changed, because a setting changed before the fork is tested destroys the evidence the fork would have given.

Fork One: Is There a Video Track in the File at All?

The first fork is the MediaInfo comparison, and it is the cheapest test in the guide. Use MediaInfo to read what tracks the finished file contains. If there is only an audio track and no video track, the fault is locked to the encoding and muxing layers — the file contains no picture data at all, and no player can be blamed. If there is a video track as well as an audio track, move to the second fork. If MediaInfo cannot read the file at all, the file structure itself is damaged, and the investigation moves to step seven. This fork decides whether the problem is in the file at all, and that is why it comes first. No player should be blamed and no codec pack should be installed before this fork has been run, because installing decoders for a file that has no video track to decode wastes the investigation entirely.

Fork Two: Does VLC Show the Picture?

The second fork is the player comparison. Take the same finished file and open it in VLC, which carries its own decoders, and in another player. If VLC shows the picture and the other player does not, the fault belongs in the playback decoding layer — the video track is in the file, but the other player cannot decode it. If VLC cannot show the picture either, the fault belongs in the encoding or file layer, and the investigation moves on. This fork is what separates a decoding problem from a file problem, and it only works because VLC does not depend on the system codecs. A file that plays in VLC is not thereby repaired — it still has to be usable in the players and platforms it was made for — but the fork has shown where the fault lives, and that is the result.

Fork Three: Is the Picture Missing Everywhere, or Only in Places?

The third fork is the time pattern, recorded in the opening section. If the picture is missing from the very start to the very end, the fault points at a missing video track or a failed encode — the video stream was never written, or it was written wrong from the first frame. If the picture is missing only in some places, while other parts of the file show a picture, the fault points at file damage or an encode that went wrong partway through. A picture that is present at the start and disappears later, or that appears and disappears at the same places every time, should be noted with its time positions, because those positions are evidence for the file layer. A pattern that changes from one playback to the next is different again, and it should be written down rather than averaged away.

ForkComparisonResult AResult B
MediaInfo track checkWhat tracks the finished file containsAudio track only, no video track — encoding and muxing layerVideo track and audio track both present — move to the player fork
Player comparisonSame finished file in VLC and another playerVLC shows the picture, the other player does not — playback decoding layerVLC cannot show the picture either — encoding or file layer
Time patternWhere in the file the picture is missingMissing from start to finish — missing track or failed encodeMissing only in some places — file damage or partial encode failure

The Five Suspicion Layers

A finished file with sound and no picture can fail at five layers, and they must be kept separate. Changing the export settings, the encoder, and the player all at once and finding the picture back proves nothing about which change did the work, and the fault will return the next time only one of those conditions is present. The layers below run from the file structure to the export settings, and each one has its own deciding evidence. The order itself is the diagnosis: the MediaInfo check is cheapest and decides whether the file is at fault at all, so it comes first; the player comparison is the second fork and decides whether to work on the file or on the decoding; the rendering and settings layers need one-at-a-time comparisons, so they come after the file has been read.

LayerWhat it coversDeciding evidence
1. File structure layerThe finished file contains no video track at all, or the video track cannot be recognisedMediaInfo comparison: what tracks, what codec, and what resolution the file contains
2. Encoding layerThe encoder could not produce a picture, or the picture it produced was never written into the fileSoftware encoding comparison: a short clip re-exported with software or CPU encoding brings the video track back
3. Rendering layerAn effect, a composite, or a plug-in on the timeline produces no picture for the encoderEffect comparison: disabling one effect at a time brings the video track back for the same short clip
4. Playback decoding layerThe video track is in the file, but the player cannot decode it — codec not supported, or hardware decoding at faultPlayer comparison: VLC shows the picture and another player does not; switching hardware acceleration off changes the result
5. Export settings layerThe export settings are wrong — the video track switched off, the wrong format chosen, or the data range not matchingSettings comparison: the video track is switched off in the export settings, or the format and codec do not fit

Layer One: The File Structure Layer

The first layer is the structure of the file itself. The finished file may contain no video track at all, or it may contain a video track that cannot be recognised because the file was never properly finished. The signature of this layer is the MediaInfo result: MediaInfo shows only an audio track, or it shows a video track with no usable codec or resolution, or it cannot read the file at all. In the first case the video data was never written. In the second case the data may be present but the file header is damaged, so no player can find the track. In the third case the file structure itself is damaged, and the investigation moves straight to step seven rather than spending time on players or codecs. This layer is the most decisive in the guide, because a file with no video track cannot be made to show a picture by changing players, installing decoders, or switching hardware acceleration off. Those steps only help when a video track exists to be decoded, and this layer is where that question is answered.

Layer Two: The Encoding Layer

The second layer is the encoder. The encoder takes the rendered frames from the timeline and compresses them into a video stream. If the encoder cannot produce a picture — because hardware encoding has gone wrong, or because the encoder was given frames it could not process — then there is no video stream to write into the file, and the finished file will have sound and no picture. The signature of this layer is the software encoding comparison: re-export the same short clip with software-only or CPU encoding, and see whether the video track comes back. If it does, the fault follows the hardware encoding path. If it does not, the fault is further back, in the rendering or the settings. This comparison is a test, not a repair: using software encoding permanently gives up graphics acceleration, and it does not repair the original export problem. It only shows which layer the fault belongs to, and that evidence should be written down as a comparison result.

Layer Three: The Rendering Layer

The third layer is the rendering of the timeline itself. An effect, a composite, or a plug-in on the timeline can produce no picture for the encoder. A single effect that the renderer cannot process can leave a whole section of the timeline with nothing to encode, and if that section covers the whole clip, the finished file will have no picture at all. The signature of this layer is the effect comparison: disable the effects on the timeline one at a time, export the same short clip after each change, and see which disabled effect brings the video track back. The effect that brings the picture back is the one the fault follows. This step must be done one effect at a time, because disabling several effects at once and finding the picture back proves nothing about which effect mattered. The timeline should also be isolated section by section, so that the part of the timeline where the fault begins can be found, rather than the whole project being treated as one block.

Layer Four: The Playback Decoding Layer

The fourth layer is the player decoding the file. The video track is in the file, the codec and the resolution are readable in MediaInfo, but the player cannot decode it. That can happen because the codec is not supported on that system — HEVC, for example, needs an extension on some Windows installations — or because hardware decoding has gone wrong, or because the video track has been disabled or hidden in a multi-track file. The signature of this layer is the player comparison: VLC shows the picture and another player does not, or switching hardware acceleration off in the player changes the result. VLC carries its own decoders, so it is the reference player for this fork. In VLC, the codec information can be checked under Tools and then Codec Information, and the video menu can show whether a video track is present but disabled. One caution applies here: a file that plays in VLC is not repaired. The file still has to be usable in the players, software, and platforms it was made for, and a decoding fault that only VLC can work around is still a fault that needs a usable answer, such as a re-export in a more widely supported codec.

Layer Five: The Export Settings Layer

The fifth layer is the export settings. The video track may have been switched off in the export settings, or the wrong format or codec may have been chosen, or the data range may not match the footage. In each of those cases the file is written exactly as it was told to be written — with sound and no picture, or with a codec the target player cannot read — and no error is reported, because nothing failed. The signature of this layer is the settings comparison: open the export settings and check whether the video track is switched on, whether the format and codec fit the target, and whether the data range fits the footage. A setting that is wrong should be corrected and then tested with a short clip, not with a full re-export, so that the result can be read quickly. This layer is checked after the MediaInfo fork, because the settings can only be judged once the file has been read: a settings error concluded before MediaInfo has been run is a guess, and a guess that changes the export settings destroys the evidence the MediaInfo result would have given.

The Seven Diagnostic Steps

The steps below are comparison tests. Each one changes one variable and records the result. Changing two things at once and finding the picture back proves nothing about which change mattered, and the fault will return the next time only one of those conditions is present. Write down each result before moving on.

Step 1: Record the Baseline

Before anything is changed, record the baseline. What format and codec the finished file is in, and whether the export reported any error. Whether the picture is missing from the very start to the very end, or only in some places, and at which time positions. Whether the sound is normal all the way through. The editing software and its version, the export settings including the format, the codec, and whether hardware or software encoding was used, and the size of the finished file. A file that is far smaller than expected for its length and resolution is itself a clue, because a file with no video track will usually be much smaller than a file with a picture, but the size alone is not a verdict — it is a note to be read alongside the MediaInfo result. Without this record, later comparisons have nothing to compare against, and a fault that changes form halfway through the investigation will look like a new problem when it is the same one wearing a different shape.

Step 2: The MediaInfo Comparison

Use MediaInfo to read what tracks the finished file contains. If there is only an audio track and no video track, the fault is locked to the encoding and muxing layers, and the investigation moves to step three. If there is a video track as well as an audio track, note the codec and the resolution, and move to step four. If MediaInfo cannot read the file at all, the file structure is damaged, and the investigation moves to step seven. MediaInfo reads the file without changing it, so this step is safe to repeat, and the track list should be written down exactly as MediaInfo reports it. Do not judge the file by its extension in this step: two MP4 files can hold different codecs, and the extension says nothing about what is inside. The MediaInfo result is the first fact the whole investigation rests on, and no player, codec pack, or re-export should be tried before it is in hand.

Step 3: The Export Settings Comparison

Check the export settings for the video track. Is the video track switched on? Is the format the one intended? Is the codec the one intended? Does the data range fit the footage? If a setting is wrong, correct that one setting and export a short clip to compare, writing down the result before changing anything else. If the settings are correct, move to step five. This step comes after MediaInfo because the settings can only be judged once the file has been read. A settings error found here is a clean result: a single setting corrected, a short clip re-exported, and the video track back is evidence for the settings layer. A settings check that finds nothing wrong is also a result, and it should be written down as such rather than treated as a wasted step.

Step 4: The Player Comparison

Take the same finished file and open it in VLC and in another player. If VLC shows the picture and the other player does not, the fault belongs in the playback decoding layer. Try switching hardware acceleration off in the player that cannot show the picture — in VLC, under Tools, then Preferences, then Input and Codecs, then Hardware-accelerated decoding — and see whether the picture appears. Check the codec information in VLC under Tools and then Codec Information, and check the Video menu to see whether a video track is present but disabled or hidden. If a more widely supported codec is needed, a short test transcode to H.264 can show whether the picture is readable in that form, using a command such as converting the file with libx264 for video and AAC for audio. That transcode is a comparison test, not a repair: it shows whether the picture data is present and readable in another form, and it does not repair the original export. If VLC cannot show the picture either, move to step five.

Step 5: The Software Encoding Comparison

Re-export the same short clip with software-only or CPU encoding, changing nothing else. If the video track comes back, the fault follows the hardware encoding path. If the video track is still missing, move to step six. This step is a comparison test, not a repair. Using software encoding permanently gives up graphics acceleration, and it should not be left switched on as if the problem were solved. The result should be written down as a comparison result: which encoder was used, what the short clip contained, and whether the video track was present in the re-exported file, checked again with MediaInfo rather than judged by eye alone.

Step 6: The Effect-by-Effect Comparison

Disable the effects on the timeline one at a time, exporting the same short clip after each change, and compare the result each time. When the video track comes back after one particular effect is disabled, the fault follows that effect. Then isolate the timeline section by section, to find which part of the timeline the fault begins in. This step is the most labour-intensive in the guide, and it should not be started before the cheaper comparisons have been run, because an effect fault concluded too early will send the investigation into disabling effects that were never the problem. Write down each effect disabled, each short clip exported, and whether the video track was present, because that table is the evidence for this layer.

Step 7: Decide and Prepare for Inspection

Once a layer has been found, write down the comparison results that point to it, and do not change several settings at once. Then assemble the conclusion in three sentences: what the symptom is, which variable made the symptom appear or disappear, and which possibilities are still not ruled out. Write it down with the full record: the format and codec, the MediaInfo track list, the export settings, the player comparison result, the software encoding result, and the effect comparison result. If all seven steps have been run and the layers still cannot be separated, or if the finished file is accompanied by a blue screen, a missing graphics card in Device Manager, or a burning smell, stop and bring the record to inspection. One point matters more than any other in this step: do not delete or overwrite the original finished file before the layers have been separated, and do not treat a file suspected of damage as the only copy. Keep the original, the short test exports, and the written record together, and keep the original timeline and footage as well, because a file with no video track can be re-exported from the timeline when the timeline and the footage are still there.

Six Misconceptions That Mislead This Diagnosis

Misconception 1: Sound Means the File Is Fine

Sound and picture are two independent streams inside the same container. The audio track working only proves that the audio stream was written correctly and can be decoded. The video track can be completely missing while the audio track plays perfectly. A file that has sound is not thereby a file that has a picture, and the two streams must be tested separately — the audio track by listening, the video track by reading the file with MediaInfo.

Misconception 2: An MP4 Extension Means There Must Be an H.264 Picture Inside

The container is not the codec. MP4, MOV, and MKV are containers, and H.264, HEVC, AV1, and ProRes are codecs. Two MP4 files can hold completely different codecs, and a player that can decode one may not be able to decode another. The extension says what box the file is in, and nothing about what is inside the box. The file must be read with MediaInfo to find out what tracks, what codec, and what resolution it actually contains, and no conclusion should be drawn from the extension alone.

Misconception 3: A Player That Shows the Picture Means the File Is Repaired

A file that plays in VLC has only shown that its picture data can be decoded by a player with its own built-in decoders. That is valuable evidence — it proves the video track is present — but it is not a repair. If the file has to be handed to other people, other software, or other platforms, the problem is still there, because those players and platforms may not decode it either. The file still needs a usable answer, such as a re-export in a more widely supported codec, and the VLC result should be written down as a comparison result, not reported as a fix.

Misconception 4: Switching to Software Encoding or H.264 Counts as a Repair

Software encoding and transcoding to H.264 are comparison tests, not repairs. Software encoding can show whether the fault follows the hardware encoding path, and transcoding can show whether the picture data is present and readable in another form. Neither repairs the original export problem. Using software encoding permanently gives up graphics acceleration, and transcoding only makes the file playable in more places — it does not repair the export that produced a file with no video track. Record the comparison result and continue from the layer it points to.

Misconception 5: Installing a Universal Codec Pack Will Solve It

A codec pack should not be installed blindly, and certainly not before the layers have been separated. A codec pack from an unknown source can bring its own problems, and it cannot help at all when the file has no video track to decode. The correct order is to read the file with MediaInfo first, separate a file problem from a decoding problem, and only then decide what the next step is. Installing decoders for a file that has no video track wastes the investigation, and overwriting the original file before that decision has been made destroys the evidence.

Misconception 6: A Missing Video Track Means the Picture Is Lost Forever

A missing video track means two completely different things, and they must not be confused. If the file never had the video data written into it, the picture cannot be recovered from that file — but the original timeline and footage are usually still there, and a re-export can produce a file with a picture. If the file has a video track that a player cannot decode, the picture is in the file, and a different player or a transcode can show it. Until MediaInfo has been read, neither conclusion can be drawn, and the file should not be written off. Even when MediaInfo shows no video track, a re-export from the timeline is still available while the timeline and the footage remain.

Comparison Table

The table below puts the comparison results side by side. Each comparison changes one variable at a time; a different result points in a different direction.

ComparisonResult AResult BWhat to record
MediaInfo track checkAudio track only, no video trackVideo track and audio track both presentTrack list, codec, resolution, exactly as reported
Player comparisonVLC shows the picture, the other player does notVLC cannot show the picture eitherWhat each player shows, hardware acceleration setting
Export settings comparisonVideo track switched off, or format and codec wrongSettings correct, fault elsewhereFormat, codec, video track setting, data range
Software encoding comparisonShort clip re-exported with software encoding brings the video track backVideo track still missingEncoder used, short clip contents, MediaInfo result
Effect comparisonOne disabled effect brings the video track backNo single disabled effect changes the resultEach effect disabled, each short clip, video track present or not

Each comparison has to be run separately and recorded separately. Saying from memory that the picture came back after a change has no diagnostic value — run the comparison again with the same short clip and write both results down before comparing them.

What the Sources Disagree About

The published sources do not agree with each other, and both sides are given below.

First, switching hardware acceleration off against transcoding to another codec. One source describes switching hardware acceleration off as the most common answer for a black screen with sound. Other sources put the emphasis on codec support, and describe the codec as the deciding factor. Both are correct, but they are aimed at different layers: switching hardware acceleration off only helps when the video track exists but cannot be decoded, and it is completely useless when there is no video track at all. Until MediaInfo has been read, neither answer can be claimed first, and this guide follows the position that the MediaInfo fork comes before either of them.

Second, a repair tool against a re-export. One source describes a repair tool as able to repair a black screen or a missing picture. The same source states plainly, in its own words, that if the video frames were never written, or were overwritten, or are missing, a repair tool cannot rebuild picture data that was never there. For an editing export, the original timeline and footage are usually still available, so a re-export is the proper path, not a repair tool. This guide follows the position that a repair tool should never be presented as the first step or as a universal answer, and that the tool's own admission should be stated alongside its claim.

Third, file damage against a player problem. One source says most cases are not file damage at all, only a player that cannot draw the picture. Another source says file damage needs a repair. The two claims are aimed at different shapes: a file that VLC can play is a player problem, while a file that VLC cannot play and that MediaInfo shows has no video track is a file problem. Neither claim can be written as a general conclusion, and this guide follows the position that the shape decides which claim applies.

Fourth, there is a disagreement about how to describe the comparison steps. Third-party tutorials often describe switching hardware acceleration off, switching to software encoding, and transcoding to H.264 as repairs. This site's position is that all of them are comparison tests. They produce evidence about which layer the fault belongs to, and they are not repairs. This guide follows that position throughout: no comparison step is presented as a fix.

Two further points should be stated plainly. A completely black picture and a completely missing video track are two different things — a black picture can mean the encoding went wrong and the frames were written as black, while a missing video track means there is no video stream in the file at all — and the distinction is the core of the first fork. And the Windows 11 24H2 note about AC-3 audio is an audio track matter, not a missing picture matter, and it should not be used to explain a file with sound and no picture.

When to Stop Testing

Sound-with-no-picture testing carries risk if it is done in the wrong order. Do not delete or overwrite the original finished file before the layers have been separated, and do not treat a file suspected of damage as the only copy. The original file is the evidence for the comparison, and deleting it removes the baseline. Do not install a codec pack from an unknown source before MediaInfo has been read: a pack cannot help a file with no video track, and it can bring its own problems. Do not change several settings at once. A test that has already given a clear result does not need to be run again, and a settings change that brings the picture back in one player while leaving it missing in another is a result in itself — record it and move to the next comparison instead of chasing that player further.

Stop immediately if the finished file is accompanied by a blue screen, a missing graphics card in Device Manager, or a burning smell. Those are signs to stop and arrange inspection, not to keep testing. Stop also if the export itself starts failing — errors, stops halfway, or never finishing — because that shape belongs with the guide numbered 476. Stop if the finished file has a broken picture, with coloured blocks, a torn image, a flash, or a black frame, because that shape belongs with the guide numbered 493. Stop if the preview itself is damaged while the finished file is normal, because that is the mirror shape covered in the guide numbered 488. Stop if the problem is a protected video with a black screen and sound, because that is the playback protection shape covered in the guide numbered 438. Stop if the problem is live encoding overload with dropped frames during a stream or a recording, because live encoding has a real-time deadline and is different from an editing export, as covered in the guide numbered 171. And stop if the editing software cannot find the graphics card at all, because that shape belongs with the guide numbered 407, where the renderer was never set to the graphics card in the first place.

What to Bring for Inspection

If the comparisons point nowhere conclusive, or if they point toward a layer that cannot be separated at home, the next step is a professional inspection. Bring the full record: the format and codec of the finished file, the MediaInfo track list exactly as reported, the export settings including whether hardware or software encoding was used, the player comparison result with what each player showed, the software encoding comparison result, and the effect-by-effect comparison result with each effect and each short clip. The three-sentence conclusion from step seven is the summary of that record. Bring the original finished file as well, on the same storage it was exported to, together with any short test exports, and keep the original timeline and footage available, because a file with no video track can be re-exported from the timeline when the timeline and the footage are still there.

Inspection and repair pricing follows the site's published three-tier scale of HK$400 to HK$2,800, with the actual quote given after inspection. No price in this guide should be read as a quote for a particular fault, and no fee is stated here for any specific repair.

The workshop is at Room 1209, Dali Plaza, Shek Mun. The telephone number is 2186 8010, and the WhatsApp number is 6558 6806. There is no Mong Kok shop, and there is no on-site service — inspection is carried out at the workshop.

Frequently Asked Questions

My export finished, but the file has sound and no picture. Is the whole file damaged?

Not necessarily. Sound and picture are separate streams inside the same file, and sound working only proves the audio stream is sound. Use MediaInfo to read what tracks the file contains. If there is only an audio track and no video track, the fault is in the encoding and muxing layers. If there is a video track as well, the fault may be in the playback decoding layer. Do not conclude the file is destroyed before MediaInfo has been run.

What is the difference between a black picture and a missing video track?

They are two different things. A black picture can mean the encoding went wrong and the video frames were written as black. A missing video track means there is no video stream in the file at all for any player to decode. Both look the same on screen — black, with sound — and only MediaInfo can tell them apart. Read the track list before drawing any conclusion about the file.

The file plays with a picture in VLC but not in another player. What does that mean?

It means the video track is in the file, but the other player cannot decode it. VLC carries its own decoders and does not depend on the system codecs, so a file that plays in VLC and not elsewhere is pointing at the playback decoding layer. Try switching hardware acceleration off in the player that cannot show the picture, and check the codec information in VLC. The file is not thereby repaired — it still has to be usable in the players it was made for.

The file has an MP4 extension. Does that mean it must contain an H.264 picture?

No. The container is not the codec. MP4, MOV, and MKV are containers, and H.264, HEVC, AV1, and ProRes are codecs. Two MP4 files can hold completely different codecs, and a player that can decode one may not be able to decode another. Use MediaInfo to find out what tracks, what codec, and what resolution the file actually contains, and do not judge it by its extension.

Should I install a universal codec pack to fix it?

No, not before the layers have been separated. A codec pack from an unknown source can bring its own problems, and it cannot help at all when the file has no video track to decode. Read the file with MediaInfo first, separate a file problem from a decoding problem, and only then decide what the next step is. Installing decoders for a file that has no video track wastes the investigation.

Will switching to software encoding fix the missing picture?

No, not as a repair. Switching to software-only or CPU encoding is a comparison test: re-exporting the same short clip with software encoding can show whether the fault follows the hardware encoding path. If the video track comes back, that is valuable evidence for the encoding layer. Using software encoding permanently gives up graphics acceleration, and it does not repair the original export problem. Record the result and continue from the layer it points to.

The picture is missing only in some places, not the whole file. What does that mean?

It means the fault may be file damage or an encode that went wrong partway through, rather than a missing video track. A picture missing from the very start to the very end points at a missing track or a failed encode, while a picture missing only in some places points at damage or a partial encode failure. Note the time positions where the picture disappears, because those positions are evidence for the file layer.

Can a repair tool bring back a video track that was never written?

No. A repair tool can work on picture data that exists but is damaged or unreadable, but it cannot rebuild picture data that was never written into the file. The source that promotes such a tool states this plainly itself: if the video frames were never written, were overwritten, or are missing, the tool cannot rebuild them. For an editing export, the original timeline and footage are usually still available, so a re-export is the proper path, not a repair tool.

The video track is missing. Is the picture lost forever?

Not necessarily. A missing video track has two different meanings, and they must not be confused. If the file never had the video data written into it, the picture cannot be recovered from that file — but the original timeline and footage are usually still there, and a re-export can produce a file with a picture. If the file has a video track that a player cannot decode, the picture is in the file, and a different player or a transcode can show it. Do not write the file off until MediaInfo has been read.

What should I record before bringing the project in for inspection?

Record the format and codec of the finished file, the MediaInfo track list exactly as reported, the export settings including whether hardware or software encoding was used, the player comparison result, the software encoding comparison result, and the effect-by-effect comparison result. Bring the original finished file as well, together with any short test exports, and keep the original timeline and footage available. Then put it together as three sentences: what the symptom is, which variable made the symptom appear or disappear, and which possibilities are still not ruled out.

Sources

Related articles

Related services

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