Log in

View Full Version : Fixing VOB pointers


mikenadia
15th January 2008, 17:31
Ripped T4XI.
went to PGCEdit ,(no Jump to Nowhere, No Jump to void PGCs, No uncalled PGCs), did Rebuild all timetables and Saved.
went to VOBblanker (no free space to Regain), and Process.

I got the following Warning and was wondering if I should have done more checks in PGCEdit or if I have always to process with VOBblanker.Thx.

VTS 01: Fixing VOB pointers in 5 Cells of 5
Fixing Cell # 1, VID=1 CID=1
Fixing Cell # 2, VID=2 CID=1
Fixing Cell # 3, VID=3 CID=1
Fixing Cell # 4, VID=4 CID=1
Fixing Cell # 5, VID=5 CID=1
--------------TITLE VOB FIXING POINTERS FINISHED-
VTS 01: Processing IFO (Titles)
Looping into Title PGCs and cells
PGCN Pointer: Pointing Prev PGCN to itself in PGC 1
PGCN Pointer: Pointing Prev PGCN to itself in PGC 2
PGCN Pointer: Pointing Next PGCN to itself in PGC 3
PGCN Pointer: Pointing Prev PGCN to itself in PGC 3
Processing TMPATI table
NOTE: PGC: 1 is not a One Seq PGC. Anyway, creating entries in TMAPTI
Added 394 entries in TMAPTI of PGC 1
NOTE: PGC: 2 is too short. No entries in TMAPTI are created
Added 0 entries in TMAPTI of PGC 2
Added 1605 entries in TMAPTI of PGC 3
Generated a TMAPTI table with same # of sectors than original
Building VTS_C_ADT table
Filling VTS_VOBU_ADMAP table

blutach
15th January 2008, 21:09
Maybe you had the setting to fix always all pointers in VobBlanker?

Regards

mikenadia
15th January 2008, 21:39
Blutach, always right. I took the settings that you recommended for VOBblanker (cannot find the link with the picture anymore) on one computer and default ones on the other .
To summarize, nothing wrong with that warning .Thx.
P.S. I hope you did not change your mind on the settings.
I rerun VOBblanker with default settings and all those "Fixing ..." do not appear. Was scared by the wording "Fixing".