How NAS and Media Servers Stream Split VOB Files

This article examines how modern Network Attached Storage (NAS) devices and media servers process, stream, and transcode legacy split VOB (Video Object) directories. It breaks down the challenges posed by traditional VIDEO_TS structures, contrasts file-share streaming with dedicated media server parsing, explains how software handles buffer transitions across split files, and highlights why container remuxing remains the industry-standard workaround.

The Challenge of the Split VOB Format

The DVD-Video standard restricts file sizes to a maximum of 1 GB (1,048,576 KB) to maintain compatibility with legacy file systems such as FAT16 and FAT32. As a result, a single feature film is segmented across multiple files (such as VTS_01_1.VOB, VTS_01_2.VOB, and VTS_01_3.VOB). Crucial navigation, chapter markers, audio sync offsets, and aspect ratio flags are not stored inside the VOB files themselves, but inside accompanying .IFO (Information) files.

Streaming this format requires the server or playback client to parse the entire directory structure, interpret the .IFO file, and seamlessly chain the separate 1 GB segments without introducing audio gaps or visual stutter.

File-Level Sharing vs. Media Server Processing

How split VOB files are handled depends fundamentally on whether the NAS acts as a passive storage provider or an active media server:

• Passive Network Shares (SMB, NFS, WebDAV): When streaming directly from a NAS using standard network protocols, the NAS does not process the files. Instead, it serves the raw byte streams to client-side players (such as Kodi, VLC, or Infuse). Advanced players read the VIDEO_TS.IFO file directly over the network, reconstruct the playlist, and pre-buffer subsequent VOB files into local RAM, achieving continuous playback with full DVD menu support.
• Dedicated Media Servers (Plex, Emby, Jellyfin): Modern streaming platforms prioritize modern single-file containers (MP4, MKV) and streamable transport formats (HLS, DASH). Because split VOB architectures clash with these protocols, each platform handles them differently:
  • Plex: Officially discontinued support for VIDEO_TS folders and ISO disc images. Plex treats each .VOB file as an independent video track or ignores the directory altogether, leading to broken playback, missing durations, and unsynced audio.
  • Emby and Jellyfin: Maintain limited legacy support for DVD folder structures. They scan the directory, attempt to parse the primary movie title via the .IFO file, and assemble the split VOB segments into a single virtual timeline for the user.

Transcoding and Buffer Stitching Mechanics

When a media server streams split VOBs to a client that cannot natively decode MPEG-2 video or AC-3/DTS audio, it must transcode the content in real time. This process introduces significant technical hurdles:

1. FFmpeg Concatenation: Media servers rely on backend libraries like FFmpeg to process files. To handle split VOBs, the server uses a concatenation protocol (concat:) to treat sequential segments as an unbroken stream.
2. Timestamp Discontinuities: Because each VOB split can contain non-continuous Presentation Time Stamps (PTS) and Program Clock References (PCR), the transcoder must dynamically realign timestamps at segment boundaries. A failure to normalize these timestamps causes audio-video desynchronization.
3. Seamless Buffer Swapping: During direct play, the server must look ahead and stream the opening packets of the next VOB chunk before the preceding chunk finishes playing. If the read buffer drops, playback stutters at the exact 1 GB boundary point.

The Industry Solution: Remuxing to MKV

Because native streaming of raw VIDEO_TS directories remains resource-intensive and prone to boundary glitches, modern workflows avoid streaming raw VOB structures. Instead, users routinely remux split VOB sets into a single Matroska (MKV) container using tools like MakeMKV.

Remuxing does not re-encode or compress the original audio and video data; it extracts the underlying MPEG-2 video, audio streams, and subtitle tracks from the split VOB files and places them into a single, unified MKV file. This process completes in minutes, preserves 100% of the original quality, resolves all timestamp discontinuity issues, and ensures native compatibility across all NAS-hosted media platforms.