MenuShrink ver 1.0 - utility for shrinking DVD motion menus to still frames

[jeanl]

Well, I see your point. Having a featurette is somewhat cheating... But boy, it sure looks good! I think you get credit for finding it!
At this point, it looks like both nwg and mig$y have found DVDs with lots of transition cells (menu intros/outros) with tiny buttons (less than 4x5).
If you keep them in MenuShrink (which is the normal behavior), the result is an annoying still before your menu, which is useless (non functional buttons) and you have to wait or press next to get to the real menu.

I'm tempted to enable the automatic kill feature when the buttons are smaller than 5 pixels. What do you guys think? There is a danger though, that it might kill a useful menu! That would be bad.
jeanl

[blutach]

Give ppl the option - they really should be able to view the cell and make their own decision. But, yes, those buttons are going to be pretty useless if they're just a few pixels wide.

Maybe you could test their command as well? - the ones I've seen are usually NOPs. In this case, there would be np in kill playback.

Regards

[nwg]

Sent you a email. MIB has 4x6.

[jeanl]

Originally posted by blutach
Give ppl the option - they really should be able to view the cell and make their own decision. But, yes, those buttons are going to be pretty useless if they're just a few pixels wide.

Maybe you could test their command as well? - the ones I've seen are usually NOPs. In this case, there would be np in kill playback.

Regards

Yes, that's a good idea... In fact, the size of the button does not really matter, it could be very tiny, with a very tiny highlight (say, a small arrow?) but still be functional (on a TV, harder with a mouse)... But of course, if you find the commands are NOPs, then there's no point in keeping them!

I think I'll turn the code ON by default (kill tiny buttons by default) with an option to not kill...

jeanl

[jeanl]

BTW, a million thanks to you guys, mig$y, nwg and blutach for doing all these tests for me!
jeanl

[blutach]

@jeanl - Just cos a button is tiny doesn't mean it's useless. For example in chapter menus to skip to previous/next program and HL a button.

These, of course, have another 10 or more "real" buttons in the cell. So, the button needs to be the only one in the cell and probably with a NOP, for auto Kill PB.

Eg MIB - VTSM 3, PGC's 6 and 8 (at least for R4)

Regards

[nwg]

Blutach, I sent you an email. I thought you may want to compare my log file with yours.

[blutach]

It's a monster isn't it? Taking a look.

Can you please do a menu button dump in PgcEdit and email? I would be interested in seeing button numbers by cell and their commands. I bet those "1 buttoners" are all NOPs.

Regards

[jeanl]

Originally posted by blutach
I bet those "1 buttoners" are all NOPs.

Regards

that would make my job easy!
jeanl

[blutach]

Jean is away for a week.

You can still post questions here.

v2 should be released shortly after his return.

Regards

[Mig$y]

Possible bug...? 1.16

@ Jean

Hope you had a nice break

A slight problem whilst "Menushrinking" the Mummy (R2)
(Using 1.16)



It then just closes and does not report the overall space saved.
It also does not give me time to save the log but here is where the problem lies:

[nwg]

I have the Mummy but is R1. How does that sentence end?

that was not originally what?

[Mig$y]

I'm not sure, it quits out quite quick, I'll try again and see if I can catch it

[nwg]

You could save the log to a txt file with the save button.

I just done the R1 and that works ok.

[Mig$y]

"that was not originally declared"