4K and HDR live TV on Xbox Series X: what to expect

A Series X will play a 4K live channel. That is the first thing to say, because the rest of this article is about what it will not do, and those gaps are easy to mistake for a fault.

The short shape: 4K decodes and plays. HDR is tone-mapped to SDR. Dolby and DTS bitstream passthrough is unavailable. AV1 falls back to software. All four follow from one fact: the console app links a different native player library from the Windows app.

Two builds of the same library#

The desktop head loads libvlc 3.0.23. The console head links a UWP build made from libvlc 3.0.16 with the app-container plugin set, which is what a Store app on a console is allowed to ship.

What each head may ask for, side by side:

switch                     desktop            console
--------------------------------------------------------------
--avcodec-hw=...           yes                yes
--avcodec-threads=3        no                 yes (memory cap)
--mmdevice-passthrough=N   yes (primary)      no (no mmdevice plugin)
--d3d11-hdr-mode=...       yes (10-bit only)  no (plugin too old)

The two builds do not carry the same modules, and we cannot route around that in our own code. Hand libvlc an option from a module the build lacks and it does not degrade. It fails the whole instance. The console had already been broken once this way, by a prefetch buffer switch. So the switches are decided in one place, per head, and the console gets the subset its build can honour. 63 tests hold that line, asserting that every head, role and surface-depth combination emits only allow-listed switches and that the console never sees the two it cannot support.

HDR#

Not on the console today. Its Direct3D11 plugin predates the HDR mode switch, so there is nothing to turn on. The surface stays 8-bit and VLC tone-maps an HDR stream down to SDR before you see it.

An HDR channel plays, and looks like a competent SDR conversion of itself. Not wrong. Flatter than the same stream on a Windows machine with an HDR display.

On the desktop this took an app-owned swapchain, and the reason explains why it is not a small port. The stock video control builds its swapchain as 8-bit BGRA, and DXGI refuses an HDR10 colour space on an 8-bit buffer, so negotiation could only ever land on sRGB whatever the stream carried. Owning the swapchain was the only lever. Doing the same on the console needs a newer UWP libvlc build from upstream.

We got this wrong on the first cut, in a way only the running app showed. Asking for 10 bits unconditionally changes how the compositor treats the video plane: the translucent player chrome composited lighter, and the transport controls started ghosting through the video. So the desktop now asks for 10 bits only when the display it sits on reports an HDR colour space, and any probe failure answers SDR, because SDR is the answer that cannot regress anything.

Audio#

Passthrough is off on the console, for two independent reasons. The UWP libvlc build ships no mmdevice plugin at all, so the switch has nothing to talk to. Separately, Xbox does not let third-party apps bitstream audio in the first place.

Either alone would settle it. Console audio is decoded to PCM and sent to the TV or receiver that way. Fine for stereo and most surround; not what you want if you bought a receiver to decode the bitstream itself. Even on the desktop, passthrough is restricted to the primary player, because it opens the audio device in exclusive mode and a standby or mosaic tile asking for the same endpoint would fail its audio outright.

The settings cards for HDR and passthrough are hidden on the console rather than shown disabled. A control that cannot do anything is worse than no control.

Codecs, and the one that bites#

H.264 and HEVC are the normal cases and both are fine. AV1 is the one to know about: the console build's FFmpeg carries no AV1 hardware decoder, so a stream a recent Windows GPU handles without effort falls back to software on the console.

Software-decoding 4K is expensive, and this is where the memory budget shows up. The console caps frame-decoding threads at 3, and the number is not arbitrary. Left to choose for itself, the decoder picked 6 on the measurement machine, which produced a 40-surface Direct3D11 output pool at 4K: roughly 500 MB of GPU-visible commit against an Xbox budget of 1 GB. Capping at 3 keeps that in bounds. Hardware decode does not use those threads, so the cap costs nothing on the paths that matter.

The practical version: if a channel stutters on the console and plays cleanly on Windows, check the codec before your connection. Why some channels work on Windows but not on Xbox is the walkthrough, and H.264 versus HEVC versus AV1 explains what the difference costs.

What good looks like#

For reference, the desktop numbers from the same verification pass: 4K live plays, 4K on-demand plays with the GPU decode engines at about 11 percent where it used to be software-only, and a full pass covering cold start, fullscreen and picture-in-picture logged 0 errors.

The console does not reach all of that today, and the gap is upstream rather than in our code. What it does well is the thing most people bought it for: a 4K live channel on a big screen, driven from the sofa, with no PC in the room. Turning an Xbox into a living-room TV hub is the setup for that.