Mock Strip and PGCEdit

[mikenadia]

The movie is HIGH SCHOOL MUSICAL . VTS05 has some ILVU cells.
Did some preprocessing with PGCEdit and got the following error message duing the "Rebuild" phase in DVD-RB.
---------------------------
Rebuilder
---------------------------
Error in UpdateIFO:VTS_FO VOBID: 05/CELLID: 01was not found in the VOB
---------------------------
Then, I rerun DVD-RB straight from the rip and got the same error message.
The issue was fixed by running a "Mock Strip" with IFOEdit on VTS05 (the one that has ILVU cells).
Is it pure coincidence or not (the fact that the issue was on the titleset with ILVU cells).
Could I have done something in PGCEdit to find out that there was a potential problem before running unsucessfully DVD-RB.
Thx a lot.

[blutach]

Sounds like a mastering error/bad rip.

Regards

[mikenadia]

Thx you. That is what I thought. But I was interested in a "check " function in PGCEdit that will tell me that my Rip MIGHT be bad (like a simulation of what DVD-RB rebuild phase is doing ) so I can try to fix it with IFOEdit.

[blutach]

There is nothing that says that VCID 5/1 should be in any PGC. Not illegal if it's there or vice-versa. DVD Rebuilder (http://dvd-rb.dvd2go.org/) is your best test here concerning your source material. If it winges, then something is wrong. You might try running the project through a mock strip or thru VobBlanker or from PgcEdit: Tools - FixVTS (current domain). That should fix your VID #s.

Regards

[mikenadia]

Blutach, last question on that subject.
In my case, I run PGCEdit, Voblanker and FixVTS before proceeding to DVD-RB. During the Rebuild phase, I found out the problem (not fixed by either program), and did a Mock Strip. If the Mock Strip outputs the IFO files into DVD-RB source folder, can I just do the Rebuild phase or do I have to start from scratch DVD-RB.
Thx in advance.

[blutach]

A mock strip does not strip any VIDs. It is there to just fix pointers etc. If you have done a real strip of certain cells or streams then the output of course is a bit different.

In terms of DVDRB, if your project is now OK, I'd start from scratch. The reason is that the ECL and other files will be all different and while the encode might be OK for various segments, the rebuild will be messed up. You can of course try something like this. Move your m2vs to a backup folder. Do a prepare. Move the m2vs back. Rebuild. TEST!

Regards

[r0lZ]

A missing VOB or Cell ID in the VOB or in the IFO files is not illegal, and is theoretically transparent to the players. However, some applications such as transcoders or IFO editors have problems, usually because an internal table is not filled completely with correct data. This was the case of PgcEdit, but I have fixed that issue a long time ago. I remember that, when I have discovered that problem, we have discussed the problem here at D9. At that time, Jsoto has added the option "Reorder VID/CID sequence (if needed)" in VobBlanker, and FixVTS has been modified to automatically reorder the V/C IDs sequentially.

I wonder why FixVTS has not fixed the problem. Unless you use the CLI option -v (to not renumber the VOB IDs), it is supposed to remove the unreferenced cells, and renumber the remaining ones. Maybe it doesn't renumber the cells in the IFOs if they are already missing in the VOBs?

You can also try the VobBlanker option. (IIRC, it is off by default.)

I'll see if I can easily add a warning in the PgcEdit log when a missing VOB or Cell ID is detected...

[r0lZ]

OK, I've added the warnings when PgcEdit detects a gap in the VOB or Cell ID in the VOB files.

However, note that only the domains that are parsed for menu buttons or BOVs are checked. All menu domains are automatically parsed for menu buttons when PgcEdit loads the DVD, but the parsing for BOVs of the title domains is currently optional, and even if you have this option enabled, PgcEdit skips automatically by default the title domains without subpics, as they cannot normally have BOVs.
Also, the warning is displayed in the log only, and you can easily miss it.
For those reasons, I have added a function in the VOBU plugin to check for gaps in the V/CIDs. It will display the list of missing VOB and Cell IDs (or nothing if none were found.) If the parsing of some title VOBs has not been done yet, it will be launched automatically when needed.

