HDR10, Dolby Vision, and MV-HEVC on Vision Pro

Apple Vision Pro playback depends on the video stream, HDR format, container, and stereo structure inside a file. A filename and extension can identify a container, but they do not confirm that a title will play or determine whether it will display in HDR10, Dolby Vision, or stereo.

Lumair gives compatible files several paths on Vision Pro:

• Compatible MP4, MOV, and M4V files use native playback when AVFoundation can handle them.
• Compatible HEVC video in MKV uses a remux path that preserves the original HEVC base video.
• Dolby Vision files receive conservative preparation when the source structure is safe for that path. When preparation is not safe and a compatible HDR10 base layer exists, Lumair uses that base layer.
• Compatible H.264 MVC video in MKV is decoded and converted on the device to stereo MV-HEVC for the visionOS system player.
• Existing MV-HEVC stereo video follows the system playback path.

These are format-specific paths. Lumair does not treat every file with an MKV extension, an HEVC codec label, or a Dolby Vision filename as interchangeable. Test the exact file you plan to watch.

The formats Vision Pro uses

Apple Vision Pro supports high dynamic range video and spatial video capabilities through Apple’s media frameworks and system playback tools. Apple lists support for HDR video formats including HDR10 and Dolby Vision in Vision Pro specifications. Apple Vision Pro technical specifications describe the device’s display and video capabilities, but an app still needs a compatible source file and playback route.

A few terms make the differences clearer:

• Codec: The method used to compress video, such as H.264 or HEVC.
• Container: The file wrapper, such as MP4, MOV, M4V, or MKV.
• HDR format: The metadata and color system used for high dynamic range video, including HDR10 and Dolby Vision.
• Stereo format: The way a 3D title stores left-eye and right-eye views.

An `.mkv` file can contain HEVC HDR video, H.264 MVC Blu-ray 3D video, a standard 2D stream, or another combination of tracks. An `.mp4` file can also vary widely. File extensions are useful for choosing an import path, but they do not guarantee codec, HDR, audio, subtitle, or profile compatibility.

Native MP4, MOV, and M4V playback

Lumair can open compatible local files through the Files app on Vision Pro. Apple’s Files documentation explains how visionOS users view, organize, and open files stored locally or available through supported file locations. Use Files on Apple Vision Pro covers the system file workflow that Lumair uses for local imports.

For compatible MP4, MOV, and M4V files, Lumair uses native playback through AVFoundation. This route is appropriate when the system media stack can open the video, audio, and metadata in the file.

A compatible native file may include:

• Standard 2D H.264 or HEVC video.
• HDR10 video that AVFoundation recognizes.
• Dolby Vision video with a compatible structure.
• MV-HEVC stereo video where the system can use the multiview track.
• Audio and subtitle tracks that the selected playback route can handle.

Compatibility still depends on the complete file. Codec name, bitrate, file size, and extension each describe only one part of the source. A large MOV file may play normally, while a smaller MP4 may fail because of an unsupported stream profile, an unusual track arrangement, damaged file data, or metadata that the system does not accept.

Open the file in Lumair and test the section you intend to watch. That test is more useful than relying on labels such as “4K,” “HDR,” “Dolby Vision,” or “REMUX” in the filename.

HEVC MKV files and the base-video remux path

MKV is a container rather than a video codec. Many movie libraries use MKV because one file can hold video, several audio tracks, chapters, subtitles, and other metadata. VisionOS system playback does not make MKV support universal, so Lumair handles compatible HEVC MKV files through a remux path.

For a compatible HEVC MKV source, Lumair remuxes the media for playback while preserving the original HEVC base video. The video does not go through a picture re-encode in that path. The HEVC base layer remains the video foundation used for playback.

That distinction matters for HDR sources. HDR10 is carried by the HEVC video and its static metadata. Dolby Vision can add dynamic metadata and, depending on the file, other profile-specific components. Lumair’s preparation step evaluates whether the Dolby Vision arrangement is safe for the supported route.

A compatible HEVC MKV file can therefore take one of two HDR paths:

1. Dolby Vision preparation: Lumair prepares Dolby Vision when the source profile and metadata arrangement fit the supported workflow.
2. HDR10 fallback: Lumair uses the source HDR10 base layer when Dolby Vision preparation is not appropriate for the file.

HDR10 fallback is an expected result for some Dolby Vision sources. It does not identify a damaged file, and it does not mean Lumair converts the HEVC base video into SDR. The source’s HDR10 base layer provides the fallback image when it is available and compatible.

Do not assume every Dolby Vision profile, enhancement layer, metadata arrangement, or MKV source will retain Dolby Vision output. Dolby Vision files vary by profile and by the way their layers and metadata are stored. Lumair takes a conservative approach because retaining a reliable HDR10 base layer is preferable to making a broad promise about profile coverage.

Apple’s media documentation also separates format specifications from app-level behavior. The HLS Authoring Specification for Apple devices describes supported delivery formats for Apple playback environments. It does not make every locally acquired file playable in every app.

HDR10 and Dolby Vision: what to expect

HDR10 uses static metadata. The mastering information applies across the program or title. Dolby Vision can use dynamic metadata that changes scene by scene or frame by frame, depending on the source.

