Making video from game using MeGUI

[eurUz]

Hello, i'm doing a movie from a game and i was wondering if someone can help me with MeGUI settings. As i told the video clip is done from a game and as i have kind of slow pc then sometime it takes me 12 hours to enode 9 second clip and it would be really annoyng to start testing and always see the same result that still isnt good enough. The point is that i would like to have a really high quality movie that wouldn't be very much over 35Mb per minute. The settings i use give me picture like this(http://www.zone.ee/pro1337/nonii.mp4) but i know it can be a lot more better.OK the settings i use in MeGUI for getting this picture are:
Turbo, Automated 3pass @ 3150 bitrate, deblocking is enabled and deblocking strength is -2 and Threshold is -1, fourCC is VSSH, AVC Profile is high Profile and AVC Level is unrestricted,VBV Initial Buffer is 0.9, Bitrate Variance is 4.0, Quantizer Compression is 0.7, Temp. blur of est. Frame Complexity is 20, Temp. Blur of Quant after CC is 0.5, Chrome M.E is enabled M.E Range is 32, Scene Change Sensitivity is 40, M.E Algorithm is Multi Hex(sometimes i use Hexaustive), Subpixel Refinement is 7-RDO Level 2, Keyframe interval is 250, Min GOP size is 25, Noise Reduction is 0, Encode
interlaced disabled
Trellis 2-Always
Number of referenced frames 10
Mixed Reference frames enabled
CABAC enabled
No Dct Decimation disabled
No fast P-skip disabled
Minimum Quantizer 3
Maximum Quantizer 51
Maximum Quantizer Delta 4
Credits Quantizer 40
Factor between P and B frame quants 1.3
Chroma QP offset 0
Quantizer matrix JVT
Macroblock Options i'va enabled all(adaptiveDCT, l4x4, P4x4, i8x8, P8x8, B8x8)
Number of B-frames 16
Adaptive B-frames enabled
B-Pyramid enabled
RDO for B-frames enabled
Weighted B-prediction enabled
Bidirectional M.E enabled
B-frame mode Temporal
B-frame bias 1
So maybe someone can help me a bit, thx
i forgot to mention that i use x264 codec

[Dr.Khron]

12 hours for a 9 second clip?!?
Something sounds really wrong about that... even with a "slow" PC, that just ain't right.

If you are doing some heavy AviSynth filtering, using the pre-render pass might help, specially since you are using three-pass encoding...

Whats your AS script look like? Is your source material in an uncompressed format, like Huffy AVI? What did you capture your source with?

[eurUz]

My avisynthscript:
AVISource("VEGAS_test_1_MmF.avi")
Crop(0,0,-0,-0)
ConvertToYV12()
#Lanczos4Resize(720,480)
i use 200 fps captur from the game so i get 1280x720 TGA's
i compress them at virtual dub with huffyuv 2.1.1 and do same with vegas after virtual dub and make it to 25 fps and move to MeGUI

[Dr.Khron]

hmmmm... I'm not familiar with doing that kind of work in VDub, I would do all of that directly in AviSynth... (ie, load the still frames in, change the frame rate, etc.etc)

Two things:
Why are you changing the aspect ratio? Video games use square pixels, and I would assume you want your final output to be square pixel, too.

Why 25 FPS for output? Was that a random choice, or are you looking to make PAL content?

[eurUz]

well i'm changing aspect ratio because.. dunno why, but i did it coz as much as i have seen other people doing movies like it, do it aswell and i was following them.
fps i was using 25 pal yes and because the 200 fps would become way big also and why i'm using vdub is because imo it's very simple but good program and i use it for making the clip to avi so i could edit it in vegas and make it smaller there again.
1 question about megui settings would be that if i should look for settings that go for animations more or for real life and can u tell me what settings can i change in megui?
Actually picture is fine after vegas but x264 settigs i have kinda screw it
imo

[Sharktooth]

subme 7, 10 refs, trellis 2, me exhaustive, me range 32 are all killing your encoding speed.
use some SANE settings...

[foxyshadis]

What do you export it from vegas as? Huffyuv/lagarith? Lossy, like mjpeg, mpeg, divx, indeo, and so on will all ruin the final encode quality.

Don't bother with 3-pass, use quality encode, with quality of about 18 to 20 (14-16 if you want extremely sharp). Not only will it be more than twice as fast, the quality will be well-defined, but on the other hand bitrate won't. Get in the habit of thinking that bitrate doesn't matter, it'll serve you better in the long run. Bitrate only matters in any way when streaming or when fitting movies onto a CD, not when posting them for download.

To encode super-sharp video games in any lossy format, you're usually going to be disappointed in the final quality unless the bitrate is enormous. If you want this 1280x720 to look really amazingly good, expect to spend 2x or even 3x the bitrate, or else just live with it.

Edit: Looking over the sample, your mean quantizer is about 18 already. You'll need to use an insanely low Q to get the quality up much further; I doubt it'll really be worth it.