Casanova R1. VobBlanker reports aberration w/ DVD-RB processing, and not on Original.

[JFerguson]

The Setup:


Source was Casanova R1 ripped via DVD Decrypter v3.5.4.0 (Mode, ISO, Read), with all Remove options enabled under "ISO Read Mode" settings (e.g., Remove IFO Structure Protection, etc.). AnyDVD v5.9.5.8 was enabled on source DVD-ROM drive during ripping with "Copy Protection based on unreadable Sectors" option enabled. ISO image file was mounted via Alcohol 120% v1.9.2b1705.
No preprocessing was performed.



The Anomaly:

VobBlanker v2.1.1.0 reported this on load of the DVD-RB resultant build:

VTS 01: Detected 2 cells with pointers mismatch between VTS_C_ADT and PGC_PBK tables
Using VTSM_C_ADT initial and ending pointers...

This is quite ususal in ILV/multiangle VTSs, but VobBlanker does not support them,
except in skip mode.

Note: This is NOT and InterLeaVed VTS


Is this something to be concerned about? I do not get this from VobBlanker on load of the original mounted ISO.


Here is my project file:

[Options]
TargetSectors=2295205
vts_min_size=1024
vtsm_min_size=1024
CLOSED_CAPTIONS=1
Mode=1
OneClick=0
ReduceOpt=0
NoWarn=0
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=0
RemoveDTS=0
HC_Quality=1
HC_Matrix=1
SkinVersion=12
Skin=Rebuilder Default
AudioDub=1
QuEncodeType=0
iDCT=0
GOP=0
DCPrec=0
MainMatrix=Encoder Default
LowMatrix=Same as Main Feature
VLowMatrix=Same as Main Feature
ExtraMatrix=Same as Main Feature
ProCoder_Quality=4
DVD_Label=CASANOVA
DVD_Name=CASANOVA.ISO
MovieOnly=0
HalfD1=00000
Convert_16_9=00000
DisableInterlace=00000
ConvertToYUY2=1
CCE=3
SkipPrepare=1
Encode_Menus=1
[Paths]
Source=S:\VIDEO_TS\
QuEnc=D:\Program Files\DVD Rebuilder PRO\Encoders\QuEnc\QuEnc.exe
ReJig=D:\Program Files\DVD Rebuilder PRO\Encoders\ReJig\ReJig.exe
HC=D:\Program Files\DVD Rebuilder PRO\Encoders\HC Encoder\HCbatch.EXE
ProCoder=D:\Program Files\DVD Rebuilder PRO\Encoders\EclPro\EclPro.exe
DECOMB=D:\Program Files\AviSynth 2.5\plugins\Decomb521.dll
MPEG2DEC=D:\Program Files\DVD Rebuilder PRO\DGDecode.dll
Working=G:\!DVDWORK\!DVDRB1\
Output=H:\!DVDWORK\!DVDRB1\
CCENew=D:\Program Files\Custom Technology\CCE SP Trial Version\cctspt.exe
[Audio]
Selected=10000111
[Subpictures]
Selected=10011

[jdobbs]

Not sure, as I've never used VOB Blanker. But I can tell you that are a lot of DVDs these days that use a strange type of "sub cell" reference in the PGC that is never truly referenced. For example, you may find two cell references in the PGC tables that reference the same VOB_ID/CELL_ID, but point to different start sectors (one of them might be halfway through the cell). In this instance DVD Rebuilder will recreate the references so they will act the same as the original. I'm not sure how VOB Blanker responds to that.

[blutach]

If you run a mock strip or just let VobBlanker (http://jsoto.posunplugged.com/vobblanker.htm) do its stuff on the affected title, the pointers will be fixed.

Also, IIRC, this is an ARccOS DVD, which may have introduced some complexity into the process.

Regards

[setarip_old]

@JFerguson

"Casanova" R1 is a "RipGuard" copy-protected DVD. For a "clean" starting point (before using DVD Rebuilder):

1) (WITHOUT using "AnyDVD") Rip using DVD Decrypter v.3.5.4 in "File" mode (select "ALL" files, NOT "movie" files) and

2) Load the rip into VOBBlanker, set a new output directory/folder, select "Process all" and then press the "Process" radiobutton

[JFerguson]

Got this same error again with Deep Blue R1. Two within one week - that's an interesting trend. I do a lot of post-processing and never got these before.

I don't think I tried it with Casanova, but I did as blutach suggested with the Deep Blue output and it cleaned it up.


@setarip_old:

I haven't tried your suggestion, but I have no doubt that it would work - I'm very familiar with VobBlanker's ability to clean garbage out of DVD sources. In fact, it probably wouldn't make a difference whether I did so in File Mode, or via ISO/AnyDVD for that matter. I never rip in file mode, btw.

I haven't been a big fan of preprocessing DVD-RB source for support reasons, but I'm finding it increasingly necessary these days because of certain limitations of the tool (which is otherwise awesome, btw). For discussion, I'll probably document these limitations via a new thread in a few days...

[JFerguson]

Here's another one. And not that it's been 8 months since this has occurred... I see this pretty regularly and want to bump this to prompt a question or two.

The Setup:


Source was The Guardian R1 ripped via DVD Decrypter v3.5.4.0 (Mode, ISO, Read), with all Remove options enabled under "ISO Read Mode" settings (e.g., Remove IFO Structure Protection, etc.). AnyDVD v6.1.1.4 was enabled on source DVD-ROM drive during ripping with "Copy Protection based on unreadable Sectors" option enabled. ISO image file was mounted via Daemon Tools v3.47.
No preprocessing was performed.
I believe this a RipGuard-protected title.



The Anomaly:

VobBlanker v2.1.2.0 reported this on load of the DVD-RB resultant build:

The following PGCs are marked as not one_seq but they can be marked as one_seq (recommended)
VobBlanker will do it in output IFOs

VTS 01 PGC 003

- and then -

VTS 01: Detected 2 cells with pointers mismatch between VTS_C_ADT and PGC_PBK tables
Using VTS_C_ADT initial and ending pointers...

This is quite unusual in ILV/multiangle VTSs, but VobBlanker does not support them, except in skip mode.

Note: This is NOT an InterLeaVed VTS

List of Cells:

VTS 01, PGC 003, Cell 01
VTS 01, PGC 003, Cell 02


The one_seq check is something new, maybe something that v2.1.2.0 started doing. The original .ISO (mounted) produces this popup on load into VobBlanker as well.

The original .ISO (mounted) however, does not produce the pointers mismatch popup that DVD-RB's output yields when loaded into VobBlanker, though.

The question is this: is this pointers mismatch warning telling us that DVD-RB's output is not "correct" in some sense?

And yes, if I do nothing, I'm certain this will play without issue in any of my players.

And yes, if I run a mock strip in VobBlanker, it will clear this out (and the one_seq warning, for that matter), but who wants to bother doing this when the output is sized and ready to burn?

Just curious what you all thought -- thanks...

[setarip_old]

I'd strongly suggest you try changing your ripping methodology to using ONLY the "RipIt4Me" package of programs...

[JFerguson]

I'd strongly suggest you try changing your ripping methodology to using ONLY the "RipIt4Me" package of programs...

Does RipIt4Me rip to .ISO? That's my preferred format, and I thought that jdobbs uses AnyDVD as well...

[jdobbs]

I do. I normally rip to ISO using DVD Decrypter over AnyDVD.