DVD-VR vs Standard DVD-Video Navigation Tables

DVD-Video and DVD-VR (DVD Video Recording) handle disc navigation differently because they were designed for different use cases: standard DVD-Video was built for commercial, read-only playback with complex interactive menus, whereas DVD-VR was engineered for real-time recording, rewritability, and on-disc editing. The primary difference lies in how navigation tables are structured and referenced: standard DVD-Video relies on a rigid hierarchy of Video Title Sets (VTS) with navigation data embedded directly into the video stream via Navigation Packs (NV_PCK), while DVD-VR centralizes navigation in a single management file using Original and User-Defined Program Chains (PGCs) paired with simplified Real-Time Data Information (RDI) packs.

File Organization and Hierarchy

Standard DVD-Video discs store data inside the VIDEO_TS directory, dividing control information across multiple files:

• VMG (Video Manager): Located in VIDEO_TS.IFO, this table handles disc-wide navigation, parental controls, and global menus.
• VTS (Video Title Sets): Each video title set has its own VTS_xx_0.IFO file containing dedicated Program Chain Information Tables (VTS_PGCIT), which map the chapters, playback order, and cell boundaries for that specific title.

DVD-VR eliminates this multi-file hierarchy, storing everything in a DVD_RTAV directory using just two operational files: VR_MANGR.IFO (management data) and VR_MOVIE.VRO (the combined audio/video stream). All navigation tables exist entirely within VR_MANGR.IFO, doing away with individual title-set files.

In-Stream Navigation Packs: NV_PCK vs. RDI_PCK

In standard DVD-Video, navigation is deeply intertwined with the MPEG-2 stream:

• Every Video Object Unit (VOBU)—roughly 0.5 seconds of video—begins with a Navigation Pack (NV_PCK).
• The NV_PCK contains two specific sub-tables: the Presentation Control Information (PCI) and the Data Search Information (DSI).
• PCI manages real-time menu button actions, sub-picture switching, and angles.
• DSI provides forward and backward sector pointers to other VOBUs, enabling fast-forward, rewind, and seamless branching.

DVD-VR discards PCI and DSI tables to allow real-time encoding without the computational overhead of calculating complex cross-sector jump pointers:

• Each VOBU begins with a Real-Time Data Information (RDI) Pack.
• The RDI pack stores basic presentation timestamps, copy generation management system (CGMS) flags, and aspect ratio flags, but lacks interactive button tables or complex jump pointers.

Program Chain Structures: Fixed Playback vs. Playlists

The Program Chain (PGC) tables define playback sequencing, but they behave differently across both formats:

• DVD-Video: Navigation uses fixed Program Chain Information (PGCI) tables. Titles consist of sequential Cells grouped into Programs. Because navigation is authored beforehand, modifying the order of playback or trimming scenes requires rebuilding the VTS_PGCIT and re-multiplexing the VOB files to update sector pointers.
• DVD-VR: Navigation is split into two primary PGC tables:
  1. Original PGC (ORG_PGCI): Represents the raw, chronological recordings as they exist on the disc. It automatically updates when new video is recorded or deleted.
  2. User-Defined PGC (UD_PGCI): Serves as a virtual playlist table. Users can create, delete, reorder, and trim scenes without touching the recorded stream in VR_MOVIE.VRO. The UD_PGCI simply references start and end timecodes within the existing stream.

Time Mapping and Random Access

• DVD-Video: Uses the Time Map Table (VTS_TMAP) inside each title's IFO file. It maps playback intervals (typically every few seconds) directly to logical sector numbers (LSNs) in the corresponding .VOB files to allow jump-to-time functionality.
• DVD-VR: Utilizes a Time Map (TMAP) located inside the Video Object Information (VOBI) structure within VR_MANGR.IFO. Because DVD-VR discs (such as DVD-RAM or DVD-RW) frequently undergo file fragmentation from repeated recording and deleting, the DVD-VR time map translates playback time directly to discontinuous data extents within the single .VRO file.