MeGUI: General Questions and Troubleshooting Thread

[hello_hello]

Zathor,
I think I found a little bug or rounding error in MeGUI's aspect error calculations. I have the acceptable aspect error set to 0%.

I created a couple of custom input pixel aspect ratios to use in the script creator and combined with anamorphic encoding and "resize to selected mod", any resizing will result in an aspect error of between 0.00003% and 0.00005% being displayed. It doesn't matter how you resize (any mod or dimensions) MeGUI always shows a small aspect error.

As an example, I created two custom aspect ratios of 1.363636, which MeGUI then displays as 15:11, and 1.818181, which is displayed as 20:11 (I thought I'd try spending some time in the world of mpeg4 pixel aspect ratios). They both result in a small aspect error when anamorphic encoding is enabled with resizing.

According to my calculations, if I use the 15:11 aspect ratio with a PAL DVD, I should be able to resize it to exactly 720x528 with zero aspect error, and that's what MeGUI shows, so I assume the small error in the aspect calculations only applies to anamorphic encoding and resizing.

Thanks.

[LouieChuckyMerry]

Originally Posted by hello_hello

It still sounds like you're going about it the wrong way.

Man, good thing I wasn't driving a motor vehicle. Honestly, it really made sense in my head, as sad as that seems . Anyway, thanks again for the kind help, hello_hello, it's now clear. And I'll edit my templates, thus eliminating at least one way to embarrass myself in the future...

Originally Posted by hello_hello

PS. I kind of tried your script on the sample, but I don't have all the required plugins and I was getting a few errors which would have taken some time to sort out (things like a missing function in a script which probably require an additional plugin to fix), so I deleted Stab() and fiddled with a few things to make it work, but I think I saw the gist of it. It definitely looks better than the original video which is fairly horrible. I forgot you were probably working with animation. No nasty artefacts from using QTGMC on it yet?

I thought (ha ha ha) that this was only the case for using QTGMC to deinterlace animation? The QTGMC here is being used in progressive mode to reduce the shimmering, after the deinterlacing-field matching-decimating and doubled-line fixing (I get about 7% of the credit for the script, mostly the neatness ). I've not noticed any artifacts yet, but I've only watched two episodes in their entirety so there might be some yet. Given how impressively QTGMC reduces the shimmering, I'd happily live with the occasional blip (which given the source's low quality might not even be QTGMC's fault).

[hello_hello]

Originally Posted by LouieChuckyMerry

I thought (ha ha ha) that this was only the case for using QTGMC to deinterlace animation? The QTGMC here is being used in progressive mode to reduce the shimmering, after the deinterlacing-field matching-decimating and doubled-line fixing (I get about 7% of the credit for the script, mostly the neatness ). I've not noticed any artifacts yet, but I've only watched two episodes in their entirety so there might be some yet. Given how impressively QTGMC reduces the shimmering, I'd happily live with the occasional blip (which given the source's low quality might not even be QTGMC's fault).

Wasn't it you I was conversing with in the QTGMC thread a while back regarding using it for animation? Ah, yes it was. The bottom pic was courtesy of QTGMC in progressive mode, although if I remember correctly I played with a Simpson's sample at the time and it looked okay. I think I'm remembering that correctly, but if it's doing the job and not causing problems, you might as well use it.

For "video" artefacts don't stand out because they usually only happen for a tiny part of a single frame where there's movement and I'd normally only notice by accident when looking closely for something else, but for animation with large blocks of flat colour if there's artefacts they'll be more obvious. Maybe there's a QTGMC setting you could tweak. I haven't tried as I rarely encode animation myself. If you're not seeing any problems though.... don't worry about it.

[LouieChuckyMerry]

Long story truncated, after encoding Seasons 1-8 I decided to switch to 10-bit x264, so I figured I'd take the time to try and improve my script before starting over. It's weakest link was the deinterlacing-decimating (turns out the first season is bad tape transfers and the following seasons aren't much better, frequent patches of field-blending and inconsistent pulldown patterns the norm). After posting here I was incredibly lucky when someone with way more knowledge than I happened to be encoding the early-season Simpsons as well. (S)he did all the grunt work regarding the deinterlacing-field matching-decimating, evolving from the questionable use of QTGMC for deinterlacing-decimating to the final script above. It's surely not a perfect approach, but for an automated method, given the horrible source quality, I think it does a really really good job. Someday when I'm bored I'll attack frame-by-frame .

Also, I ran tests with variations of the above script--without NEEDI3, without QTGMC, etc.--and it just looks better as is. Somehow the NEEDI3-QTGMC combo does wonders with regards to the line-doubled fields and shimmering (I tested QTGMC with various presets, and the default was noticeably better than faster options). Now that you've reminded me that QTGMC denoises by default, and since I'm only about halfway through Season 2, I'll double-check my SMDegrain denoise settings to make sure they're not too strong. I ran tests before but what's a little extra paranoia, er, due diligence.

Ahhh, there might be an extra couple, but MinimumPluginsForSimpsonsSuperScript.

[AW-]

After 100's of MKv rips, one day I did a mkvmerge update on two computers and both will not do SAR resize.
I have same setup on two machines, If i set it to (704, 480) with force SAR 10:11 or in the custom command line --sar 10:11 It will come out 704 x 480 instead of 704x480 ~> 704x528.
All Sars are the same thing. I reinstalled and the same thing again...hmm

[Information] Log
-[Information] Versions
--[Information] [7/21/2015 6:36:03 AM] MeGUI: 2525
--[Information] [7/21/2015 6:36:03 AM] Operating System: Windows 7 Premium Edition x64 SP1 (6.1.65536.7601)
--[Information] [7/21/2015 6:36:03 AM] .Net Framework: 2.0.50727.5420
--[Information] [7/21/2015 6:36:03 AM] .Net Framework: 4.0.0.0
--[Information] [7/21/2015 6:36:04 AM] AviSynth: 2.5.8.5 (21-12-2008)
--[Information] [7/21/2015 6:36:04 AM] AvisynthWrapper: (02-01-2009)
--[Information] [7/21/2015 6:36:04 AM] Haali Matroska Splitter: 1.13.138.14 (14-04-2013)
--[Information] [7/21/2015 6:36:04 AM] Haali DSS2: (14-04-2013)
--[Information] [7/21/2015 6:36:04 AM] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [7/21/2015 6:36:04 AM] LinqBridge: 1.0.0.0 (28-05-2009)
--[Information] [7/21/2015 6:36:04 AM] MediaInfo: 0.7.72.0 (07-01-2015)
--[Information] [7/21/2015 6:36:04 AM] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [7/21/2015 6:36:04 AM] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [7/21/2015 6:36:04 AM] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [7/21/2015 6:36:04 AM] 7z: 9.20 (18-11-2010)
-[Information] Update detection
--[Information] [7/21/2015 6:36:04 AM] Using cached update config and server: http://megui.tmebi.de/stable/
--[Information] [7/21/2015 6:36:04 AM] No package requires an update
-[Information] Log for job63 (video, Bla blaClip.avs -> )
--[Information] [7/21/2015 6:38:26 AM] Started handling job
--[Information] [7/21/2015 6:38:26 AM] Preprocessing
--[Information] [7/21/2015 6:38:26 AM] Avisynth input script
---[NoImage] LoadPlugin("C:\Program Files (x86)\MeGUI_2418_x86\DGMPGDec 1.5.5\DGDecode.dll")
---[NoImage] #LoadPlugin("C:\Program Files (x86)\MeGUI_2418_x86\AviSynthPlugins\Tdeint.dll")
---[NoImage] LoadPlugin("C:\Program Files (x86)\MeGUI_2418_x86\AviSynthPlugins\TIVTC.dll")
---[NoImage] #LoadPlugin("C:\Program Files (x86)\MeGUI_2418_x86\AviSynthPlugins\mt_MaskTools.dll")
---[NoImage] #LoadPlugin("C:\Program Files (x86)\MeGUI_2418_x86\AviSynthPlugins\mt_masktools.dll")
---[NoImage] MPEG2Source("C:\DVD\Bla bla (1978) NT D5 CG\Bla bla\Clip\Clip.d2v", cpu=0)
---[NoImage] #import("C:\Program Files (x86)\MeGUI_2418_x86\AviSynthPlugins\Srestore.avs")
---[NoImage] #tdeint(order=-1)
---[NoImage] #tdeint(order=1)
---[NoImage] #srestore()
---[NoImage] tfm().TDecimate()
---[NoImage] #greyscale()
---[NoImage] #AssumeFPS("film")
---[NoImage] Crop(8, 0, -8, -6)
---[NoImage] BicubicResize(704, 480)
--[Information] [7/21/2015 6:38:26 AM] resolution: 704x480
--[Information] [7/21/2015 6:38:26 AM] frame rate: 24000/1001
--[Information] [7/21/2015 6:38:26 AM] aspect ratio: 4:3 (1.333)
--[Information] [7/21/2015 6:38:26 AM] custom command line: --sar 10:11
--[Information] [7/21/2015 6:38:26 AM] Job commandline: "C:\Program Files (x86)\MeGUI_2418_x86\tools\x264\avs4x264mod.exe" --level 3.1 --preset slow --tune film --pass 1 --bitrate 1800 --stats "C:\Program Files (x86)\MeGUI_2418_x86\logs\1011.stats" --deblock -3:-3 --keyint 240 --bframes 5 --ref 9 --vbv-bufsize 14000 --vbv-maxrate 14000 --ratetol 3.0 --rc-lookahead 60 --merange 32 --subme 10 --partitions all --trellis 2 --no-dct-decimate --no-fast-pskip --sar 10:11 --output NUL "C:\DVD\Bla bla (1978) NT D5\SBla bla\Bla blaClip\Bla blaClip.avs"
--[Information] [7/21/2015 6:38:27 AM] Process started
--[Information] [7/21/2015 6:38:27 AM] Standard output stream
---[Information] [7/21/2015 6:38:44 AM] avs [info]: AviSynth 2.58, buildec 22 2008 [08:46:51]
---[Information] [7/21/2015 6:38:44 AM] avs [info]: Video colorspace: YV12
---[Information] [7/21/2015 6:38:44 AM] avs [info]: Video resolution: 704x480
---[Information] [7/21/2015 6:38:44 AM] avs [info]: Video framerate: 24000/1001
---[Information] [7/21/2015 6:38:44 AM] avs [info]: Video framecount: 1364
---[Information] [7/21/2015 6:38:44 AM] avs4x26x [info]: "x264_64" - --level 3.1 --preset slow --tune film --pass 1 --bitrate 1800 --stats "C:\Program Files (x86)\MeGUI_2418_x86\logs\1011.stats" --deblock -3:-3 --keyint 240 --bframes 5 --ref 9 --vbv-bufsize 14000 --vbv-maxrate 14000 --ratetol 3.0 --rc-lookahead 60 --merange 32 --subme 10 --partitions all --trellis 2 --no-dct-decimate --no-fast-pskip --sar 10:11 --output NUL --frames 1364 --fps 24000/1001 --input-res 704x480 --input-csp i420
--[Information] [7/21/2015 6:38:27 AM] Standard error stream
---[Information] [7/21/2015 6:38:28 AM] raw [info]: 704x480p 10:11 @ 24000/1001 fps (cfr)
---[Information] [7/21/2015 6:38:28 AM] x264 [info]: using SAR=10/11
---[Information] [7/21/2015 6:38:28 AM] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
---[Information] [7/21/2015 6:38:28 AM] x264 [info]: profile Main, level 3.1
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: frame I:10 Avg QP:17.84 size: 62706
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: frame P:262 Avg QP:20.70 size: 27645
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: frame B:1092 Avg QP:24.80 size: 4595
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: consecutive B-frames: 1.2% 1.6% 7.9% 3.5% 4.4% 81.4%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: mb I I16..4: 11.7% 0.0% 88.3%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: mb P I16..4: 13.6% 0.0% 0.0% P16..4: 82.5% 0.0% 0.0% 0.0% 0.0% skip: 3.8%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: mb B I16..4: 1.5% 0.0% 0.0% B16..8: 28.9% 0.0% 0.0% direct:13.6% skip:56.0% L0:18.7% L1:32.4% BI:48.9%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: final ratefactor: 19.94
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: direct mvs spatial:99.4% temporal:0.6%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: coded y,uvDC,uvAC intra: 83.1% 79.4% 55.3% inter: 27.9% 16.6% 7.9%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: i16 v,h,dc,p: 24% 29% 33% 14%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 28% 10% 7% 8% 7% 8% 7% 9%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: i8c dc,h,v,p: 49% 24% 20% 7%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: Weighted P-Frames: Y:3.1% UV:0.0%
---[Information] [7/21/2015 6:38:44 AM] x264 [info]: kb/s:1812.35
---[Information] [7/21/2015 6:38:44 AM] encoded 1364 frames, 80.00 fps, 1812.35 kb/s
--[Information] [7/21/2015 6:38:44 AM] Postprocessing
---[Information] [7/21/2015 6:38:44 AM] Deleting intermediate files
--[Information] [7/21/2015 6:38:44 AM] Job completed

If you need any other settings info I may have left out, please ask. I'm sure it's something trivial I over looked.

Thanks in advance.

[LigH]

Useful ressource: http://members.optusnet.com.au/squid_80/sources/

To possibly build a custom binary of xvid_encraw, one may be interested in:

• xvid_encraw_src.zip containing a Matroska output module (and a HVS module);
• AviWriter_src.zip containing an OpenDML AVI writer based on VirtualDub sources

according to a message from the xvid-devel mailing list.

squid_80 used to be a member here; last posts in Sept. 2011

[tebasuna51]

Originally Posted by AW-

After 100's of MKv rips, one day I did a mkvmerge update on two computers and both will not do SAR resize.
I have same setup on two machines, If i set it to (704, 480) with force SAR 10:11 or in the custom command line --sar 10:11 It will come out 704 x 480 instead of 704x480 ~> 704x528.
All Sars are the same thing. I reinstalled and the same thing again...hmm

I don't see the problem.
Using --sar 10:11 don't force a pixel resize to 704x528 at encoder time, the resize is make at play time.

Use a mkv output, not NULL like in your log, and you can see the display size like 704x528.

[AW-]

Originally Posted by tebasuna51

I don't see the problem.
Use a mkv output, not NULL like in your log, and you can see the display size like 704x528.

Is there another format setting other than this one.

Screen shots and viewing still 704 x 480

Even tried typing .mkv in "Video Output" after the file name and still says NULL in logs....hmmm

Thanks again

[LigH]

A "NUL" output is usually the result of only a first pass of a 2-pass encode. If you want 2-pass, either put both the first and the second pass into the queue, or use the auto 2-pass option.

[AW-]

I've been using the automated 2nd pass, Thought that would be ok?


I always create my scripts with AvsPmod, Thought I'd double check the other settings as well.


I also tried Disabled 64 bit mode,



Thanks

[tebasuna51]

Originally Posted by AW-

Screen shots and viewing still 704 x 480

Maybe is a player (what?) problem.

Use MediaInfo to put a repport of your mkv output. You must see someting like:

Width                                    : 704 pixels
Height                                   : 480 pixels
Pixel aspect ratio                       : 0.909
Display aspect ratio                     : 4:3

The display of 704x480 internal pixels must be 4:3 (704x528 screen pixels)

[bxyhxyh]

Hello, what's the reason of choosing FluxSmooth 1.1a instead of 1.1b?
Was 1.1b problematic or just forgot to update it?

[hello_hello]

How does MeGUI cause x264 to lock a file that's not been encoded? It seems to happen quite a bit. As an example.....
I indexed with DGIndex. opened the d2v file in the script creator, played around with a bit of filtering in the script, then closed the script creator without saving the script. Nothing was loaded into MeGUI's video section for encoding, yet when I tried to delete the vob file, Windows told me it was locked. Unlocker agreed, and reported this:



Thanks.

[LigH]

Did you check in a task manager if a process of x264.exe runs in the background at this moment? I rather doubt that Unlocker is correct here, x264 should not lock any video source file while it is not busy encoding, it should not be in RAM any other time.

Uhm, well ... except you were playing with the deinterlacer options in the script builder, and x264 was just used to analyze it (I believe this is done by comparing the output of a very fast TFF and BFF encode of a tiny area with x264).

[hello_hello]

That's why I asked, because the file wasn't encoded so there was no reason for x264 to know it even existed, unless MeGUI is somehow doing something unexpected. It's definitely happened more than once before.... Unlocker reporting a file as locked by x264 even though I hadn't loaded a script to encode it. If Unlocker is getting it wrong, it seems a co-incidence that of all the exe's on my PC it could choose to incorrectly claim had locked the video, it just happened to pick x264. Can MeGUI somehow lock a file on behalf of another program, or is that theoretically impossible?

I'll probably need to wait until it happens again before I can answer those questions. I opened the same vob file again and when checking it with Unlocker it reported it was locked by MeGUI, and when I closed the script creator Unlocker reported as it no longer being locked. It doesn't happen all the time. Just now and then, but enough to be annoying.

I was playing around with de-interlacing but I never got MeGUI to analyse it, however I analysed it with MeGUI just now and Unlocker still says it's only locked by MeGUI. After closing the script creator it's unlocked again. Computers....

[Zathor]

x264 is only used in the encoding job so if you have not started any encoding it is not caused by MeGUI. Are you running any scripts outside of MeGUI? Are you able to reproduce it somehow?

[hello_hello]

I'll have a play but it seems to be fairly random. I'm 110% certain though, that for the sample in question all I did was create a d2v file and experiment with some filtering using the script creator. And I'm fairly certain the same thing has happened previously, but maybe I'm going mad......
I'll try to forget about it until it happens again, and then see if I can work out what's going on.

[hector1980]

hi
when i encode audio with neroaac some where in the middle like when HBO logo comes up or there is a jet or airplane sound it cut off suddenly and there is no sound at all after it please help me fix its driving me crazy
and how can i do batch in onecliker encoding?!
thanks

[Zathor]

Does it happen also with other encoders and/or input decoders?

Batch encoding in OC: drag&drop files or folders onto the input field or open a directory/folder.

[hector1980]

Originally Posted by Zathor

Does it happen also with other encoders and/or input decoders?

Batch encoding in OC: drag&drop files or folders onto the input field or open a directory/folder.

no just neroaac