Why a 3D Blu-ray MKV Plays Flat on Vision Pro—and How to Fix the Playback Path

A 3D Blu-ray MKV can play as a flat 2D movie on Apple Vision Pro when the playback path reads only its standard video layer. Many Blu-ray 3D files use H.264 MVC, which contains a normal H.264 base view plus a second view for stereoscopic depth. If an app, server, or transcode process delivers only the base view, the movie still plays, but it has no visible depth.

Start by identifying the file's actual 3D structure. Then test it locally in Lumair. A local test separates file compatibility from server delivery, network conditions, and metadata detection.

Lumair can open compatible local files through Files, connect directly to SMB, and connect to a user's Jellyfin server. For compatible H.264 MVC video in MKV, Lumair decodes MVC and converts it on the device to stereo MV-HEVC for the visionOS system player. This is an on-device conversion path, not direct MVC playback and not a no-conversion MVC path.

Lumair plays compatible decrypted 2D and 3D Blu-ray ISO disc images but does not open BDMV folders, bypass DRM, or rip discs. 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.

Start With the File Structure, Not the MKV Extension

An MKV container can hold many types of video. The `.mkv` extension does not establish that a file is 3D, that it contains MVC, or that it will play correctly on a particular device.

Ordinary H.264 is 2D

Ordinary H.264, also called AVC, contains one video view. It can be stored in MKV, MP4, MOV, and other containers. A normal H.264 file plays as 2D because it has no second eye view.

A 3D title may also have an H.264 base layer that looks like ordinary 2D H.264 to software that does not inspect the MVC structure. That behavior is expected. The base layer is intended to remain decodable as a conventional video stream.

H.264 MVC contains the second view

H.264 MVC, or Multiview Video Coding, adds a dependent view to the H.264 base video. Together, the views provide the left and right eye images needed for stereoscopic presentation.

A compatible H.264 MVC MKV requires a playback path that can:

1. Detect the MVC structure.
2. Read both views.
3. Decode the multiview video.
4. Prepare compatible stereo MV-HEVC on the device for the visionOS system player.

Apple documents MV-HEVC as the multiview format used for spatial video workflows in its media frameworks. Apple’s AVFoundation documentation also describes conversion of supported stereoscopic inputs into multiview HEVC and spatial video.

Lumair performs its compatible MVC-to-stereo-MV-HEVC conversion locally on Vision Pro. The source MVC file remains the source file; Lumair prepares a playback representation for the system player.

File size and codec labels do not prove compatibility

Do not use file size, bitrate, a codec name, container, or extension as a guarantee of playback. Two MKV files can both report H.264 video while one contains MVC and the other contains only a 2D stream. A title can also have unusual track structures, damaged timing data, unsupported audio, or metadata that does not describe the stream accurately.

Check the actual video stream information when possible. Then use the local-file test below. Playback is the practical compatibility check.

Do Not Confuse MVC With Side-by-Side or Over-Under

A file that looks flat may not be MVC at all. It may use a packed layout that needs a different presentation setting.

Side-by-side video

Side-by-side, often abbreviated SBS, stores both eye views in one frame. The left and right images sit next to each other. An unconfigured player may show two narrow pictures instead of a single stereoscopic image.

Use the side-by-side layout only when the source is genuinely side-by-side. Selecting SBS for an MVC file does not restore a missing MVC view.

Over-under video

Over-under, also called top-and-bottom, stores one eye view above the other in the same frame. A player must split the frame vertically and assign each section to the correct eye.

If an over-under file uses the wrong presentation mode, it can appear as stacked images, reduced resolution, incorrect depth, or a flat image.

MVC is not a packed layout

MVC stores the additional view as part of a multiview H.264 structure. It does not place two complete images side-by-side or top-and-bottom in each decoded frame.

Use this quick distinction:

If the image shows two views at once, inspect the source for SBS or over-under before treating it as an MVC problem. If the movie looks like a normal flat 2D presentation, the file may be ordinary H.264, an MVC file detected only as its base layer, or a server-transcoded version of the original.

Check Metadata and Detection Before Changing Playback Settings

A media library can label a title as “3D” based on a filename, folder name, library field, or manually entered tag. That label does not prove the video stream contains MVC or that the client can use it.

Metadata can also be incomplete. A server may identify the base H.264 stream without exposing the dependent MVC view in a way a client expects. The player then receives or selects a 2D-compatible interpretation of the file.

Use metadata as a clue, not a verdict. Check these points:

• Confirm whether the file is H.264 MVC, SBS, over-under, MV-HEVC, or ordinary 2D video.
• Confirm that the item selected in the media library is the intended source version.
• Confirm that the server is sending the original video rather than a converted output.
• Test the same source file locally through Files.

A filename such as `Movie.3D.MVC.mkv` can be useful for library organization, but it does not change the encoded stream.

Fix the Jellyfin Playback Path

Lumair connects to a user's Jellyfin server. Jellyfin’s own documentation explains that client codec support and server transcoding affect what a client receives. See Jellyfin’s codec support documentation and transcoding documentation.

