Why VOB Containers Cannot Support Dolby Atmos

The standard Video Object (VOB) container cannot store Dolby Atmos because it is constrained by decades-old DVD-Video specifications that only recognize fixed-channel, legacy audio formats. Because Dolby Atmos relies on dynamic spatial metadata delivered via modern codecs like Dolby TrueHD or Dolby Digital Plus, the rigid MPEG-2 Program Stream architecture of a VOB file lacks the structural identifiers, multiplexing capabilities, and bandwidth allocations required to process and output object-based sound.

Frozen MPEG-2 Program Stream Architecture

A VOB file is fundamentally an MPEG-2 Program Stream (PS) governed by the strict DVD Forum specifications finalized in the late 1990s. The format assigns specific private stream IDs (typically Private Stream 1, ID 0xBD) exclusively to legacy audio types, including standard Dolby Digital (AC-3), DTS, and linear PCM.

Because the DVD-Video standard was frozen to ensure universal compatibility with standalone hardware players, the container’s specification was never updated to include packet identifiers, descriptors, or syntax for modern, object-based bitstreams.

Incompatible Underlying Codecs

Dolby Atmos is not a standalone audio format; it is an extension layer of spatial metadata embedded within a host audio stream. Atmos requires one of two specific codecs to function:

• Dolby TrueHD: A high-bitrate, lossless codec commonly used on Blu-ray discs.
• Dolby Digital Plus (E-AC-3): An advanced, high-efficiency codec used primarily by streaming services.

The VOB container does not support either of these codecs. It cannot recognize the extended substream headers used by E-AC-3, nor can it handle the MLP (Meridian Lossless Packing) architecture of Dolby TrueHD. Even though a basic Dolby Digital (AC-3) stream can live inside a VOB, standard AC-3 cannot carry the complexity of Atmos metadata.

Channel-Based vs. Object-Based Audio Limitations

VOB was designed exclusively for channel-based audio environments, such as stereo or 5.1 surround sound. In a channel-based setup, individual sounds are mixed into discrete, fixed speaker positions during post-production.

Dolby Atmos replaces this paradigm with audio objects—individual audio elements accompanied by real-time positional coordinates (X, Y, Z axes) that tell an Atmos-capable receiver where to place the sound in a 3D space. The VOB format has no mechanism to parse, preserve, or synchronize this dynamic spatial metadata alongside the video stream.

Bitrate and Buffer Constraints

VOB containers are engineered around the physical and operational limitations of standard DVDs:

• Total Bitrate Ceiling: The maximum combined bitrate for all multiplexed video, audio, and sub-picture streams in a compliant VOB is capped at roughly 10.08 Mbps.
• Buffer Management: Audio buffers are configured specifically for low-bitrate streams, such as 448 kbps or 640 kbps AC-3 tracks.

A lossless Dolby TrueHD bitstream with an Atmos extension can easily exceed 4 to 8 Mbps on its own. Multiplexing an Atmos stream into a VOB would breach both the maximum stream limits and the memory buffer allocations required for standard VOB demuxing, resulting in playback errors or buffer overflows.

To store and play Dolby Atmos tracks, modern media setups use updated containers such as M2TS (standard Blu-ray transport streams), MKV (Matroska), or MP4, all of which feature modernized muxing protocols capable of handling object-based spatial metadata and high-bitrate audio packets.