PDA

View Full Version : Why does Batman Begins hate me?


shlap
8th February 2008, 16:42
The following method has worked great for me ripping a number of other HD-DVDs but for some reason, Batman Begins is giving me a hard time.

1.) Rebuilt the EVO into 1 file with EVODemux including only video and audio stream 0.

2.) Created graph for video ( Haali --> WMVideo Decoder)
Created graph for audio ( Haali --> Sonic Audio Decoder 4.3)

3.) Create 3 AVISynth Scripts, one for video, one for audio, and one to mux the two.
Video.avs = DirectShowSource("C:\Rips\Work Area\Batman\Video.grf",fps=23.976024,audio=false,video=true,framecount=201467)crop( 0, 128, 0, -152)
Audio.avs = DirectShowSource("C:\Rips\Work Area\Batman\Audio.grf",fps=23.976024,audio=true,video=false,framecount=201467)
Batman.avs = video = import("Video.avs")audio = import("Audio.avs")AudioDub(video,audio)

4.) Play Batman.avs in Zoom or Media Player and it plays great so I run it through MeGUI - PS3 Profile - here's the 1st & 2nd pass command line.
"D:\Program Files\megui\tools\x264\x264.exe" --pass 1 --bitrate 7672 --stats "C:\Rips\Work Area\Batman\Batman.stats" --level 4.1 --bframes 3 --direct auto --subme 1 --analyse none --vbv-bufsize 15000 --vbv-maxrate 25000 --me dia --merange 20 --threads auto --thread-input --sar 1:1 --progress --no-psnr --no-ssim --output NUL "C:\Rips\Work Area\Batman\Batman.avs"

"D:\Program Files\megui\tools\x264\x264.exe" --pass 2 --bitrate 7672 --stats "C:\Rips\Work Area\batman\batman.stats" --level 4.1 --ref 3 --mixed-refs --bframes 3 --b-rdo --bime --weightb --direct auto --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --vbv-bufsize 15000 --vbv-maxrate 25000 --me umh --merange 24 --threads auto --thread-input --sar 2543:2500 --progress --no-psnr --no-ssim --output "C:\Rips\Work Area\batman\batman.mkv" "C:\Rips\Work Area\batman\batman.avs"

As you can see, I'm using 2pass with a bitrate of 7672. When the encode starts I get thousands of
x264 [warning]: VBV underflow (-1575458 bits) warnings, my mkv always ends up being around 23GIG, and the video is just a pixelated mess, it looks horrible!

Did anyone else run into this issue this flick? I had the same sort of issue with Breach but found it was due to using the wrong framerate (thanks Dark Shikari). I'm pretty sure I've got the framerate right on this one. Any suggestions?

CruNcher
8th February 2008, 18:03
Hmm underflow ??? i would have maybe expected overflow because of Darks New AQ and these settings but underflow??? try with --aq-strength 0

Sharktooth
8th February 2008, 18:12
are you using the latest megui?
if so, have you updated all the packages (expecially x264) thru the auto-update?

Sagittaire
8th February 2008, 19:07
Why use vbv if you make mkv ... ???

vbv is usefull only for hardware decoding and actual x264 build don't respect the vbv value.

LoRd_MuldeR
8th February 2008, 19:36
Why use vbv if you make mkv ... ???
AFAIK there are Standalone Players with MKV support now ;)

Sharktooth
8th February 2008, 20:36
the x264 build that comes with megui includes an experimental VBV patch

shlap
8th February 2008, 23:01
Hmm underflow ??? i would have maybe expected overflow because of Darks New AQ and these settings but underflow??? try with --aq-strength 0


Thanks, I'll give this a try when I get home.

Why use vbv if you make mkv ... ???

vbv is usefull only for hardware decoding and actual x264 build don't respect the vbv value.

I play the resulting file from the PS3 after using MKV2VOB. For some reason this works great. If I take the h264 and AC3 files generated by x264.exe and try to mux them directly into a vob using ffmpeg, the PS3 won't play it.


are you using the latest megui?
if so, have you updated all the packages (expecially x264) thru the auto-update?


Yep, I have the latest x264.exe updated via meGUI.

Dark Shikari
8th February 2008, 23:36
Hmm underflow ??? i would have maybe expected overflow because of Darks New AQ and these settings but underflow??? try with --aq-strength 0Underflow means overflow; i.e. the VBV fills up, and it violates VBV restriction. Its how akupenguin decided to name it, because he goes by how the decoder views it, not the encoder.

AQ isn't the problem; the problem is that 2pass does not strictly obey VBV. Try using a version of x264 with the 2pass VBV patch. Techouse's site (http://x264.tk/) has builds with this patch.

Sharktooth
9th February 2008, 05:07
the x264 version he used already has the VBV patch...

survivant001
9th February 2008, 15:50
I have the same problem with a movie too. Dr Stange (anime)

here my post

http://forum.doom9.org/showthread.php?p=1098148#post1098148

i'm using x264 build (http://forum.doom9.org/showthread.php?p=1095545#post1095545)

x264_aq_var.48.diff
http://forum.doom9.org/showthread.php?t=132760
x264.gaussian.cplxblur.01.diff
Dark Shikari: - gaussian cplxblur: gives a tiny improvement in 2pass ratecontrol
x264_me-prepass_DeathTheSheep.01.diff
http://forum.doom9.org/showthread.php?p=1093523
x264_2pass_vbv.4.MatMaul.diff
http://mailman.videolan.org/pipermai...ry/004015.html
x264_hrd_pulldown.04_interlace.diff
- HRD and pulldown for HD compatibility, updated patch for interlacing
http://forum.doom9.org/showthread.ph...19#post1047919