Missing or Corrupted Sequence VOB File Effects

When a sequential VOB file such as VTS_01_2.VOB is missing or corrupted, the DVD structure breaks, leading to playback failures, missing video segments, and conversion errors. This article explains how DVD sequencing relies on continuous VOB chains, what happens during playback in physical and software players, how ripping software handles the missing data, and whether the remaining footage can still be salvaged.

The Role of VOB Sequences in DVD Architecture

Standard DVD-Video structures store movie data inside the VIDEO_TS folder, split into 1 GB chunks named sequentially (e.g., VTS_01_1.VOB, VTS_01_2.VOB, VTS_01_3.VOB). These files are not entirely independent videos; they are continuous MPEG-2 program streams split across files to comply with the UDF/ISO file system limits. The playback logic, chapter points, and timing maps are stored separately in the corresponding .IFO file (such as VTS_01_0.IFO).

Playback Failure in DVD Players

If a physical DVD player or full-disc software player attempts to play the title:

• Playback Halts or Freezes: The player follows the sector pointers in the IFO file. When playback reaches the end of VTS_01_1.VOB and attempts to address the data blocks expected in VTS_01_2.VOB, the player encountered a missing address or unreadable sector. This typically results in a frozen screen, an indefinite loading loop, or a read error message.
• Timeline and Chapter Inconsistencies: The DVD menu might still load if the menu files (VTS_01_0.VOB and VIDEO_TS.VOB) are intact. However, selecting a chapter located within or after the missing file will cause an immediate crash or reset back to the root menu.
• Skipped Content: Some modern software players will attempt error recovery by jumping to the next available sector. If successful, playback skips the entire missing chunk directly to VTS_01_3.VOB, causing an abrupt jump in the video and often causing audio/video synchronization errors for the remainder of the title.

Impact on Media Players (Direct File Playback)

When playing the files outside the DVD menu structure using media players like VLC:

• Individual VOB files act as raw MPEG-2 containers. If VTS_01_2.VOB is deleted, VTS_01_1.VOB will play normally up to its final frame.
• VTS_01_3.VOB can often be opened independently, but it may suffer from missing timestamp headers, broken keyframes at the start, or audio drift because the initial stream headers were established in the earlier files.

Failure in Ripping and Transcoding Tools

Tools like MakeMKV, HandBrake, or FFmpeg rely on the continuous stream and the IFO navigational tables to assemble a complete video track:

• MakeMKV: Reads the IFO file to map chapters and cells. Missing a sequential VOB causes a read error, leading the software to abort the rip or output a corrupt, truncated MKV file.
• HandBrake: Typically fails during the title scanning phase or fails mid-encode when encountering the missing sector, resulting in a partial video output up to the end of VTS_01_1.VOB.
• Direct Concatenation: Merging the remaining files via command-line tools will result in a hard jump where the missing segment was, often breaking the MPEG-2 timecode stamps and causing audio desynchronization.

Salvaging the Remaining Data

If VTS_01_2.VOB cannot be restored:

1. Process VOBs Individually: Treat each remaining VOB file as a standalone video file rather than a DVD set. Convert VTS_01_1.VOB and VTS_01_3.VOB separately into MP4 or MKV formats.
2. Re-encode with Fresh Timestamps: Pass the isolated files through a transcoder to rebuild the missing MPEG-2 headers and fix timestamp discontinuities before stitching the remaining parts together.