Log in

View Full Version : Menu shrinking


buzzby
16th February 2006, 14:53
Hi

Been using DVDrb for a while now but feel as though i am not using it to it full potensial.

I used to use dvdshrink and used to use menushrink to shrink the menu's

Can i use this with DVDrb and if not is there another way to compress/shrink the menu's as i really only want the menu to activate the special features and stuff.

Thanks in advance

urvieh
16th February 2006, 16:35
There should be no problem using the two programmes along with DVD-RB. I would disable menu processing in DVD-RB though.

buzzby
16th February 2006, 17:58
Ahh cool. I was under the impression it would fail. I'll give it a go tonight.

Thanks

Trahald
16th February 2006, 18:19
Dvd RB Pro supports menu shrinking built in.
As far as preprocessing (using something else like dvdshrink or menushrink, etc first) you may be on your own if there is an issue as far as help goes. However, In general there are no issues with preprocessed sources.

urvieh
17th February 2006, 00:00
There are several ways to handle menus. For example, you can encode the main movie only AND the menu (just in case you want to keep the look and feel of the dvd but don't care about the extras), or you may keep the extras as slide shows. All these items are accessable via the menus.

blutach
17th February 2006, 07:30
If you use MenuShrink (http://jean.laroche.free.fr/MenuShrink/), chances are DVD Rebuilder (http://dvd-rb.dvd2go.org/) will ignore the resultant menu anyway, cos the shrunk menus are tiny (usually less than 20Mb).

Regards

buzzby
17th February 2006, 11:56
I have started playing with DVDRemake Pro as well which i think i prefer.

Just wish now it didn't take 13 hours to encode the DVD's to see the end result.

jdobbs
17th February 2006, 12:13
Why would it ever take 13 hours? My computer isn't that fast -- and usually takes 2 hours...

buzzby
17th February 2006, 13:28
WHAT


i have just finish an Encode with QuEnc using pretty much every seeting that slows it all down and it has taken 994 minutes ( which is over 16 hours).

jdobbs
17th February 2006, 14:55
Well, I normally use CCE -- QuEnc would be more like 3 hours...

feedback
17th February 2006, 20:33
Trellis Quantization will slow your encode down a Lot with not much improvement in quality. I believe I read a post by dragongodz or Nic a while back that indicated there was not much improvement in video quality by it's use. Hmmm! maybe it was jdobbs...:confused: well, I don't remember who it was but it was somebody that knows QuEnc.:)

dragongodz
18th February 2006, 02:41
QuEnc using pretty much every seeting that slows it all down
of course that will mean encoding takes a very long time. only use things like extreme & slow settings if you really dont care how long it takes.

Trellis Quantization will slow your encode down a Lot with not much improvement in quality. I believe I read a post by dragongodz or Nic a while back that indicated there was not much improvement in video quality by it's use.
thats right. trellis can give a small improvement but it is in no way optimised code so runs at snails pace. personaly i dont use it because the little extra it can give is IMHO not worth the time it takes. turning it off speeds things up considerably.

also if you are doing a test encode to check the menus etc then you would be better off turning off all quality settings so you could see the results quicker. then if ok do a proper encode with settings such as HQ on.

Boulder
18th February 2006, 09:37
And you can check the m2v files by opening them in VDubMod. No need to wait for the whole process to finish.

buzzby
18th February 2006, 10:45
thanks for the help.

Will just use High quality and 2 pass setting for now and see the difference.

If this speeds it up to like 3 hours then there goes my reason for trying to get a dual core CPU :)