For MVC troubleshooting, the important distinction is between video transcoding and Lumair’s authenticated byte-range delivery path.

Video transcoding can remove the MVC result

When Jellyfin transcodes video, it creates a new output stream for the client. A transcode path that produces a conventional single-view video loses the MVC presentation needed for stereo playback. The result can look like a successful movie playback because the H.264 base view remains watchable as 2D.

The server may choose a transcode because of codec support, bitrate restrictions, subtitle processing, audio handling, network conditions, or client capability reporting. Check the Jellyfin session and playback details while the title plays. If Jellyfin reports video transcoding, treat that as a likely cause of flat playback.

Avoid assuming that “Direct Play” labels alone settle every MVC issue. The useful test is whether Lumair receives the selected original source through its compatible playback path and whether the same file works locally.

Lumair uses an authenticated MVC byte-range path

For compatible MVC playback from Jellyfin, Lumair uses an authenticated byte-range path to access the selected source file. Byte-range requests let the app request portions of the original file, including the portions needed for seeking, without asking Jellyfin to create a replacement video transcode.

The authentication matters because the request still uses the user's Jellyfin connection and account permissions. This byte-range path is specific to Jellyfin. Direct SMB is a separate supported source for browsing, streaming, and downloads from a compatible server on the local network.

If a compatible MVC MKV works as a local file but plays flat through Jellyfin, review the server session first. Look for video transcoding, a different selected version, or a source-specific metadata issue. Also confirm that Lumair is connecting to the expected Jellyfin library and item.

Use a Local File to Isolate the Problem

The local-file test is the fastest way to identify whether the problem comes from the file or the server path.

Vision Pro can access files through the Files app. Apple describes file access and organization in its Vision Pro Files guide.

Follow this sequence:

1. Make the original MKV available in Files on Vision Pro.
2. Open that local file in Lumair.
3. Start playback and check for stereoscopic depth.
4. Test the same source through direct SMB or Jellyfin only after the local result is known.

If the local file plays with correct depth, the source is a compatible candidate and the issue is likely in server delivery, source selection, metadata, or network behavior.

If the local file plays flat, inspect the file structure again. It may be ordinary H.264, a file whose MVC data is absent or unsupported, or a packed-layout source that needs SBS or over-under presentation.

If the local file fails to open, that result can involve the video stream, audio tracks, file integrity, available storage, or another file-specific limit. It does not prove that all MKV files or all 3D files will fail.

Lumair can open compatible local files through Files. 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.

Test Downloads Before Travel

Lumair can download compatible video from an SMB server or a selected original source file from a connected Jellyfin server to app-managed storage for offline playback. SMB downloads retain the source information needed for retry and playback. Jellyfin downloads remain unchanged from the selected source. Embedded video, audio, and subtitle tracks remain in the downloaded file.

Separate external subtitle files are not bundled into SMB or Jellyfin downloads. If a server item depends on an external subtitle file, test the downloaded result before travel.

Apple’s Travel Mode documentation covers using Vision Pro while traveling. Before you leave, play the downloaded item from the device and confirm the video, stereo presentation, selected audio, and subtitles work as expected.

Do not assume a successful server stream guarantees an offline result. Test the exact download.

HDR, Dolby Vision, Audio, and Subtitle Limits

H.264 MVC Blu-ray sources and HEVC HDR files follow different playback paths.

Compatible MP4, MOV, and M4V files that AVFoundation handles use native playback in Lumair. For compatible HEVC MKV files, Lumair remuxes the file while preserving the original HEVC base video. Lumair may prepare Dolby Vision when that is safe. When it is not safe, Lumair uses the source HDR10 base layer.

That behavior does not promise support for every Dolby Vision profile, HEVC file, audio format, subtitle format, or MKV structure. Test each title.

For MVC files, treat HDR handling as a separate question from 3D detection. A title can have correct stereoscopic depth while a particular audio track, subtitle track, or HDR treatment needs a different selection or is unavailable.

A Short Troubleshooting Checklist

Use this order when a 3D Blu-ray MKV plays flat:

1. Identify the source as MVC, SBS, over-under, MV-HEVC, or ordinary H.264.
2. Do not infer MVC from the MKV extension or a “3D” library label.
3. Use SBS or over-under presentation only for a packed-layout source.
4. Open the same original file locally through Files in Lumair.
5. If local playback works, inspect the SMB path or Jellyfin for delivery and source-selection problems.
6. For Jellyfin, confirm the selected compatible MVC source is using Lumair’s authenticated byte-range path.
7. Download the selected original source for offline use and test it before travel.
8. Check audio, subtitle, HDR, and Dolby Vision behavior separately from 3D depth.

Lumair includes no media. Users are responsible for obtaining and using media they have the rights to view. Lumair is not affiliated with Jellyfin.

Lumair includes a 5-minute playback preview for every video. Full Playback is a one-time $14.99 US purchase. App Store pricing can vary by storefront.

Download Lumair free on the App Store.