Note also that this function checks for missing VOB/Cell IDs in the VOB files. It doesn't check for missing IDs in the IFOs. That means that a cell that is present in the VOBs but not referenced in the IFOs (and is therefore useless) is not displayed in the list. You can get rid of the unreferenced cells easily with FixVTS or VobBlanker.

As I don't have a DVD with missing IDs at home, I can't check the new function in real circumstances. Please check it yourself, and report here if it finds the missing cell correctly. Thanks!

vobu_plugin_v15.zip (http://home.tele2allin.be/vt6328799/pgcedit/plugins/vobu_plugin_v15.zip)

(This new function is not directly related to the VOBUs, but I don't want to have to maintain too many plugins, so I've added the function in the VOBU plugin.)

[mikenadia]

Thank you, blutach and r0lZ. I will check with the plug-in and report.
In the meantime, I misled you and apologizes for it. I did not use VObblanker after PGCEdit (ONLY FixVTS: did not use the CLI option ) because it is ILVU. The VOB that was giving me problem during the rebuild did not have ILVU (my mistake) and produced the following message in VobBLANKER.

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

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

Note: This is NOT an InterLeaVed VTS

It may be linked to the rebuild error message because when I load in VObblanker the output of the Mock Strip (that does not give any issue in DVD-Rb), I do not have the "mismatch" error.

P.S. I have read the ILVU thread
http://forum.doom9.org/showthread.php?p=913214
Probably that DVD-RB is too picky. Thx again.


PLUG-IN Report.
I must have done something wrong: I run the plug-in in the folder that gives me the mismatch error (no Mock Strip). Got the following Application error.
Error: wrong # args: should be "::menued::get_buttons_all_title_domains dir autostart ?msg? ?autoclose?"

The plug-in is probably installed properly (got the upgrade to PGCedit 8.7 message in the "PGC entry..." function)

[r0lZ]

My bad! I forgot that I've modified the routine that does the scanning for buttons and BOVs. The plugin is not compatible with the current version of PgcEdit. Sorry, you will have to wait the next version! :(

Anyway, seems you don't need the plugin, as the problem is probably due to bad authoring and/or incompatibility with DVDRB.

[Sir Didymus]

...
...Sorry, you will have to wait the next version! :(


Hei r0lZ, but this way the curiosity and the interest of all the forum is now directed towards the planned date of such new release... :scared:

Cheers,
and thanks a lot for your continuous and very much appreciated work on PgcEdit!

[r0lZ]

I don't have any planned date for the new version. Probably after the summer...

[Sir Didymus]

OK! No pressure from this side...
It was really just a personal curiosity!

Thanks anyway for answering.
Cheers,
SD

[mikenadia]

I know it is an old thread but...
I rerip this one with an updated ripper, got again the same issue (at least, deterministic) and was able to solve it (it went through DVD-RB with no error message ) by processing the problematic VOB ( that is ILVU) with VOBblanker .
I know that VOBblanker is not compatible with ILVU, but because I did not do any blanking, cutting... to any VOB, am I right in thinking I can use VOBblanker with ILVU in this Specific case, to fix pointers.

Thanks in advance.

[r0lZ]

Hum, I'm not sure. The problem is exactly that VobBlanker is unable to fix some pointers that are needed only for ILVU. I guess it could do its job just fine if the original ILVU pointers do not need fixing and if it doesn't modify them, but anyway, you cannot have the guarantee that all pointers are right.

And iirc, the problem is even worse, at least in some cases. VobBlanker (often or always?) reorders the cells, so it could as well separate the interleaved cells in "normal" cells, but still retain some info of the original ilved cells. You could end up with all interleaved cells playing in sequence, or with the impossibility to seamlessly jump from or to an ILVU to the next or previous cell.

Have you verified if the interleaved cells play as expected?

[blutach]

I'd stick to IfoEdit for ILVU'ed DVDs.

Regards

[mikenadia]

Thanks, rOlZ and blutach. Will stick to IFOEdit. It seems the interleaved cells are playing fine but I am not familiar at all with Angles.