Guide · Dolby Vision
Dolby Vision Profile 7 on Android TV: why disc remuxes play flat, and the fix
You have a 4K remux with Dolby Vision. Your TV does Dolby Vision. Your box does Dolby Vision. You press play and the picture looks flat, dim, or just ordinary — and the TV never lights up its Dolby Vision badge. Nothing is broken. You are watching the base layer.
Two kinds of Dolby Vision
Dolby Vision comes in several profiles, and the difference matters more than the shared name suggests. The ones you meet in practice are:
- Profile 5 — single layer, used by streaming services. One video stream plus the RPU metadata that drives dynamic tone mapping.
- Profile 8.1 — single layer with an HDR10-compatible base. Plays as Dolby Vision on gear that understands it, and degrades gracefully to HDR10 on gear that doesn't.
- Profile 7 — dual layer. A base layer, a separate enhancement layer, and the RPU. This is what UHD Blu-ray uses, so it is what disc remuxes carry.
Profile 7 exists because Blu-ray players are built to combine two layers in hardware. Streaming boxes are not. Almost every Android TV device on the market decodes the single-layer profiles and has no route for the second layer at all.
What actually happens when you press play
Faced with a Profile 7 file, a player has three options, and none of them is good. It can refuse the file outright. It can hand the whole thing to a decoder that produces a broken picture. Or — most commonly, and most confusingly — it can quietly play the base layer and drop the rest.
That third case is the one that sends people looking for answers, because nothing announces itself as wrong. You get valid HDR10. The film plays start to finish. But the dynamic per-scene metadata that makes Dolby Vision worth having never reaches the TV, so dark scenes sit murky and bright ones look muted. Your TV shows an HDR10 badge, or no badge, and you are left wondering whether the file is bad.
If a Dolby Vision remux plays but looks disappointing, suspect the profile before you suspect the file.
The conversion nobody should have to do by hand
Profile 7 can be turned into Profile 8.1 losslessly. The enhancement layer is discarded, the RPU is rewritten so a single-layer decoder understands it, and the actual video bitstream is left completely untouched. There is no re-encode, so there is no generational loss and no overnight transcode.
On the desktop this is well-trodden ground: dovi_tool and friends will do it to a file, and the enthusiast forums are full of step-by-step threads. It works. It also means keeping a computer in the loop, processing every title before you can watch it, and storing a second copy of a file that was already 80 GB.
The obvious question is why the player can't just do this while the film plays. It can.
How Sipario handles it
Sipario performs the Profile 7 to 8.1 conversion on the box, in real time, as the file streams. The enhancement layer is dropped and the metadata rewritten on the fly; the video bitstream passes through untouched. Your TV receives genuine single-layer Dolby Vision and displays it as Dolby Vision, from the original file, with no pre- processing step and no second copy on disk.
It also knows when not to do any of this. A title that is already single-layer Profile 8 needs no conversion, so Sipario detects the profile from the container and plays those files directly — full seeking, no transformation in the path. The conversion only engages for the files that actually need it.
The work is verified on the hardware rather than assumed: the reference device is the $20 onn 4K Plus, where playback is checked frame by frame against the display's own presentation clock, including matching the display to 23.976 Hz before the decoder opens so 24p material runs at its native cadence.
Honest limits
Conversion needs a box whose hardware decodes Dolby Vision in the first place — this makes Profile 7 files playable as Dolby Vision on such hardware, it does not add Dolby Vision to a device that lacks it. The enhancement layer is genuinely discarded rather than merged, which is the same trade the desktop tools make and is inaudible-to-invisible in practice next to the gain of working dynamic metadata. And a high-bitrate remux still needs the bandwidth to stream: conversion is metadata work, not compression.
Common questions
What is Dolby Vision Profile 7?
Profile 7 is the dual-layer form of Dolby Vision used on UHD Blu-ray. It ships a base layer, a second enhancement layer, and the RPU metadata that drives the dynamic tone mapping. Streaming services never use it — they use single-layer Profile 5 or 8 — so it turns up almost exclusively in disc remuxes.
Why does my Profile 7 file look flat or dark on Android TV?
Because the box is showing you only the base layer. Nearly every Android TV device decodes single-layer Dolby Vision (Profile 5, 8, sometimes 9) and has no path for Profile 7's second layer, so the player falls back to the HDR10 base and the Dolby Vision dynamic metadata never reaches your TV. The picture is technically correct HDR10, which is why it looks washed out or dim rather than obviously broken.
Do I have to re-encode the video to fix it?
No. Profile 7 can be converted to Profile 8.1 by rewriting the metadata layer and discarding the enhancement layer. The video bitstream itself is never touched, so there is no quality loss and no hours-long encode. Desktop tools like dovi_tool do this to a file; Sipario does it to the stream as it plays.
Is converted Profile 8.1 real Dolby Vision?
Yes. Profile 8.1 is single-layer Dolby Vision with an HDR10-compatible base and the RPU intact, and your TV receives and displays it as Dolby Vision. What you lose is the enhancement layer, whose real-world contribution is small compared with getting dynamic metadata working at all.