Adding codec support to a Windows signage player

What a codec pack is, and what 8K is not

A codec is the software that turns a compressed video file back into frames. Windows ships with a set of decoders, and a codec pack is a bundle of extra decoders installed so that more file types open.

8K is not a codec. It is a frame size: 8K UHD is 7680 x 4320 pixels, four times the pixels of 3840 x 2160 and sixteen times 1920 x 1080. The codec inside an 8K file is usually HEVC or AV1. So when you ask whether a codec pack will make the player take "the latest codec, like 8K", two separate things must work at once: the decoder for the codec, and the render path for the frame size. A pack addresses the first. It does nothing for the second.

Two decode paths in Windows

DirectShow is the older framework. Its decoders install as filters registered with Windows, and every application that decodes through DirectShow sees every registered filter. That is the whole reason a codec pack propagates: install it once and any DirectShow-based signage player inherits the new decoders.

Media Foundation is the newer framework. Microsoft's own Windows documentation points new development at Media Foundation and keeps DirectShow for older software. A player that renders through Media Foundation decodes with Windows' own decoders plus optional codec extensions from the store; it never consults DirectShow filters. The payoff was stated plainly by the maintainer of one open-source Windows video renderer when asked to switch it to Media Foundation: one package that plays video without telling the end user to install codec packs.

So the answer to "will the pack reach my player" depends on a fact about the player, not about the pack.

Tell the two paths apart with a 10-second test clip

Encode one short file and watch where it plays:

1. Encode a 10-second clip in the codec you actually need, for example AV1 at 1920 x 1080.
2. Play it in the signage player, exactly as the machine stands now.
3. If it plays, the decoder was already present. No pack and no extension needed.
4. If it fails in the signage player and in a plain desktop player too, suspect the encode first and re-encode before touching codecs. USB video playback troubleshooting for signage displays covers the failures that look like codec problems.
5. If it fails in the signage player alone, install the codec pack on a bench machine, not on the screen that plays for customers, and play the clip again.
6. If the pack fixes the clip, your player decodes through DirectShow and the pack reaches it. If nothing changes, the player is built on Media Foundation: uninstall the pack and install the store codec extension for that codec instead.

The result of that one test decides everything else on this page.

Why 8K needs more than a decoder

A decoded frame still has to reach the panel. Three gates sit between the file and the screen:

• Decode. At 8K the decoder needs the graphics chip to share the work. A graphics chip with no accelerated decoding for HEVC or AV1 at that frame size pushes the work to the CPU, the frame budget is missed and playback drops frames.
• Output. HDMI 2.0 carries 18 Gbps, enough for 3840 x 2160 at 60 Hz. 8K at 60 Hz needs HDMI 2.1 and its 48 Gbps. An output that stops at 4K shows the 8K file downscaled: it plays, and you paid an 8K decode bill for a 4K picture.
• Screen. The panel itself. On a 1920 x 1080 panel, the numbers in the example below decide.

The render gate is not Windows-specific. Android players meet the same wall in another form: a player that only renders at 1080p cannot show a 4K file at full size, whatever the decoder does.

Example: an 8K file on a 1920 x 1080 player

Inputs. The file is HEVC at 7680 x 4320 (8K UHD) at 30 fps: the frame size the codec question is about, at a typical signage loop rate. The player outputs 1920 x 1080 at 60 Hz, the most common signage panel size.

Rule. Decode throughput in pixels per second equals frame width x frame height x frame rate.

Arithmetic:

• 7680 x 4320 = 33,177,600 pixels per frame.
• 33,177,600 x 30 = 995,328,000 pixels per second, about 995 million.
• The 1080p loop for comparison: 1920 x 1080 = 2,073,600 pixels, and 2,073,600 x 60 = 124,416,000 pixels per second.
• 995,328,000 / 124,416,000 = 8.

Result. The 8K file asks the decode path for about 1 billion pixels per second, eight times the throughput of the clip this hardware was sized for.

Decision. 33,177,600 / 2,073,600 = 16, so the screen keeps one of every sixteen decoded pixels and fifteen in sixteen are thrown away. Where the screen has fewer pixels than the file, a codec pack buys nothing: re-encode the file at 1920 x 1080 and the decode load falls with the pixels; exporting slides to video for an offline signage player shows the export step. Only a screen that is genuinely 7680 x 4320 justifies the full chain of codec, accelerated decoding in the graphics chip and a 48 Gbps output.

What a codec pack can break

A DirectShow filter registers for the whole machine. Every DirectShow application on that box reads the same filter list, so one bad decoder in a pack can take playback down in every application at once, not only in the signage player. That is why codec installs belong on a bench first, the same test-before-you-deploy rule as video bitrate for signage players.

Three habits:

• One pack per machine. Packs overlap, and when two of them claim the same file type you lose track of which decoder handled a file that plays.
• Set a restore point before the install, so undoing it is one step.
• After the install, play the whole playlist on the bench, every video and every resolution you use, before the machine goes back on the wall.

The decision, case by case

• The test clip fails in the player alone and a store codec extension exists for that codec: install the extension. The player is Media Foundation-based, and this is the fix that fits it. The AV1 Video Extension in the Windows store is the pattern: one extension adds decoding for one codec to the video apps on the machine.
• The extension changes nothing and the pack fixes the clip: the player is DirectShow-based. Keep the pack, but only after the bench run through the whole playlist.
• The panel is 1920 x 1080: skip both. Re-encode at the panel size; the codec work buys a picture the panel cannot show.
• The panel is really 7680 x 4320: all three gates must pass, codec first, then accelerated decoding in the graphics chip, then the 48 Gbps output. Any gate that fails means downconverting the file to what the chain carries.

If you would rather not manage codecs at all, this is where an offline player earns its keep: our panel-mount players take H.264 MP4 straight from microSD or USB with no subscription, so the codec question is settled at export time. If you are still choosing the hardware itself, the guide to choosing a digital signage player covers what to check before you buy.

Recommendation: run the 10-second test clip before you install anything. If a store extension plays it, use the extension. If only a codec pack plays it, prove the pack on a bench machine through the whole playlist before it goes near a live screen. And if the screen is 1920 x 1080, re-encode the file instead: at sixteen times the pixels the screen can show, no codec pack improves the picture.

Questions