| Author |
Message |
toaddub Moderator

Joined: 12 Sep 2004 Posts: 1988
|
Posted: Fri Dec 16, 2005 1:14 am Post subject: Recovering cell info shows different size b/t v322 and v267 |
|
|
Here's the log when v3.2.2 is recovering cell info for VTS 4: ........... Read VTS4 can't find segment (862:VobData.cpp) Recovering C_ADT & VOBU_ADMAP tables. (680:VobData.cpp) Can't open title set vob - will substitute blanks. (860:VTS.cpp) Cell #1 uses vobus (vobID=1, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Cell #2 uses vobus (vobID=2, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Cell #3 uses vobus (vobID=3, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Cell #4 uses vobus (vobID=4, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Cell #5 uses vobus (vobID=5, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Cell #6 uses vobus (vobID=6, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Cell #8 uses vobus (vobID=7, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Cell #9 uses vobus (vobID=8, cellID=1) not pressent in vob file. Substituting blank cell instead. (1774:PGC.cpp) Apparently, there are previews in VTS 4 when play normally and directly. I tried prior v3 and they show the same log and size. I then loaded into v2.6.7 and below shows the difference. VobBlanker also shows 226 MB.
| Description: |
| Here's the VTS 4 navpack for you to look at. |
|
 Download |
| Filename: |
Navpack.rar |
| Filesize: |
91.31 KB |
| Downloaded: |
132 Time(s) |
|
|
| Back to top |
|
 |
Mirx Respected Member

Joined: 17 Apr 2004 Posts: 696
|
Posted: Fri Dec 16, 2005 5:53 am Post subject: |
|
|
| Quite common actually. Have seen this multiple times as well. But it's just due to the fact that DRM actually checks the ifo pointers versus the VOB pointers. If the pointers are to far of, DRM can't distinguish which content will belong to which cell, and blank it, as it considers it fubar. So in this case, they messed up the source disc, and the ifo pointers don't allign with the vob pointers. Replica used to have a hand of getting these wrong, remember all the posts when v3 just came out.
|
|
| Back to top |
|
 |
DimadSoft DvdReMake Official support

Joined: 19 Mar 2004 Posts: 2193
|
Posted: Fri Dec 16, 2005 9:39 am Post subject: |
|
|
Can't reproduce the problem with that file.
|
|
| Back to top |
|
 |
toaddub Moderator

Joined: 12 Sep 2004 Posts: 1988
|
Posted: Sat Dec 17, 2005 6:53 pm Post subject: |
|
|
I processed with VobBlanker, changed nothing for VTS 4, then import into DRMP -- no more recovering cell info attempt and there's content and 226 MB. The DVD is Silver Hawk R1, if you like to take a look. Another alternative, I used FixVTS to process VTS 4 vob, with "Remove unref. and blank cells" checked. Here's the log: | Code: | | FixVTS -- Beta 1.17 Processing J:\Silver Hawk\DVD\VIDEO_TS\VTS_04_1.VOB -- from backup Remove unrefed is ON Found VCID 1/1 at LBA 0 (0 out) Found Video Format: NTSC Format Video: NTSC Found VCID 2/1 at LBA 3698 (3698 out) Found VCID 3/1 at LBA 3894 (3894 out) Found VCID 4/1 at LBA 40515 (40515 out) Found VCID 5/1 at LBA 43563 (43563 out) Found VCID 6/1 at LBA 45674 (45674 out) Found VCID 7/1 at LBA 82285 (82285 out) Found VCID 8/1 at LBA 115950 (115950 out) Found VCID 9/1 at LBA 115955 (115955 out) VCID 9/1 is unreferenced... Done with VOB files. 0 navpack pointers adjusted, 499 packs removed, 0 navpack remapped Processing J:\Silver Hawk\DVD\VIDEO_TS\VTS_04_0.IFO Now cleaning VTS_C_ADT Now updating navpack info Now updating navpack info Now updating PGC playback times Now updating VTS sectors Now writing IFO file Now updating video_ts.ifo vts sectors Now writing video_ts.ifo | Import the result into DRMP and there's content, even though the log says "Recovering C_ADT & VOBU_ADMAP tables. (680:VobData.cpp)". At least it does not substitute with blank cells for V/C 1/1 - 8/1. This situation also occurs in the Skeleton Key R1 as well for VTS 8, where there is an unreferenced V/C 4/1 (the running man). Only after using FixVTS will DRMP can read the info correctly. Could this due to the fact that there's an unreferenced cell involved? I thought DRMP would remove that automatically if found.
|
|
| Back to top |
|
 |
CDR-Zone.COM Advertisement Bot
 
|
Posted: Post subject: Advertisement: |
|
|
|
|
|
| Back to top |
|
 |
|
Powered by phpBB © 2001, 2005 phpBB Group
|