All guides / Guide · Dolby Vision
Dolby Vision Profile 7 on Android TV: compatibility and conversion
A Dolby Vision label does not tell you everything about compatibility. The profile, container, TV box and display all participate in the result.
The profile matters
Profile 7 is the dual-layer Dolby Vision format associated with UHD Blu-ray. It carries a base video layer, an enhancement layer and dynamic metadata called the RPU. Many streaming boxes support single-layer Dolby Vision but cannot combine both Profile 7 layers.
Profile 8.1 uses a single video layer with an HDR10-compatible base. Profile 5 is another single-layer format, but its base is not a normal HDR10 fallback. Treating all Dolby Vision files alike can therefore produce very different results.
HDR10 is not inherently a broken picture
Some players show a Profile 7 file's HDR10 base without using its Dolby Vision metadata. That can be valid HDR10 playback. A dark or washed-out image can also involve display settings, an incorrect colour path or the source itself; appearance alone cannot identify the cause.
Check the signal reported by your display and the selected playback mode. Neither a filename nor a Dolby Vision badge verifies the entire picture pipeline.
What Sipario converts
On supported Android TV hardware, Sipario can convert confirmed Profile 7 sources to Profile 8.1 while streaming. The compressed base video is retained, the RPU metadata is rewritten and the enhancement layer is removed. No separate transcoding server or preprocessed copy is needed.
This is a compatibility tradeoff, not lossless preservation of the complete Profile 7 presentation. In particular, enhancement-layer picture information is not reconstructed. Supported Profile 5 and Profile 8 sources take the direct Dolby Vision route instead of this conversion.
The current Android TV behaviour
Sipario uses Media3 for its dedicated Dolby Vision path and mpv for non-Dolby Vision playback. A Dolby Vision failure is surfaced for retry or source selection; it is not silently switched to mpv's HDR10 base-layer output.
The primary verified device is onn 4K Plus. Other boxes, firmware versions, displays and receiver chains require their own checks. Conversion does not add Dolby Vision capability to unsupported hardware.
What still depends on your setup
- A compatible decoder and display, with appropriate HDMI settings.
- A source and container the selected playback path can handle.
- Enough source and network throughput for the video's bitrate.
- Correct aspect ratio, black levels and subtitle presentation on the physical display.
Common questions
Does Profile 7 conversion re-encode the video?
Sipario converts supported Profile 7 sources without decoding and re-encoding the base video. It rewrites Dolby Vision metadata and removes the enhancement layer. This avoids a video transcode, but does not preserve the full dual-layer presentation.
Is converted Profile 8.1 Dolby Vision?
It can be delivered as single-layer Dolby Vision to a compatible decoder and display. The enhancement layer is discarded rather than reconstructed. Hardware, container and source compatibility still matter.
Will conversion fix grey bars?
Not necessarily. Grey bars can involve the source, display settings or the device's video and overlay presentation. A Dolby Vision badge alone does not prove that aspect ratio, black levels and bars are correct. Report the device, app version and whether the issue occurs with controls visible or hidden; do not share private source credentials.