MeGUI: General Questions and Troubleshooting Thread

[bxyhxyh]

Yeah. You assumed correct
Then this page should be more recent. It seems that wikibooks page isn't updated since 2011.

https://web.archive.org/web/20150207.../X264_Settings

[Betsy25]

Anyone can still enlighten us which update server is the preferred one these days ?

I just switched to the dev server after months without any update on the stable server, and I got a bunch of updates presented.

After installing these & a restart, just as a test, I set back the update server to the stable one, checking for updates presented me with 'new' updates which were the months old versions I previously had ?

Please, which channel is adviced, and if the dev one is, what is the exact url these days ?

[Kurtnoise]

of course...if you use the stable server, you have to use the tools listed from this one. Same idea for the dev server...You can use the dev one w/o issues.

[nkk]

Where to get more topical x264 encoder presets?

[LigH]

You want to upload video to YouTube? Then forget optimal quality. YouTube will re-encode everything.

There are people who upload massively upscaled videos with high bitrates, which wastes a lot of bandwidth, to preserve a bit of chrominance resolution when YouTube will downscale it during its conversions ... for how much fame exactly?

[aegisofrime]

Hi, I'm being driven absolutely crazy by MeGUI crashing when it attempts to decode AAC files.

I have taken a look at the event viewer and found this:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MeGUI.exe
P2: 1.0.2525.0
P3: 54fc5b03
P4: bass.dll
P5: 2.4.4.0
P6: 4ad476cd
P7: c0000005
P8: 00002241
P9: 
P10:

Faulting application name: MeGUI.exe, version: 1.0.2525.0, time stamp: 0x54fc5b03
Faulting module name: bass.dll, version: 2.4.4.0, time stamp: 0x4ad476cd
Exception code: 0xc0000005
Fault offset: 0x00002241
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Faulting package full name: %14
Faulting package-relative application ID: %15

The source of the error is .NET Runtime so I have made sure that my runtime files are not corrupted and up to date. I'm running 4.5.2 which seems to be the latest, but this doesn't stop the crash.

I have also tried replacing the bass.dll files from the ones from the official website to no avail as well.

Does anyone have any ideas?

[tebasuna51]

@aegisofrime
Works fine for me.
Please put your logfile.

Try replacing the bass files from:
http://forum.doom9.org/showthread.ph...73#post1702473

[Taurus]

Just tried bassaudio (build in) and the one tebasuna51 linked to
with fdkaac, quaac and nero on some wav files.
All worked as expected.
Maybe your source files are a little suspicious?!
Could not try all kind of combinations, sources, but I'm using bassaudio quite often without any errors.

[hello_hello]

Is the following warning in MeGUI's log file some sort of x264 oddness, or is there a reason for it? The warning only appears for the first pass of a 2 pass encode, and only when "slow first pass" is not checked. The warning might be perfectly normal for all I know. I rarely use 2 pass encoding.

This is the log for the first pass. I've highlighted the relevant bits. That's probably be easier than explaining the problem.

Thanks.