Lumair supports compatible HDR10 media and provides a Dolby Vision preparation path for compatible files. The result depends on the source itself.

Check these details before planning a long offline viewing session:

• The video codec and profile.
• Whether the HDR format is HDR10 or Dolby Vision.
• The Dolby Vision profile and the arrangement of its metadata and layers.
• The container holding the video.
• The audio and subtitle tracks.
• The integrity of the file after transfer or download.

A file marked “Dolby Vision” can contain different profile structures. A file with the same title in another release may have a different base layer, metadata arrangement, or container. Lumair cannot determine compatibility from a filename label alone.

Lumair does not claim HDR10+ support. It also does not claim universal Dolby Vision profile coverage. If a Dolby Vision source cannot use Lumair’s supported preparation route, the compatible HDR10 base layer is the intended fallback path.

MV-HEVC stereo on Vision Pro

MV-HEVC, short for Multiview High Efficiency Video Coding, stores stereo video as a multiview HEVC stream. It carries left-eye and right-eye image data in a form intended for stereoscopic presentation.

Apple documents workflows for creating and converting stereo video to multiview HEVC. Its AVFoundation guidance for converting side-by-side 3D video to multiview HEVC and spatial video explains the format’s use for stereo content and Apple platform playback.

When a source is already compatible MV-HEVC, Lumair uses the visionOS system player path. The source does not need Lumair’s MVC conversion workflow because it already uses a multiview HEVC structure.

MV-HEVC differs from side-by-side and over-under 3D video:

• MV-HEVC stores separate multiview image data in a multiview HEVC track.
• Side-by-side places both eye views next to each other in one video frame.
• Over-under places one eye view above the other in one video frame.

Each source needs the matching presentation method. Selecting a stereo layout does not turn an unrelated 2D file into MV-HEVC, and an MV-HEVC label does not prove that a file will open correctly. Test the actual title in Lumair.

Apple also provides system controls for watching shows and movies in visionOS. See Play shows and movies on Apple Vision Pro for the system viewing environment.

H.264 MVC in MKV: Lumair’s conversion path

H.264 MVC is an older multiview codec commonly associated with Blu-ray 3D sources. It is not MV-HEVC.

Lumair supports compatible H.264 MVC video in MKV by decoding the MVC video and converting it on the device to stereo MV-HEVC for the visionOS system player. This is a conversion path. It is not direct MVC playback, and it is not no-conversion MVC playback.

The source needs to meet the requirements of that path:

• The video must be compatible H.264 MVC.
• The source must be in an MKV container.
• The file must be readable and intact.
• Its other tracks must not prevent the selected playback route from opening it.

Lumair plays compatible decrypted 2D and 3D Blu-ray ISO disc images but does not open BDMV folders, bypass DRM, or rip discs. A compatible decrypted Blu-ray 3D ISO can use Lumair’s disc-image playback path, while BDMV folders remain unsupported.

If you have a compatible MVC MKV, Lumair performs the necessary on-device conversion for stereo playback. Open a compatible decrypted Blu-ray ISO directly. For a protected source or unsupported folder structure, prepare another compatible file through a lawful workflow.

Local files, Jellyfin, and downloads

Lumair can open compatible local files through Files, connect directly to SMB, and connect to a user’s Jellyfin server. Lumair is not affiliated with Jellyfin.

Jellyfin’s own documentation explains that playback behavior can vary with client capabilities, codecs, containers, and server transcoding settings. Review Jellyfin codec support and Jellyfin transcoding documentation when configuring a personal server.

Lumair can browse, stream, and download compatible video directly from SMB servers on the local network. It does not claim NFS, DLNA, WebDAV, Plex, or Emby support. It also does not provide disc ripping or DRM bypass.

When you download a title from Jellyfin in Lumair, Lumair saves the selected original source file unchanged to app-managed storage. Embedded tracks remain in that saved file. Separate external subtitle files are not bundled with the download.

That behavior has practical consequences for travel:

• Select the intended source version before downloading.
• Confirm that embedded audio and subtitle tracks meet your needs.
• Do not expect a separate `.srt`, `.ass`, or other external subtitle file to travel with the downloaded source.
• Test the downloaded file in Lumair before leaving home.

Apple’s Travel Mode guidance for Apple Vision Pro covers use of the headset while traveling. It does not confirm that a particular downloaded media file will play. Test playback after the download completes and before your trip.

A practical file check

Use this sequence for a title you want to watch on Vision Pro:

1. Identify the container: MP4, MOV, M4V, or MKV.
2. Identify the video codec: H.264, H.264 MVC, HEVC, or MV-HEVC.
3. Check whether the title is 2D, side-by-side, over-under, MVC, or MV-HEVC.
4. Check whether its HDR format is HDR10 or Dolby Vision.
5. For Dolby Vision, expect the supported preparation route or HDR10 base-layer fallback.
6. Import a compatible local file through Files, or select it from your Jellyfin server.
7. Test the saved download before travel.

Lumair includes no media. Users are responsible for having the rights to access, copy, download, and watch their own files.

Lumair provides 5 playback minutes per video as a preview. Full Playback is a $14.99 US one-time purchase. App Store pricing can vary by storefront.

Download Lumair free on the App Store.