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

[jeanl]

Yes, it's pure nonsense! But jm1647 is hot on the track, frantically going through little Danny's pile, trying to find the killer one!

BTW jm1647, you don't need to rip them to find out if they're good candidates! You can inspect them with decrypter, or even with menushrink straight on the DVD (processing won't work, but MS will tell you the overall size of the menus )
Jeanl

[jm1647]

jeanl - I had my dvd drives screaming for mercy the other night using MS to check out me and Lil Danny's stuff lookin' for one that has not been done to crack the top 10. There a few new ones I wanna get, I might get lucky!

Hi Ho......

[Mig$y]

>jeanl

Little prob whilst "Menushrinking" the Muppets Treasure Island (r2).... Using 2.1



All files ripped to hd with DVD Decrypter. The files open in DVD Shrink and playback is ok with WinDVD and PowerDVD.

??

[Mig$y]

[jeanl]

mm, I'm puzzled.
- Is there a VTS_01_0.VOB to begin with?
- Is it locked by some other app?
- This message happens when MS is having a hard time moving a file. Try moving the file by hand, just to see, from the original directory to the backup...
If none of this works, then let me know!!!
jeanl

[Mig$y]

Yeah, There is a VTS_01_0..... 282mb

No other apps are using the the files.

Moving by hand works fine.


Edit - Umm, just re-tried and it works.... Ignore me bud, I'm losing the plot.

[blutach]

Had us worried there for a minute migsy

Regards

[jeanl]

Mig$y, this has happened to me before, so don't feel bad. For a reason that completely eludes me, the microsoft call to change the name of a file (move it) returns an error code on rare occasions. I'm not sure why... I thought I found why and fixed it for 2.1, but apparently not.
Usually, restarting MS fixes it... But I'd like to get to the bottom of this!
jeanl
P.S. I ran into a new problem with MS, for a DVD whose VTSM_VOBU_ADMAP table was incomplete to begin with (there was 1 cell that was not referenced in any PGC, AND not declared in VTSM_C_ADT AND whose VOBUs where's listed in VTSM_VOBU_ADMAP). MS was crashing with an error message on that (like it used to for bad VTSM_C_ADT tables), so I had to fix that as well. I'll post an update later.

[blutach]

Now that's bad authoring Jean!

Regards

[jm1647]

Ain't a killer save but it's me biggest so far over 916 MB on Control - R1

Thanks jeanl!!

[jeanl]

Originally posted by jm1647
Ain't a killer save but it's me biggest so far over 916 MB on Control - R1

Thanks jeanl!!

HAHA! You're getting closer man! That puts you in 14th position!

jeanl

[jm1647]

Ahhh... I knew it wouldn't crack the top ten soooo....

Hi Ho, Hi Ho, it's off to shrink I go

[chris83]

ISO Mode Question

I'm brand new to ALL of this, so please pardon my ignorance if it blinds all of you with this question.

If I rip a DVD using DVD Encrypter in ISO Mode (which places a disc image of the DVD on my hard drive...correct?), can I still use MenuShrink before going into DVD Shrink?

[jm1647]

I never tried it in ISO mode I usally rip in file mode, then Menu Shrink, then VOB Blank, then DVD Shrink if necessary. I like keeping the menus.

[jeanl]

chris83, MenuShrink can't process from the ISO. In my experience, there isn't much to gain in ripping to ISO, unless you want to burn it straight as is (if it's a DVD-R or you have a double layer writer).
Ripping in file mode allows you to "reauthor" your DVD (remove the unwanted stuff) before using DVDShrink. DVDShink has no problem opening DVDs ripped in file mode and all the soft DVD players can play DVDs saved in a directory (but most can't play ISOs unless you "mount" them) so there's really no drawback to doing that.
jeanl
BTW: welcome to the forum!