Is this just bad authoring or a real error

[jeanl]

I've seen several DVDs where some cells in the menu VOBs are not referenced in the VTSM_C_ADT table. MenuShrink flags that as a problem, but DVD Shrink normally opens such DVDs without problem...

I'm wondering if ommitting a cell in that table is an error, or if it's legit...
jeanl

[mpucoder]

It is non-spec, but probably part of a copy protection scheme.

[jeanl]

Originally posted by mpucoder
It is non-spec, but probably part of a copy protection scheme.
Well, it does not seem to affect many programs (except MenuShrink), not a very effective copy protection technique!!!

I checked with PgcEdit, the missing cell of course isn't referenced in any PGC, but it's in the vob, and it's long (1-2 minutes, it has 5 copies of the same studio logo twirling around).
jeanl

[dragongodz]

the missing cell of course isn't referenced in any PGC, but it's in the vob
i have seen quite a few dvds with unreferenced menu parts, especially title menu, in dvds here. i have even seen pracically the whole menu repeated as unreferenced material(200mb worth). nothing has had any problems with them though so atleast with the dvds i have seen these have been just poorly authored and not any type of protection.

so i wouldnt worry too much about it unless there is a problem copying the dvd. either way just blank or remove it and see if that causes any side effects. if not then again nothing to worry about. :)

[jeanl]

dragongodz, it's not just that the material is unreferenced. As you said, that's not a problem. What is a real authoring error, apparently, is that some of the cells are not reported in the VTSM_C_ADT table. That's pretty rare as far as I know (Menushrink complains about it, that's how I find out!).

The problem is that once these are processed with MenuShrink, DVD Shrink refuses to open them, until we do a mock strip.
I checked what the mock strip changes, and it looks like the only important thing that changes after the mock strip (other than some of the cell durations, which shouldn't matter) is the number of cells in that table...
I'm totally puzzled as to how can DVD Shrink open an original DVD that has this faulty IFO, then complain after a MenuShrink processing! I guess I'm going to have to bite the bullet and make MenuShrink fix the offending table...
jeanl

[blutach]

We do know that a mock strip - either on the original or menu shrink files - fixes the problem.

Suspect this is the way to go Jean, especially if it adds lots of processing time to MenuShrink.

Would be interesting to see how VobBlanker treats it.

Regards

[dragongodz]

That's pretty rare as far as I know (Menushrink complains about it, that's how I find out!).
yes but i mean how many other programs complain or do not work ok with it ?

The problem is that once these are processed with MenuShrink, DVD Shrink refuses to open them, until we do a mock strip.
again how many programs does this happen with, just dvdshrink or does, for example, DVD-Rebuilder or other programs complain or have problems processing ?

if the answers to the above are ,(1) no others complaining and process fine and (2) multiple programs complain or dont work correct after MenuShrink and no mock strip, then that would suggest fixing the table(as you said) would be whats needed.

[jeanl]

There's no doubt in my mind I need to do that (fix the table in MS). I'm just puzzled because I don't understand what's going on (why is the faulty table OK before MS but not OK after MS, from DVD Shrink point of view?). I'll keep on investigating, then I'll tell you guys what I've found out.
jeanl

[jeanl]

OK, I've put an updated version on the web, version 2.03, here (http://jean.laroche.free.fr/MenuShrink/Binaries/MenuShrink2.03.zip) fixes the table (if it can, i.e., if there's enough room to add the missing entry).

Just FYI...

jeanl

[jeanl]

By the way vobblanker does fine in that situation. According to the log, it rebuilds the table, and DVD Shrink has no problem opening the output DVD...
jeanl

[jsoto]

VobBlanker always rebuild the ADT and ADMAP tables, as IFOEdit's mock strip does.

AFAIK, DVD shrink uses ADMAP table to access to all the VOBUs, not sure if it uses ADT tables..

So, you should take a look what MS does with ADMAP table if the original DVD opens in DVD shrink and the one processed by MS does not.

jsoto

[jeanl]

Originally posted by jsoto
VobBlanker always rebuild the ADT and ADMAP tables, as IFOEdit's mock strip does.

I was suspecting that! Good job!


AFAIK, DVD shrink uses ADMAP table to access to all the VOBUs, not sure if it uses ADT tables..
So, you should take a look what MS does with ADMAP table if the original DVD opens in DVD shrink and the one processed by MS does not.
jsoto
I did. The ADMAP table is correct, (and unmodified by a mock strip). The new version of MS which now corrects the ADT table produces a DVD that DVD Shrink opens without any problem. So somewhere in the DVD Shrink code, the ADT table is looked up! (you can do this very simple experiment! change the number of cells in that table using ifoedit, and try to load in dvd shrink, you'll get an error)...

jeanl

[blutach]

New version on its way? Must be 5 in 5 days Jean :)

Regards