[Warning] Log for job1 (video, test.avs -> )
-[Information] [25/03/15 4:41:15 PM] Started handling job
-[Information] [25/03/15 4:41:15 PM] Preprocessing
-[Information] [25/03/15 4:41:15 PM] Avisynth input script
--[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
--[NoImage] FFVideoSource("E:\test.mkv", cachefile="D:\test.ffindex", fpsnum=25, fpsden=1, threads=1)
--[NoImage] ColorMatrix(mode="Rec.709->Rec.601", clamp=0)
--[NoImage] Spline36Resize(960,540,1,0,-1,0)
--[NoImage] Trim(0,499)
-[Information] [25/03/15 4:41:15 PM] resolution: 960x540
-[Information] [25/03/15 4:41:15 PM] frame rate: 25/1
-[Information] [25/03/15 4:41:15 PM] aspect ratio: 16:9 (1.778)
-[Information] [25/03/15 4:41:15 PM] Job commandline: "C:\Program Files\MeGUI\tools\x264\x264.exe" --level 4.1 --preset slow --tune film --pass 1 --bitrate 2500 --stats "D:\test 2 pass.stats" --vbv-bufsize 78125 --vbv-maxrate 62500 --no-fast-pskip --colormatrix bt470bg --sar 1:1 --output NUL "D:\test.avs"
-[Information] [25/03/15 4:41:15 PM] Process started
-[Information] [25/03/15 4:41:15 PM] Standard output stream
-[Warning] [25/03/15 4:41:15 PM] Standard error stream
--[Information] [25/03/15 4:41:16 PM] avs [info]: 960x540p 1:1 @ 25/1 fps (cfr)
--[Information] [25/03/15 4:41:16 PM] x264 [info]: using SAR=1/1
--[Warning] [25/03/15 4:41:16 PM] x264 [warning]: VBV bitrate (62500) > level limit (50000)
--[Warning] [25/03/15 4:41:16 PM] x264 [warning]: VBV buffer (78125) > level limit (62500)
--[Information] [25/03/15 4:41:16 PM] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
--[Information] [25/03/15 4:41:16 PM] x264 [info]: profile Main, level 4.1
--[Information] [25/03/15 4:41:22 PM] x264 [info]: frame I:2 Avg QP:11.29 size: 23715
--[Information] [25/03/15 4:41:22 PM] x264 [info]: frame P:210 Avg QP:19.34 size: 19615
--[Information] [25/03/15 4:41:22 PM] x264 [info]: frame B:288 Avg QP:19.50 size: 8905
--[Information] [25/03/15 4:41:22 PM] x264 [info]: consecutive B-frames: 11.6% 30.4% 13.2% 44.8%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: mb I I16..4: 63.3% 0.0% 36.7%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: mb P I16..4: 25.5% 0.0% 0.0% P16..4: 62.8% 0.0% 0.0% 0.0% 0.0% skip:11.7%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: mb B I16..4: 4.9% 0.0% 0.0% B16..8: 34.9% 0.0% 0.0% direct:14.7% skip:45.5% L0:25.7% L1:41.4% BI:32.9%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: final ratefactor: 17.50
--[Information] [25/03/15 4:41:22 PM] x264 [info]: direct mvs spatial:63.9% temporal:36.1%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: coded y,uvDC,uvAC intra: 46.6% 67.9% 26.9% inter: 20.9% 33.1% 3.7%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: i16 v,h,dc,p: 26% 28% 28% 19%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 14% 25% 14% 6% 10% 5% 15% 4% 7%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: i8c dc,h,v,p: 53% 24% 17% 7%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: Weighted P-Frames: Y:6.7% UV:1.9%
--[Information] [25/03/15 4:41:22 PM] x264 [info]: kb/s:2692.42
--[Information] [25/03/15 4:41:22 PM] encoded 500 frames, 80.40 fps, 2692.42 kb/s
-[Information] [25/03/15 4:41:22 PM] Postprocessing
-[Information] [25/03/15 4:41:22 PM] Job completed

[LigH]

The explicit VBV limits seem to apply for high AVC profiles only. So this x264 warning might be more or less correct, provided that x264 does not yet assume to need High Profile for a turbo 1st pass.

[hello_hello]

Originally Posted by LigH

The explicit VBV limits seem to apply for high AVC profiles only. So this x264 warning might be more or less correct, provided that x264 does not yet assume to need High Profile for a turbo 1st pass.

Cheers. Yes I guess x264 is assuming baseline or main profile for the first pass. I wonder why it doesn't when it's a slow first pass? Not that it matters, I was just curious.

Thanks.

[LigH]

I wonder if that warning can be circumvented by explicitly adding "--profile high[10]" to the 1st pass call when these parameters with maximum VBV values are added too.
__

P.S.:

Just discussed briefly in IRC, turbo 1st pass always assumes Main Profile because 8x8dtc is disabled. This warning has a minor relevance, VBV values don't matter much during a 1st pass.

[sneaker_ger]

Originally Posted by LigH

This warning has a minor relevance, VBV values don't matter much during a 1st pass.

It has no relevance at all because x264 uses the --vbv- parameters instead of enforcing the level limit.

[cengizhan]

my megui suddenly stopped working. upon program start megui says that "Fatal Error. megui encountered a fatal errorr and may not be able to proceed. reason:index was outside the boundaries of the array". if i click ok, program closes immetiately.

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: megui.exe
Problem Signature 02: 1.0.2524.0
Problem Signature 03: 54e3c3f7
Problem Signature 04: MeGUI
Problem Signature 05: 1.0.2524.0
Problem Signature 06: 54e3c3f7
Problem Signature 07: 852
Problem Signature 08: 0
Problem Signature 09: System.IndexOutOfRangeException
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1055

[hello_hello]

Originally Posted by LigH

Just discussed briefly in IRC, turbo 1st pass always assumes Main Profile because 8x8dtc is disabled. This warning has a minor relevance, VBV values don't matter much during a 1st pass.

Thanks for the info. I figured it didn't matter but I was curious as to "why". Now I know.

Thanks.

[Solon8]

Maybe this is a stupid question, but I have to ask it to learn: if I add, say, 8 GB of RAM, will encoding wth MeGUI be any faster? I already have a good CPU (4.0 GHz) and 8 GB of RAM.
Would the improvement from 8 GB of RAM be trivial as maybe MeGUI only uses the CPU? Or would it help a lot and I could grasp a good number of FPS? Thank you.

[sneaker_ger]

No speed increase.

[Solon8]

Originally Posted by sneaker_ger

No speed increase.

OK, thank you for your answer.

[Zathor]

Originally Posted by cengizhan

my megui suddenly stopped working. upon program start megui says that "Fatal Error. megui encountered a fatal errorr and may not be able to proceed. reason:index was outside the boundaries of the array". if i click ok, program closes immetiately.

Please download this file and replace your megui.exe:
http://megui.org/auto/megui-core_2525.zip

Does it fix the problem?

[cengizhan]

Originally Posted by Zathor

Please download this file and replace your megui.exe:
http://megui.org/auto/megui-core_2525.zip

Does it fix the problem?

Yes.