VOBBlanker Error: VOB Unsychronized

[kingspawn]

I am getting the following error when trying to process various DVD's (already on the hard drive) through VOBBlanker. DVDRebuilder also has problems with these same DVD's. The DVD files were put to the hard drive using the latest DVDDecrypter.

Does this sound like a program problem, bad rip or some other issue?

Thanks.

[jsoto]

Seems a rip problem.

Unsynchronized means the packs in the VOBs does not start with 000001BA, so they are invalid.

Try opening them with VOBEdit (if it can, may be it crashes with bad VOBs) and see what is there.

jsoto

[kingspawn]

Thanks, I'll give that a try.

[kingspawn]

I rip'd the DVD again and the problem went away. Thanks.

[Thang_Bom]

I got the same error.

The DVD was ripped and putback with scenarist and IFOUpdate. Play back with PowerDVD, it is ok. It failed on both 1.6.01 and 1.60.5

Here is the log: The process failed with 1.5 GB of data process.

Version 1.6.0.5. Starting new process:

VTS 01: Opening IFO
VTS 01: Processing VOB (Menus)
VTS 01: Keeping Menu LU 01, PGC 02
VTS 01: Keeping Menu LU 01, PGC 03
VTS 01: Keeping Menu LU 01, PGC 05
VTS 01: Keeping Menu LU 01, PGC 06
VTS 01: Keeping Menu LU 01, PGC 07
VTS 01: Keeping Menu LU 01, PGC 08
VTS 01: Processing IFO (Menu)
Looping into Menu PGCs and cells
Building VTSM_C_ADT table
Filling VTSM_VOBU_ADMAP table
VTS 01: Processing VOB (Titles)
VTS 01: Keeping PGC 01
Error reading input VOB: Unsynchronized

PostCommands changed into Precommands in 0 PGCs of a total of 0

Finished with ERROR. Process Aborted and not completed

[jsoto]

I'm pretty sure there is something wrong in the VOB.

Try to locate the pack with VobEdit too see if it starts with 000001BA

You can do it in the following way:
a) Change PGC1 to Cellbased mode (instead of keep) blanking one cell (the last one, for example), and hit process.
In the log file you will have the log of each cell, and you will be able to locate which cell is causing the problem.

b) Try to extract this cell (with VobBlanker). Not sure, but I believe it will extract the cell just until the offending pack. See the file size and divide by 2048 to get the number of sectors extracted. This is the sector from the start of the cell.

c) Open your original IFO in IFOEdit. Locate the Cell inisector (in VTS_C_ADT table or in PGC1 tables). Add to this sector the sector calculated in the previous step

d) Open the VobEdit and go to the offending sector. See if it starts with 000001BA


jsoto

[hf]

I'm getting the "error reading input vob: unsynchronized" error
also, but I think my case is a little different. I have some
camcorder video that I created a DVD with using Roxio's DVD
Creator. There are 4 programs. The total size is about 5.5GB.
All the audio is LPMC encoded, so I wanted to process each
program to convert the audio to AC3 to save some space.
I used pgcdemux (1.2.0.2) to demux, AC3Machine (0.41)
to convert to AC3 and muxman (0.12c) to put everything back
into a VOB. I then used VOBBlanker (1.6.0.6b3) to replace the
existing program with the new one. At the very end of processing
the replacement VOB I get the unsynchronized error. The original
program is about 1.8GB in size and the replacement program is
about 1.3GB in size. Both are a single cell.

I've done basicly the same thing when backing up an existing
dvd, converting the audio to AC3 and didn't have any problems.

Using your previous suggestion of taking the file size/2048 to get
the number of sectors, I see that vobblanker wrote out exactly 662305
sectors, but the demuxed/remuxed file size is not a multiple of
2048 (It is 662306 sectors plus 38 bytes) this is not correct
is it?

I just used vobedit to look at the end of the demuxed/remuxed file,
I see: AC3-AudioPack, NavigationPack, VideoPack, UnknownPack
so I guess that is what vobblanker is choking on. Anyone have any
ideas?

As I side note, I think I found a bug in the cells->replace
feature. After I got the Unsynchronized error using vobblanker's
replace feature I tried cells->replace instead. I didn't get
an error, but only the first GB was replaced. EG: The replacing
cell was 1.4GB and the VTS_nn_2.VOB file was not included.

[jsoto]

Yes, seems your remuxed VOB is corrupted at the end. It must be multiple of 2048 bytes. Did you look into muxman log file?

About Cell replace, not really a bug. VobBlanker assumes only one file in this case (different from PGC replace, where multiple files are allowed). You can simply join your files with a MS-DOS command:
copy /b VTS_01_1.VOB+VTS_01_2.VOB FULL_01_1.VOB

jsoto