Android — coming very soon Learn more
← All articles

Dolby Vision IPTV on Apple TV: play DV inside MKV

Most apps cannot decode Dolby Vision inside an MKV on Apple TV. Here is how OneTV Connect plays DV Profile 5 and 8 natively — and what to expect with Profile 7.

If you have ever tried to play a Dolby Vision movie stored in an MKV file on your Apple TV, you already know the pain: the picture comes up as flat SDR, the colors look washed out, or the file simply refuses to play. This is one of the trickiest problems in home streaming — and it's exactly what OneTV Connect solves natively. Here is what's really going on, and how the app gets Dolby Vision IPTV on Apple TV working without transcoding or quality loss.

Dolby Vision in MKV — and why it's hard on Apple TV

Dolby Vision is an HDR format that carries dynamic metadata, adjusting brightness and color scene by scene instead of using one static curve like HDR10. When a movie is ripped or downloaded, that Dolby Vision stream is usually wrapped in an MKV (Matroska) container, which is the format of choice for high-bitrate 4K rips.

The problem is that Apple's video stack — AVPlayer, the engine every tvOS app is built on — does not decode Dolby Vision when it's inside an MKV. Apple only exposes Dolby Vision playback through fragmented MP4 and HLS with a very specific codec declaration. So even though the Apple TV 4K hardware is perfectly capable of decoding the stream, the container gets in the way. That's why Dolby Vision MKV on Apple TV usually degrades to SDR or fails outright in most players.

How OneTV Connect makes it work

The trick is to change the wrapper without touching the video. OneTV Connect runs a custom remux pipeline that takes the MKV, extracts the HEVC video elementary stream, and repackages it into fragmented MP4 segments organized as an HLS playlist — all on the fly, with no transcoding. Because it's a remux and not a re-encode, the HEVC bitstream is preserved bit-for-bit: no banding, no artifacts, no quality loss.

Those fMP4 segments are served by a tiny HTTP server running on localhost inside the app itself. AVPlayer is then pointed at a http://127.0.0.1:PORT/master.m3u8 URL whose playlist declares the right codec string — for a Profile 8 stream that's SUPPLEMENTAL-CODECS="dvh1.08.06/db1p". That declaration is the missing key: it tells tvOS "this is Dolby Vision, decode it as such." From tap to first frame is typically one to two seconds, and seeking stays keyframe-accurate thanks to the HLS segment boundaries. Hardware decoding does all the heavy lifting.

Profile 5 vs 8 vs 7 — what plays, what falls back

Dolby Vision comes in several profiles, and being honest about which ones work matters more than a marketing checkmark:

  • Profile 5 — single-layer, with no HDR10 base. OneTV detects it from the stream metadata and configures the codec string to play DV Profile 5 on Apple TV natively. Full Dolby Vision output.
  • Profile 8 (8.1 / 8.4) — single-layer with a compatible HDR10 base layer. This is the most common profile in modern rips, and it plays natively in full Dolby Vision as well.
  • Profile 7 — dual-layer (a base layer plus an enhancement layer, common on Blu-ray remuxes). Apple TV cannot decode the enhancement layer, so there is no way to reconstruct true Dolby Vision from a Profile 7 file on tvOS. OneTV Connect handles it gracefully by falling back to HDR10, using the base layer and its static metadata. You still get a proper high dynamic range picture — just not the dynamic per-scene Dolby Vision metadata.

So in practice: Profiles 5 and 8 give you real Dolby Vision; Profile 7 gives you HDR10. That HDR10 fallback is the correct, standards-compliant behavior — the same limitation applies to every player on Apple TV, because it's an Apple hardware constraint, not an app one.

How the audio is handled

Video is only half the battle. High-bitrate rips often carry lossless audio tracks — TrueHD or DTS-HD — that don't pass through HLS on tvOS. Rather than dropping the sound, OneTV Connect applies a smart fallback: lossless codecs are handled so you keep audio and language selection, while the Dolby Vision video bitstream stays completely untouched. If a track is already HLS-compatible (E-AC-3, AC-3, AAC), it passes through directly. The goal is simple — you never lose the picture or the sound.

Tips for the best results

A few things help you get the cleanest Dolby Vision experience:

  • Use an Apple TV 4K. Any generation works for Dolby Vision output; Apple TV HD does not support it at all, regardless of the app. Pair it with a Dolby Vision TV and a high-speed HDMI cable.
  • Prefer Profile 5 or Profile 8 files. If you have a choice between a Profile 7 dual-layer remux and a Profile 8 encode of the same title, the Profile 8 version gives you full Dolby Vision on Apple TV.
  • Serve from a fast source. Whether the file lives on Plex, Jellyfin, Emby or a local download, the remux happens in the app — so a stable, high-bandwidth path to the file keeps startup and seeking snappy.
  • Check your TV's HDMI input. Dolby Vision needs HDMI 2.0a or later; an older port or a set to "Standard" HDMI mode can silently cap the signal.

That's the whole story: real Dolby Vision from your MKV library, on your Apple TV, in one app. The full technical breakdown lives on the Dolby Vision feature page, and you can read more about the underlying decoding on the 4K HEVC page and the Apple TV overview. If anything misbehaves, the support page has the full checklist. Ready to try it? Download OneTV Connect on the App Store.