MenuShrink version 2.4 - utility for shrinking DVD motion menus to still frames

[Mig$y]

I didn't do VTSM1 before, although I just did and it works and opens in Shrink no probs...

As you mentioned previously, it may be an idea for jean to mention the mock stripping solution for problem dvds

[blutach]

Tra dahh.

OK, jeanl needs to see this. Did you mock strip before or after the menu shrink?

Did DVD Shrink open the original OK?

Can you run an little experiment for me? Run a VidChanger (at jsoto's site) over the menus in VMGM and VTSM1. Fixed cell ID. Then run menushrink and see if any warnings.

BTW: Running VidChanger will ensure unreffed mat can be eliminated by IfoEdit, shrinknig things even further!!!

Regards

[Mig$y]

I processed through MS, restored backup then did a Mock Strip
(ensuring there were no files left in the Menushrinkbackup folder)

Shrink opened the original with no problems.

I'll grab VidChanger and let you know...

[blutach]

It would be interesting to see what happens if you did a mock strip of the menu shrunk files.

In general, and I hope jeanl updates the home page on this, with any problems with this error, a mock strip seems to be the first port of call.

Regards

[Mig$y]

Ok...

VIDChanger run using Video_ts.ifo & VTS_01_0.ifo as input.

Output files cut and paste into Video_ts folder and then processed through MenuShrink.

Still reports the same errors..

[jeanl]

OK, so it looks we can't ignore these problems with VTSM_C_ADT tables.
I suspect the problem is in MS. I'm guessing I'm quitting the routine that normally updates VTSM_C_ADT and I don't finish the job the right way... I'll take a look. Sorry about that guys!
But really, is it legit to have a cell that's not referenced in VTSM_C_ADT????

I'll ask mpucoder at doom9!
jeanl

[blutach]

So, if you do a Mock Strip on the output now, does that fix it?

I would think that it is an authoring error in the original.

Regards

[blutach]

@jean - does MenuShrink actually do a mock strip or just update the table?

Regards

[jeanl]

Originally posted by blutach
@jean - does MenuShrink actually do a mock strip or just update the table?

Regards

It depends on what you mean by a mock strips. MS does not do a full mock strip (i.e. get all the info from the VOBs and then reflects that in the IFO). It simply updates what's in the IFO, reflecting the changes that have been made in the VOBs. So it's really not a full mock strip. But apparently the VTSM_C_ADT error (if indeed it's one!) isn't something that causes shrink a problem in itself. Only after MS is done processing does it cause a problem. I'll look into it.
I have an example of a DVD with such an error.
jeanl

[blutach]

Good stuff Jean. It seems that migsy's got 2 like these, where a Mock Strip (on the originals!) has cured them both - that's what makes me thing it's an authoring problem.

Regards

[Mig$y]

On the Files that are processed through MS then given a Mock Strip work fine (Video_ts.ifo & VTS_01_0.ifo)

[blutach]

Jean - it's on the originals - I reckon there's nothing you can do (other than doing a full mock strip in the prog) except highlight a warning in the manual and the home page that if this warning occurs to do a mock strip.

Do you think it would be a good idea to go back to the old behaviour of stopping on this error instead of allowing it?

Regards

[jeanl]

Wait! It's not that simple! Why does DVD Shrink open the original DVD with no problem (even though it has this "error") but not the MS version?! There must be something I'm not doing on the IFO that I should!
jeanl

[jeanl]

mig$sy, here's something you could do to help me: Could you possibly send me video_ts.ifo after MS (the one that DVD Shrink won't open)? along with the MS video_ts.vob (remove audio, it should be pretty small).
Then I can do a mock strip and see what area of the IFO gets modified. Presumably that would be the area the DVD Shrink finds offending!
jeanl

[Mig$y]

Sure Jean, no problemo

I've been messing around so I'll re-rip first....