MeGUI: General Questions and Troubleshooting Thread

[leon]

AviSynth does not natively support 16 bit, only 8 bit. It has to put those extra 8 bits somewhere - that's why the picture resolution doubles (either stacked or interleaved). MeGUI probably does not (fully) support this hack, hence the garbled preview. Is MeGUI using avs4x264mod for piping? Then using e.g. "--input-depth 16" as an additional cli parameter for x264 might produce correct output even if the preview is garbled. Make sure to use interleaved 16 bit hack (like in your screenshot), not vertically stacked.

Hi
in the other thread (MeGUI: bug reports and feature requests) you can see I've add "Ditherpost()" to the end of my script in order to have a 8bit output but it has problems too.

[leon]

I think..... and someone could correct me if I'm wrong....

Filtering is usually added to a script in the order you want it applied. Some filtering (noise removal, IVTC) is effectively applied to a group of frames. If you put Trim() first, it might effect the output a tad, so as a general rule you'd apply other filtering first, then use Trim() to output only the required frames.

Mind you, I sometimes use Trim() to apply different filtering to different parts of a script, so mostly I'd add the "apply to everything" filtering, followed by the trims, maybe followed by filtering which is just applied to each frame independently. Something like this (just as an example):

Thank you I tested that method and it was 1 FPS faster (saved me 30 mins :) )

[sneaker_ger]

There's no way for the x264 encoder to automatically determine the correct bitdepth, is there?

I'd assume MeGUI's x264 encoder configuration would need an option along with the one for using the 10 bit encoder in order to output 16 bit. One which gets MeGUI to use an appropriate commandline including "--input-depth 16" etc.
AFAIK avs4x264mod automatically handles high bit if it sees the --input-depth 9...16 parameter being uses. No additional settings should be required. (Except one that makes MeGUI use avs4x264mod in the first place.)

As I've done almost no 10 bit encoding, could I ask why? The Dither plugin seems to use "vertically stacked" by default. If you add nothing but "Dither_convert_8_to_16 ()" to a script and use MeGUI's preview, the 16 bit result seems to be "stacked" (video on top, green on bottom).
x264 expects interleaved.

One last question.... aside from MeGUI's preview, how do you determine which method is being used?
You read the documentations of your AviSynth plugins, of course.

[hello_hello]

You read the documentations of your AviSynth plugins, of course.

If you don't know, you only had to say so. ;)

[leon]

MeGUI encountered an error after 9 HOURS encoding :angry::angry::angry:

[Error] Log
-[Information] Versions

-[Error] Update detection
--[Information] [8/12/2014 11:33:06 PM] Automatic update is disabled
--[Information] [8/12/2014 11:33:06 PM] Using cached update config and server: http://megui.org/auto/
--[Information] [8/12/2014 11:33:06 PM] No package requires an update
--[Information] [8/13/2014 1:46:40 AM] Connected to server: http://megui.xvidvideo.ru/auto/
--[Information] [8/13/2014 1:46:40 AM] No package requires an update
--[Error] [8/13/2014 11:52:03 AM] Could not save update package settings
-[Information] Log for job1 (video, Noah 2014 720p 2.avs -> Noah 2014 720p 2.mkv)
--[Information] [8/13/2014 1:53:36 AM] Started handling job
--[Information] [8/13/2014 1:53:36 AM] Preprocessing
--[Information] [8/13/2014 1:53:36 AM] Avisynth input script

---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] #denoise
---[NoImage] #resize
---[NoImage] ColorMatrix(mode="Rec.709->Rec.601", clamp=0, threads=0)
---[NoImage] FFT3DGPU(sharpen=0.2,plane=4,mode=1,interlaced=false)
---[NoImage] MosquitoNR(strength=10,restore=128,radius=2,threads=0)
---[NoImage] f3kdb(range=23,sample_mode=2,dither_algo=3,grainY=90,grainC=90,dynamic_grain=true,Y=90,Cb=90,Cr=90,blur_first=true,keep_tv_range=false)
---[NoImage] Tweak(hue=0,sat=1.0,bright=0,cont=1.0,coring=false,startHue=0,endHue=360,maxSat=150,minSat=0,interp=16,dither=true)
---[NoImage] RemoveGrain(mode=2,modeU=2,modeV=2)
---[NoImage] Gradfun3()
---[NoImage] Trim(3076, 189200)
--[Information] [8/13/2014 1:53:39 AM] resolution: 1280x696
--[Information] [8/13/2014 1:53:39 AM] frame rate: 24000/1001
--[Information] [8/13/2014 1:53:39 AM] aspect ratio: 160:87 (1.839)
--[Information] [8/13/2014 1:53:39 AM] custom command line: --bframes 3 --ref 6
--[Information] [8/13/2014 1:53:39 AM] Job commandline: "C:\Program Files\MeGUI\tools\x264_10b\avs4x264mod.exe" -L "C:\Program Files\MeGUI\tools\x264_10b\x264-10b_64.exe" --level 4.1 --preset slower --crf 31.0 --keyint 240 --ref 6 --qpmin 10 --qpmax 51 --vbv-bufsize 78125 --vbv-maxrate 62500 --rc-lookahead 75 --aq-strength 1.1 --no-fast-pskip --stitchable --colorprim bt709 --transfer bt709 --colormatrix bt709 --sar 1:1 --output "F:\Users\Admin\Desktop\Videos\New folder\2.mkv" "F:\Users\Admin\Desktop\Videos\New folder\2.avs"
--[Information] [8/13/2014 1:53:39 AM] Process started
--[Information] [8/13/2014 1:53:39 AM] Standard output stream
--[Information] [8/13/2014 1:53:39 AM] Standard error stream
---[Information] [8/13/2014 1:54:00 AM] raw [info]: 1280x696p 1:1 @ 24000/1001 fps (cfr)
---[Information] [8/13/2014 1:54:00 AM] x264 [info]: using SAR=1/1
---[Information] [8/13/2014 1:54:00 AM] x264 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT
---[Information] [8/13/2014 1:54:00 AM] x264 [info]: profile High 10, level 4.1, 4:2:0 10-bit
---[Information] [8/13/2014 1:58:18 AM] x264 [info]: frame I:16 Avg QP:39.29 size: 32945
---[Information] [8/13/2014 1:58:18 AM] x264 [info]: frame P:314 Avg QP:42.97 size: 5108
---[Information] [8/13/2014 1:58:18 AM] x264 [info]: frame B:790 Avg QP:47.87 size: 1254
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: consecutive B-frames: 3.3% 4.3% 11.0% 81.4%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: mb I I16..4: 22.8% 72.4% 4.8%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: mb P I16..4: 2.8% 4.0% 0.1% P16..4: 39.7% 2.2% 7.4% 0.0% 0.0% skip:43.9%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: mb B I16..4: 0.1% 0.3% 0.0% B16..8: 26.2% 0.9% 0.1% direct: 0.3% skip:72.1% L0:40.9% L1:58.2% BI: 0.8%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: 8x8 transform intra:64.8% inter:82.9%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: direct mvs spatial:99.2% temporal:0.8%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: coded y,uvDC,uvAC intra: 36.9% 25.2% 0.7% inter: 3.2% 1.5% 0.0%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: i16 v,h,dc,p: 15% 22% 7% 56%
---[Information] [8/13/2014 1:58:19 AM] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 6% 5% 7% 11% 17% 14% 15% 10% 13%
---[Information] [8/13/2014 1:58:20 AM] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 6% 5% 4% 10% 18% 14% 16% 10% 16%
---[Information] [8/13/2014 1:58:20 AM] x264 [info]: i8c dc,h,v,p: 41% 27% 8% 25%
---[Information] [8/13/2014 1:58:20 AM] x264 [info]: Weighted P-Frames: Y:9.6% UV:7.3%
---[Information] [8/13/2014 1:58:20 AM] x264 [info]: ref P L0: 60.6% 20.9% 11.4% 3.2% 3.4% 0.5% 0.0%
---[Information] [8/13/2014 1:58:20 AM] x264 [info]: ref B L0: 89.7% 5.7% 3.1% 0.9% 0.5%
---[Information] [8/13/2014 1:58:20 AM] x264 [info]: ref B L1: 97.0% 3.0%
---[Information] [8/13/2014 1:58:20 AM] x264 [info]: kb/s:534.58
---[Information] [8/13/2014 1:58:20 AM] encoded 1120 frames, 4.07 fps, 534.72 kb/s
--[Information] [8/13/2014 1:58:20 AM] Process exits with error: 0xFFFFFFFF (-1)
--[Information] Deleting aborted output
---[Information] [8/13/2014 1:58:21 AM] Delete aborted output set: False
--[Information] [8/13/2014 1:58:21 AM] Job completed
--[Information] [8/13/2014 1:58:21 AM] Current job was aborted
-[Error] Log for job1 (video, 2.avs -> 2.mkv)
--[Information] [8/13/2014 1:59:38 AM] Started handling job
--[Information] [8/13/2014 1:59:38 AM] Preprocessing
--[Information] [8/13/2014 1:59:38 AM] Avisynth input script
---[NoImage] # Set DAR in encoder to 160 : 87. The following line is for automatic signalling
---[NoImage] global MeGUI_darx = 160
---[NoImage] global MeGUI_dary = 87
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\ColorMatrix.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\dither.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\mvtools2.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\LoadDll.dll")
---[NoImage] LoadDll("F:\Program Files (x86)\AviSynth 2.5\plugins\libfftw3f-3.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\MaskTools.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\FFT3dGPU.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\avstp.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\dfttest.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\hqdn3d.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\nnedi3.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\RepairSSE2.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\Deen.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\flash3kyuu_deband.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\svpflow2.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\svpflow1.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\RemoveGrainSSE2.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\aWarpSharp.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\deblock.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\DctFilter.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\mt_masktools-26.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\gradfun2db.dll")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\MosquitoNR.dll")
---[NoImage] Import("C:\Program Files\MeGUI\tools\avisynth_plugin\EdgeCleaner.avs")
---[NoImage] Import("F:\Program Files\Hybrid\avisynthPlugins\Dehalo_alpha_mt.avsi")
---[NoImage] Import("C:\Program Files\MeGUI\tools\avisynth_plugin\QTGMC-3.33d.avsi")
---[NoImage] Import("F:\Program Files\Hybrid\avisynthPlugins\Deblock_QED.avs")
---[NoImage] Import("C:\Program Files\MeGUI\tools\avisynth_plugin\dither.avsi")
---[NoImage] Import("C:\Program Files\MeGUI\tools\avisynth_plugin\mt_xxpand_multi.avsi")
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
---[NoImage] FFVideoSource("K:\My Files\2.mkv", cachefile="F:\Users\Admin\Desktop\Videos\New folder\2.mkv.ffindex", fpsnum=24000, fpsden=1001)
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] #denoise
---[NoImage] #resize
---[NoImage] ColorMatrix(mode="Rec.709->Rec.601", clamp=0, threads=0)
---[NoImage] FFT3DGPU(sharpen=0.2,plane=4,mode=1,interlaced=false)
---[NoImage] MosquitoNR(strength=10,restore=128,radius=2,threads=0)
---[NoImage] f3kdb(range=23,sample_mode=2,dither_algo=3,grainY=90,grainC=90,dynamic_grain=true,Y=90,Cb=90,Cr=90,blur_first=true,keep_tv_range=false)
---[NoImage] Tweak(hue=0,sat=1.0,bright=0,cont=1.0,coring=false,startHue=0,endHue=360,maxSat=150,minSat=0,interp=16,dither=true)
---[NoImage] RemoveGrain(mode=2,modeU=2,modeV=2)
---[NoImage] Gradfun3()
---[NoImage] Trim(3076, 189200)
--[Information] [8/13/2014 1:59:41 AM] resolution: 1280x696
--[Information] [8/13/2014 1:59:41 AM] frame rate: 24000/1001
--[Information] [8/13/2014 1:59:41 AM] aspect ratio: 160:87 (1.839)
--[Information] [8/13/2014 1:59:41 AM] custom command line: --bframes 3 --ref 6
--[Information] [8/13/2014 1:59:41 AM] Job commandline: "C:\Program Files\MeGUI\tools\x264_10b\avs4x264mod.exe" -L "C:\Program Files\MeGUI\tools\x264_10b\x264-10b_64.exe" --level 4.1 --preset slower --crf 31.5 --keyint 240 --ref 6 --qpmin 10 --qpmax 51 --vbv-bufsize 78125 --vbv-maxrate 62500 --rc-lookahead 75 --aq-strength 1.1 --no-fast-pskip --stitchable --colorprim bt709 --transfer bt709 --colormatrix bt709 --sar 1:1 --output "F:\Users\Admin\Desktop\Videos\New folder\2.mkv" "F:\Users\Admin\Desktop\Videos\New folder\2.avs"
--[Information] [8/13/2014 1:59:41 AM] Process started
--[Information] [8/13/2014 1:59:41 AM] Standard output stream
---[Information] [8/13/2014 11:51:26 AM] avs [info]: AviSynth 2.60, build:Sep 18 2013 [17:36:36]
---[Information] [8/13/2014 11:51:26 AM] avs [info]: Video colorspace: YV12
---[Information] [8/13/2014 11:51:26 AM] avs [info]: Video resolution: 1280x696
---[Information] [8/13/2014 11:51:26 AM] avs [info]: Video framerate: 24000/1001
---[Information] [8/13/2014 11:51:26 AM] avs [info]: Video framecount: 186125
---[Information] [8/13/2014 11:51:26 AM] avs4x264 [info]: "C:\Program Files\MeGUI\tools\x264_10b\x264-10b_64.exe" - --level 4.1 --preset slower --crf 31.5 --keyint 240 --ref 6 --qpmin 10 --qpmax 51 --vbv-bufsize 78125 --vbv-maxrate 62500 --rc-lookahead 75 --aq-strength 1.1 --no-fast-pskip --stitchable --colorprim bt709 --transfer bt709 --colormatrix bt709 --sar 1:1 --output "F:\Users\Admin\Desktop\Videos\New folder\2.mkv" --frames 186125 --fps 24000/1001 --input-res 1280x696 --input-csp i420
--[Error] [8/13/2014 1:59:41 AM] Standard error stream
---[Information] [8/13/2014 2:00:02 AM] raw [info]: 1280x696p 1:1 @ 24000/1001 fps (cfr)
---[Information] [8/13/2014 2:00:02 AM] x264 [info]: using SAR=1/1
---[Information] [8/13/2014 2:00:02 AM] x264 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT
---[Information] [8/13/2014 2:00:02 AM] x264 [info]: profile High 10, level 4.1, 4:2:0 10-bit
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: frame I:1624 Avg QP:39.23 size: 21092
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: frame P:46749 Avg QP:42.88 size: 3872
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: frame B:107979 Avg QP:44.91 size: 1131
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: consecutive B-frames: 3.7% 5.3% 22.1% 68.9%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: mb I I16..4: 30.5% 66.3% 3.2%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: mb P I16..4: 5.9% 6.1% 0.1% P16..4: 32.6% 1.6% 4.3% 0.0% 0.0% skip:49.3%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: mb B I16..4: 0.2% 0.3% 0.0% B16..8: 25.1% 0.7% 0.1% direct: 0.2% skip:73.5% L0:38.2% L1:61.3% BI: 0.6%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: 8x8 transform intra:54.8% inter:87.9%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: direct mvs spatial:99.9% temporal:0.1%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: coded y,uvDC,uvAC intra: 21.7% 17.9% 0.6% inter: 1.7% 1.2% 0.0%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: i16 v,h,dc,p: 21% 23% 6% 51%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 5% 19% 10% 14% 11% 13% 9% 11%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 6% 6% 10% 16% 14% 15% 10% 16%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: i8c dc,h,v,p: 57% 25% 6% 12%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: Weighted P-Frames: Y:7.8% UV:6.3%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: ref P L0: 56.9% 21.3% 13.5% 3.5% 3.5% 1.3% 0.1%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: ref B L0: 90.6% 5.2% 2.7% 1.0% 0.5%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: ref B L1: 97.2% 2.8%
---[Information] [8/13/2014 11:51:26 AM] x264 [info]: kb/s:413.86
---[Information] [8/13/2014 11:51:26 AM] aborted at input frame 156433, output frame 156351
---[Information] [8/13/2014 11:51:26 AM] encoded 156351 frames, 4.40 fps, 413.86 kb/s
---[Error] [8/13/2014 11:51:26 AM] avs [error]: Error occurred while writing frame 156434
---[Information] [8/13/2014 11:51:26 AM] (Maybe x264 closed)
--[Error] [8/13/2014 11:51:26 AM] Process exits with error: 0xFFFFFFFF (-1)
--[Warning] [8/13/2014 11:51:26 AM] The 64 bit mode of x264 is enabled. Depending on the error it may help to disable it in the MeGUI settings.
--[Information] [8/13/2014 11:51:26 AM] Job completed
-[Information] [8/13/2014 11:51:59 AM] Shutdown initiated

[hello_hello]

Given you had --stitchable in the commandline I assume you found somewhere close to the end of the output MKV to split it with MKVMergeGUI?
I assume you then added Trim() to the script to start encoding from the point where the first MKV was split (where it now ends)? Better than starting again. :)

As I noticed you've added it to the commandline and I have no idea what it does..... can someone tell me when adding --input-res to the commandline is necessary?
Obviously it specifies the input resolution but the x264 help file doesn't explain why you'd need to. Maybe I'm missing the obvious...

[leon]

Given you had --stitchable in the commandline I assume you found somewhere close to the end of the output MKV to split it with MKVMergeGUI?
I assume you then added Trim() to the script to start encoding from the point where the first MKV was split (where it now ends)? Better than starting again. :)

I didn't split anything I simply added Trim() to the end of script to skip intro and credit.
this error happened before.even after using x264 32bit it doesn't fix.
I've saw the same error in other posts but there were no proper answer.

[leon]

Hi
I have a few videos like this :

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=24
Duration : 11mn 34s
Bit rate : 3 707 Kbps
Maximum bit rate : 15.0 Mbps
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate : 25.000 fps
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.358
Time code of first frame : 20:33:31:22
Time code source : Group of pictures header
Stream size : 307 MiB (92%)


but when I use "analyze" MeGUI detects it as progressive.
is it possible for Mediainfo to be wrong?
the video's been recorded and I think it suppose to be interlaced.

I'm still waiting for an answer to my last post :)

[leon]

the video's been recorded and I think it suppose to be interlaced.

yes I was correct and the video's interlaced.

I tried to deinterlace it with different deinterlacers and here's its result:

the original frame :
http://i59.tinypic.com/23vyct0.jpg

deinterlaced with TDeint :
http://i62.tinypic.com/2z80ojs.jpg

deinterlaced with Yadif :
http://i59.tinypic.com/309irk4.jpg

deinterlaced with FieldDeinterlace :
http://i59.tinypic.com/28chfyx.jpg

1)why MeGUI couldn't detect it as interlaced ?
2)why some of the numbers are incorrect for some deinterlacers ?

[AMED]

I'm still waiting for an answer to my last post :) Your probably not going to get a answer to this since it looks like you using a pirated source

-[Information] Log for job1 (video, Noah 2014 720p 2.avs -> Noah 2014 720p 2.mkv)

[LigH]

1) It is indeed possible that video with progressive content was encoded in interlaced encoder mode. Some studios always keep their encoders in interlaced mode, because it would return really bad quality to have interlaced video encoded in progressive encoder mode. MediaInfo can only report how the video was encoded by reading header flags, but cannot analyze the content.

MeGUI tries to analyze the content. But it can't do that with the whole frame, it would take too long. It takes only a small area. If you are unlucky, this small area has no details which would show any combing. So you can't rely on MeGUI's automatic analysis either. Only your eyes are reliable enough when you step frame-by-frame through a Bob() result.

2) Some "Deinterlacers" do a very fast but really bad job. Others take much effort in using content from neighborhood frames to restore content but may be too slow for realtime use.

[hello_hello]

AFAIK avs4x264mod automatically handles high bit if it sees the --input-depth 9...16 parameter being uses. No additional settings should be required. (Except one that makes MeGUI use avs4x264mod in the first place.)


x264 expects interleaved.

I'm still a little confused as to when you'd send high bitdepth video directly to the encoder or when you'd need to use avs4x264mod etc. I guess I need to research the topic some more.

You read the documentations of your AviSynth plugins, of course.

If you don't know, you only had to say so. ;)

Sorry, in hindsight my reply may have seemed a little smart-arse-ish. It wasn't intended that way, just as a joke.

[leon]

Your probably not going to get a answer to this since it looks like you using a pirated source

-[Information] Log for job1 (video, Noah 2014 720p 2.avs -> Noah 2014 720p 2.mkv)

Hi
if you mean downloaded, no it's not downloaded.
maybe the way I obtained it would consider "pirated" but I'm not sure.

and pirated or not it doesn't matter because this problem's occurred several times with various sources and there were no answer to it.

[leon]

1) It is indeed possible that video with progressive content was encoded in interlaced encoder mode. Some studios always keep their encoders in interlaced mode, because it would return really bad quality to have interlaced video encoded in progressive encoder mode. MediaInfo can only report how the video was encoded by reading header flags, but cannot analyze the content.

MeGUI tries to analyze the content. But it can't do that with the whole frame, it would take too long. It takes only a small area. If you are unlucky, this small area has no details which would show any combing. So you can't rely on MeGUI's automatic analysis either. Only your eyes are reliable enough when you step frame-by-frame through a Bob() result.

2) Some "Deinterlacers" do a very fast but really bad job. Others take much effort in using content from neighborhood frames to restore content but may be too slow for realtime use.

Thank you.
1)why some of the numbers are different for Yadif and TDeint ?
I used TFF for both.
2)which deinterlacer is better in the pictures?

[AMED]

Hi
if you mean downloaded, no it's not downloaded.
maybe the way I obtained it would consider "pirated" but I'm not sure.

and pirated or not it doesn't matter because this problem's occurred several times with various sources and there were no answer to it. If you haven't brought it and it's not public domain then most likely it's pirated.

Try disabling the avisynth lines below (put # at the start of the line) and test again. If encoding completes successfully try the encode again enabling the first 2 lines below and test again, rinse and repeat adding the next 2 lines in.

FFT3DGPU(sharpen=0.2,plane=4,mode=1,interlaced=false)
MosquitoNR(strength=10,restore=128,radius=2,threads=0)
f3kdb(range=23,sample_mode=2,dither_algo=3,grainY=90,grainC=90,dynamic_grain=true,Y=90,Cb=90,Cr=90,blur_first=true,keep_tv_range=false)
Tweak(hue=0,sat=1.0,bright=0,cont=1.0,coring=false,startHue=0,endHue=360,maxSat=150,minSat=0,interp=16,dither=true)
RemoveGrain(mode=2,modeU=2,modeV=2)
Gradfun3()

Hopefully this will allow you to narrow down the problem.

[szabi]

Hi

I have an mpg2 video.
File Indexer of MeGui was used on it.
After MeGui automatically loaded it to Avisynth script creator, and video was displayed.
When script is saved I got an error message: There is no function named "DGDecode_mpeg2source"
Plugin is loaded of course by LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll") and available in the directory.
If a change the input to simple "MPEG2Source" it is working.
What is wrong in first case?
Are there any qulity lost using simple "MPEG2Source"?

bye
szabi

[AMED]

Post your full log please.

Sent from my Nokia 925 using Tapatalk.

[szabi]

Here the full log:
[Error] Log
-[Information] Versions
--[Information] [2014.08.24. 13:37:26] MeGUI: 2507
--[Information] [2014.08.24. 13:37:26] Operating System: Windows 8.1 Professional Edition x64 (6.3.0.9600)
--[Information] [2014.08.24. 13:37:26] .Net Framework: 2.0.50727.4927
--[Information] [2014.08.24. 13:37:26] .Net Framework: 4.0.0.0
--[Information] [2014.08.24. 13:37:26] AviSynth: 2.6.0.4 (28-09-2013)
--[Information] [2014.08.24. 13:37:26] AvisynthWrapper: (02-01-2009)
--[Information] [2014.08.24. 13:37:26] Haali Matroska Splitter: 1.13.138.14 (14-04-2013)
--[Information] [2014.08.24. 13:37:26] Haali DSS2: (14-04-2013)
--[Information] [2014.08.24. 13:37:26] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [2014.08.24. 13:37:26] LinqBridge: 1.0.0.0 (28-05-2009)
--[Information] [2014.08.24. 13:37:26] MediaInfo: 0.7.69.0 (24-04-2014)
--[Information] [2014.08.24. 13:37:26] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [2014.08.24. 13:37:26] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [2014.08.24. 13:37:26] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [2014.08.24. 13:37:26] 7z: 9.20 (18-11-2010)
-[Information] Update detection
--[Information] [2014.08.24. 13:37:27] Using cached update config and server: http://megui.org/auto/
--[Information] [2014.08.24. 13:37:27] No package requires an update
-[Information] FileIndexer
--[Information] [2014.08.24. 13:38:47] MediaInfo
---[Information] [2014.08.24. 13:38:47] File: D:\movie\demo.mpg
---[Information] General
----[Information] Format: MPEG-PS
----[Information] FormatString: MPEG-PS
----[Information] FileSize: 13072388
----[Information] PlayTime: 00:00:16.560
---[Information] Video
----[Information] ID: 224
----[Information] StreamOrder: 0
----[Information] Width: 720
----[Information] Height: 576
----[Information] FrameCount: 414
----[Information] FrameRate: 25.000
----[Information] FrameRateOriginal:
----[Information] FrameRateMode:
----[Information] ScanType: Interlaced
----[Information] Codec: MPEG-2V
----[Information] CodecString: MPEG-2 Video
----[Information] Bits Depth: 8
----[Information] Format: MPEG Video
----[Information] AspectRatio: 1.333
----[Information] AspectRatioString: 4:3
----[Information] Delay: 245.144
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
---[Information] Audio
----[Information] ID: 192
----[Information] StreamOrder: 1
----[Information] Format: MPEG Audio
----[Information] FormatProfile: Layer 2
----[Information] FormatSettingsSBR:
----[Information] FormatSettingsPS:
----[Information] SamplingRate: 48000
----[Information] SamplingRateString: 48.0 KHz
----[Information] Channels: 2
----[Information] ChannelsString: 2 channels
----[Information] ChannelPositionsString2:
----[Information] BitRateMode: CBR
----[Information] Delay: 245.144
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
-[Information] Log for job1 (idx, demo.mpg -> demo.d2v)
--[Information] [2014.08.24. 13:38:52] Started handling job
--[Information] [2014.08.24. 13:38:52] Preprocessing
--[Information] [2014.08.24. 13:38:52] Job commandline: "C:\Program Files (x86)\MeGUI\tools\dgindex\dgindex.exe" -SD=< -AIF=<D:\movie\demo.mpg< -OF=<D:\movie\demo< -FO=0 -exit -hide -OM=0
--[Information] [2014.08.24. 13:38:52] Process started
--[Information] [2014.08.24. 13:38:52] Standard output stream
--[Information] [2014.08.24. 13:38:52] Standard error stream
--[Information] [2014.08.24. 13:38:52] Running auto force film
---[Information] [2014.08.24. 13:38:52] Film percentage: -1
--[Information] [2014.08.24. 13:38:52] Postprocessing
---[Information] [2014.08.24. 13:38:54] Deleting intermediate files
----[Information] [2014.08.24. 13:38:54] Successfully deleted D:\movie\demo.log
--[Information] [2014.08.24. 13:38:54] Job completed
-[Error] MediaInfo
--[Error] [2014.08.24. 13:39:15] Error parsing media file D:\\movie\demo.avs
---[NoImage] Script error: there is no function named "DGDecode_mpeg2source"
---[NoImage] (D:\\movie\demo.avs, line 2)

bye
szabi

[MKVCrazy]

I am using MeGUI 2507 and lately I notice the output file size is totally different from the estimate calculated in the built-in Bitrate Calculator. Is there a better way for me to predict the output size? I am doing x265 converts in ABR mode. The output size is totally different. Sometimes it's less than the target and sometimes it's more than the target size. Inconsistent. Is this due to the meGUI or something else?

[LigH]

It is almost never the fault of the GUI calling the encoder, but rather the "fault" of the encoder, or the bitrate control technique as such, in relation to the material to be encoded.

1-pass ABR ist hard to control: the encoder can only regulate the output quantization of future frames after it discovered that previous frames already had overshot or undershot the target bitrate. The GUI can only assume the expected output if the bitrate were as constant as possible; but most video material will have a changing complexity, its compressibility will vary over the whole playing time, therefore the output bitrate will never be really constant, even if the quantization is (belatedly) adapted to the content.

[hello_hello]

I am using MeGUI 2507 and lately I notice the output file size is totally different from the estimate calculated in the built-in Bitrate Calculator. Is there a better way for me to predict the output size? I am doing x265 converts in ABR mode. The output size is totally different. Sometimes it's less than the target and sometimes it's more than the target size. Inconsistent. Is this due to the meGUI or something else?

You could try the same thing again with x264 and if it gets a lot closer to the desired bitrate it's probably the x265 encoder's fault.
The x265 encoder is fairly new and it's constantly being updated and improved. Maybe ABR bitrate accuracy isn't a high priority, or maybe it's not easy to achieve.

[MKVCrazy]

It is almost never the fault of the GUI calling the encoder, but rather the "fault" of the encoder, or the bitrate control technique as such, in relation to the material to be encoded.

1-pass ABR ist hard to control: the encoder can only regulate the output quantization of future frames after it discovered that previous frames already had overshot or undershot the target bitrate. The GUI can only assume the expected output if the bitrate were as constant as possible; but most video material will have a changing complexity, its compressibility will vary over the whole playing time, therefore the output bitrate will never be really constant, even if the quantization is (belatedly) adapted to the content.

You could try the same thing again with x264 and if it gets a lot closer to the desired bitrate it's probably the x265 encoder's fault.
The x265 encoder is fairly new and it's constantly being updated and improved. Maybe ABR bitrate accuracy isn't a high priority, or maybe it's not easy to achieve.

Thanks for your replies. It seems when that the encoder was causing this, the complexity thing. I was able to reach my target sizes, usually in the 2nd try after calculating the difference and the new values I need to put in for the 2nd time - if not, I get it in the 3rd try. But lately, I've been using FFT3DFilter to help with the hiding the blocks due to a little low bitrate and the resulting quality are satisfying. I wonder if it got anything to do with FFT3DFilter too. :/ Both times, I've been using the same build 2507. I don't want to do without this filter, it's so helpful. Any alternative suggestions?

[hello_hello]

But lately, I've been using FFT3DFilter to help with the hiding the blocks due to a little low bitrate and the resulting quality are satisfying. I wonder if it got anything to do with FFT3DFilter too. :/ Both times, I've been using the same build 2507. I don't want to do without this filter, it's so helpful. Any alternative suggestions?

I assume fft3dfilter is removing some noise, making the video easier to compress, and therefore there's less compression artefacts (blocking) in the encoded version.

There's a few script based denoisers. For example:
http://avisynth.nl/images/FastDegrain.avs
http://avisynth.nl/index.php/MCTemporalDenoise
http://avisynth.nl/index.php/Temporal_Degrain

Mostly, I use QTGMC in progressive mode (http://forum.videohelp.com/threads/358043-A-comparison-of-AVIsynth-denoise-filters?p=2283228&viewfull=1#post2283228). It's not officially a denoiser, but it still de-noises well. It uses ff3tdfilter for the denoising by default. I think two of the above scripts use it by default too.
There's some sample encodes in the above link.
The QTGMC thread: http://forum.doom9.org/showthread.php?t=156028

Once the script based denoisers are set up they're fairly easy to use. If you need any assistance I'm sure someone will help. They tend to be a lot slower than standard noise removal plugins though.

[AMED]

another great denoiser is SMDegrain (http://doom10.org/index.php?topic=2178.0), I get excellent results with it.

For blocky sources you could try.

SMDegrain(prefilter=3,refinemotion=true,lsb=true)

[j8ee]

Looking at http://mewiki.project357.com/wiki/X264_Settings#no-fast-pskip

no-fast-pskip

Default: Not Set

Disables early skip detection on P-frames. At low bitrates, provides a moderate quality increase for a large speed cost. At high bitrates, has negligible effect on both speed and quality.

Semantics are a bit confusing... If I understand this correctly: Enabling this setting (and therefore disabling fast p-skip), provides a moderate quality increase for a large speed cost at low bitrates, but at high bitrates it doesn't effect neither encoding speed nor quality much?

What are low and high bitrates in this context?

For me at least, looking through the description it isn't obvious if it is the setting or the default fast p-skip function that provides mentioned effects.

[j8ee]

(^Nobody that can give a quick confirmation?)

I just discovered the mp4 muxer doesn't seem to be able to deal with negative audio delays?

A negative audio delay should be mapped to a positive video delay I guess, since that was what I had to do with mp4box at the command line to make it in sync. mp4box didn't gave an error though, but synchronization was off many times the original value when I tried a negative number.

[hello_hello]

The way I understand it disabling fast p-skip can potentially increase the quality as you described and checking the "no fast p-slip" option disables it. I've no idea regarding the bitrate part of your question.

I did a little research and I'm starting to think MP4Box doesn't support negative audio delays (I never use MP4 myself). No mention of negative delays here (http://gpac.wp.mines-telecom.fr/mp4box/mp4box-documentation/). If that's the case I guess MeGUI's MP4 muxer should stop you from trying to apply a negative delay.

Other containers (ie MKV) don't always support negative delays, but MKVMergeGUI would remove an appropriate amount from the beginning of the audio stream to effectively apply a negative delay. Handling negative audio delays that way probably wouldn't be uncommon, but maybe MP4Box doesn't.

[kotuwa]

in MeGUI we can select "Prefer DSS2 over DirectShowSource".
What does it do?..
What are the differences?
And why the width is different when we chose that option...
Ex: source is 1280, when the option is selected, the width is less than 1280.... DirectShowSource gives exact 1280.
!?

[LigH]

There is DirectShowSource, shipped with AviSynth. It has its specific advantages, e.g. in enforcing CFR by "resampling" the video.

And there is DirectShowSource2, shipped with Haali Media Splitter. It has different advantages; AFAIR, it cannot enforce CFR with a new framerate though, it may stretch/squeeze it instead.

I am not sure about the difference regarding video properties. One may prefer container flags regarding aspect ratio and soft cropping, the other may prefer content stream flags.

[sneaker_ger]

There is DirectShowSource, shipped with AviSynth. It has its specific advantages, e.g. in enforcing CFR by "resampling" the video.

And there is DirectShowSource2, shipped with Haali Media Splitter. It has different advantages; AFAIR, it cannot enforce CFR with a new framerate though, it may stretch/squeeze it instead.

IIRC it's a bit different:
DSS2 always does VFR->CFR (dropping/repeating frames)
DirectShowSource can do it (if convertfps=true parameter used)

DSS2 also incorporates attempts to be frame-accurate.

I have no idea why the width would change, though.

[LigH]

Not without MediaInfo full reports or a sample. But it may depend on the installed decoders too. I remember that there was a misinterpretation of WMV / VC-1 AR flags, as one example.

[j8ee]

Getting a "floating point PCM is not supported for ALAC" when trying to transcode an ac3 via qaac. Foobar does it just fine though, why the difference?

Regarding negative audio delays - delaying other tracks would be a gentler way than removing samples. Anyway the GUI shouldn't allow something the muxer cannot do.

[LigH]

You may have to force a conversion to integer (16 bit?) in the audio conversion, the preferred decoder for AC3 appears to return float samples (quite probable for decoded AC3, depending on the selected audio decoder).

[hello_hello]

Getting a "floating point PCM is not supported for ALAC" when trying to transcode an ac3 via qaac. Foobar does it just fine though, why the difference?

That seems odd. Unless you're decoding via DirectShow I'm not sure why that'd happen.
I can convert ac3 to aac with MeGUI/Qaac. I just tested it (I normally use foobar2000 myself, so I thought I should check).

Regarding negative audio delays - delaying other tracks would be a gentler way than removing samples. Anyway the GUI shouldn't allow something the muxer cannot do.

In a perfect world that's possibly true, but unfortunately it relies on players obeying any delay you set, which isn't guaranteed. Especially when it comes to MP4. It's only since MPC-HC started use LAV filters internally that it obeys audio delays in MP4s (I assume it's working properly now). Before then, it was broken in that respect. I think VLC was/is also hit and miss when it comes to MP4 delays. There's apparently more than one way to implement a delay in MP4s.... I really don't understand much about MP4 myself.... if an MP4 finds it's way onto my hard drive the first thing I do is remux it as an MKV.

When I apply a delay to an MKV track and open the MKV with MediaInfo the delay is usually listed as expected. For MP4s.... not so much, I don't think.

Instead of a negative audio delay you'd need to apply a positive delay to all the other streams. How clever is MP4Box when it comes to applying a delay to subtitles?

[kotuwa]

how to set-up CoreAudioToolbox.dll to use QAAC?
tried putting the dll in QAAC folder did not work!... also is the version of CoreAudioToolbox relevant? (7.9.7.7 etc)

[sneaker_ger]

It needs more than just the CoreAudioToolbox.dll.
Downloads iTunes from here (https://www.apple.com/itunes/download/) and use this script (https://sites.google.com/site/qaacpage/cabinet/makeportable.zip?attredirects=0&d=1) (needs 7-zip) to extract all files required by qaac. Then put them all into the qaac folder.

[LigH]

The QuickTime installer instead of iTunes will work as well.

[hello_hello]

how to set-up CoreAudioToolbox.dll to use QAAC?
tried putting the dll in QAAC folder did not work!... also is the version of CoreAudioToolbox relevant? (7.9.7.7 etc)

How did you set it up for foobar2000? It's the same principle.
The QAAC site says ideally you need CoreAudioToolbox from Quicktime 10.5 or newer, or from iTunes 7.7.1 or newer.
Unless it's been updated very recently the current CoreAudioToolbox version is 7.9.8.3.

[Kurtnoise]

I did a little research and I'm starting to think MP4Box doesn't support negative audio delays (I never use MP4 myself). No mention of negative delays here (http://gpac.wp.mines-telecom.fr/mp4box/mp4box-documentation/). If that's the case I guess MeGUI's MP4 muxer should stop you from trying to apply a negative delay.

Of course, it does...anyway, it's better to apply delay during transcoding audio files instead of muxing event.

[hello_hello]

Of course, it does...anyway, it's better to apply delay during transcoding audio files instead of muxing event.

Well that's odd. When I tried it the other day (using both MyMP4BoxGUI and MeGUI's MP4 muxer), applying an audio delay appeared to be having no effect when playing the MP4 with MPC-HC, yet today I tried again and it's obviously working, although unfortunately MediaInfo doesn't report any audio delay.

I don't quite understand what was happening. I deleted the MP4 I was using for experimenting previously so I can't try it again to see if there was something odd about it or whether I'd been doing something silly.
I wish I still had it. Is it possible the way an MP4 is muxed with another program could interfere with MyMP4Box's ability to set an audio delay, or for a player to obey that delay? I extracted the audio from the original MP4 before remuxing it while applying a delay, but not the video.

If the muxing programs remove an appropriate amount from the beginning of the audio stream in order to apply a negative delay that way (as MKVMergeGUI does), then give or take a few milliseconds the end result would be the same as applying a negative delay when transcoding. Assuming of course you're not wanting to keep the original audio rather than re-encode it...

[kotuwa]

yes... once me too had audio sync problem in MP4... muxing delay did not work when playing.... wanted to cut using a audio cutter, failed....
then i did cut doing a jilmart.. with MMG (mkvtoolnix) by first muxing into MKV using a video that has only key frames :D

[j8ee]

I just now tried a -500 value when muxing tracks from an mp4 from youtube (fmt18 version (https://www.youtube.com/watch?v=FSSDLDhbacc) for you with complete youtube saver), and both with megui mp4 muxer gui and mp4box commandline the resulting file is unplayable with cccp/mpc-hc and unwatchable with vlc.

-add "input_video.mp4:fps=30.000:delay=0:name=delay_test_track1" -add "input_audio.mp4:delay=-500:name=delay_test_track2" -new "output_video_500_minus.mp4"

With my own encodes a few days ago, I had a file that needed +2040 ms adjustment in mpc-hc, so I applied that with megui mp4 muxer. The file then needed +4080 ms adjustment... so I applied -2040 and then it needed +5000 something adjustment.

[sneaker_ger]

It seems like mp4box applies the edit list to the wrong track for negative delays. Positive delay boxes also look wrong - not sure I'm reading them correctly. Anyways, the command-line generated by MeGUI should be correct and the discussion moved to a different thread. If it's an issue it's definitely one of mp4box.

[RBO]

Romain from GPAC here. If you think there is any issue with MP4Box, can you please post a summary in our forums or bugs tracker?

https://sourceforge.net/p/gpac/discussion/
https://sourceforge.net/p/gpac/bugs/

We really appreciate the effort being made by the doom9 community. Don't hesitate to ping us if you have any questions or issues! We are often overwhelmed but it is always a pleasure to help :)

Cheers

[sneaker_ger]

I posted a thread to the help forum (awaiting moderation). The positive delay handling might be correct after all, only the negative one seems wrong. But I'm no mp4 expert.

In case anyone with mp4 knowledge can confirm if this is spec compliant for a positive delay of 2000ms with a movie timescale of 600 (first CTS and DTS 0):
entry[0]
segment_duration = 1200
media_time = -1
media_rate = 1.000000
entry[1]
segment_duration = 18027
media_time = 0
media_rate = 1.000000

[hello_hello]

I may have found the reason for my previous MeGUI/MP4Box, lack of audio delay issue. Well if not the reason as such, I can at least duplicate it.

Open MeGUI's MP4 muxer. Add an existing MP4 as the video source (it doesn't seem to matter if it contains audio).
Add a separate audio stream (I tried raw AAC and AC3).
Apply a negative delay to the audio stream (I was applying -500ms, but I don't think it matters).

When opening the resulting MP4 in MPC-HC or VLC, the displayed duration will be twice the actual duration. The audio stream will have no delay relative to the video on playback.

MeGUI command line:
"C:\Program Files\MeGUI\tools\mp4box\mp4box.exe" -add "D:\test.mp4#trackID=1:fps=25.0:name=" -add "D:\test.ac3#trackID=1:delay=-500:name=" -tmp "D:\\" -new "D:\test-muxed.mp4"

I messed around with MyMP4BoxGUI a little. It doesn't allow you to apply negative delays. Maybe that's due to an MP4Box limitation? When I tried to apply one by modifying the MyMP4BoxGUI command line, the resulting MP4 displayed with twice the actual duration again and there was no audio delay applied on playback.

MyMp4BoxGUI command line:
-add "D:\test2.mp4:fps=25.000:delay=0:name=test2.mp4" -add "D:\test.ac3:delay=-500:name=test.ac3" -itags tool="My MP4Box GUI 0.6.0.6 <http://my-mp4box-gui.zymichost.com>" -new "D:\test2.mp4-muxed.mp4"

The above is the only way I could reliably reproduce the problem. The video to be muxed must be in an MP4 container. The audio must be a raw stream. If both those conditions are true, applying a negative audio delay won't work. At least not for me.
I say "reliably" reproduce the problem because I thought I could reproduce it when using a positive audio delay too. I was absolutely sure. Yet the second or third time I tried a positive delay..... the result was an MP4 with a delay being applied on playback. So maybe I just imagined that one again......

If the video and audio you add to a muxing job in MeGUI are already in an MP4 container (the same MP4 or a different one), applying a negative audio delay seems to work. I didn't test it, but I assume the same would apply to audio in an M4A.

I wish MediaInfo displayed the audio delay in MP4s as it does for MKVs. Which made me wonder..... if MediaInfo doesn't show any delay in it's GUI, what happens when indexing an MP4 with MeGUI if it has an audio delay? So I tried it. A positive delay of 500ms first.
[Error] [04/09/14 2:04:58 PM] An error occurred: FFAudioSource: Seeking is severely broken
I tried again using the MP4 with the negative delay. No error this time, and the encoded audio was almost 500ms longer than the original, so I guess FFAudioSource applied the required delay. There was no mention of an audio delay in the log file I could find though.

I'd been relying on MKVMergeGUI to rectify any problems with MP4s during the remuxing process. I thought it knew what it was doing. Maybe it does, but.....
I took an MP4 with a positive audio delay of 500ms (checked to confirm the delay was being applied on playback) and remuxed it as an MKV. MediaInfo reported a delay of 6ms relative to the video. No sign of a 500ms delay being applied to the MKV on playback. Sigh.....
Next I did the same for an MP4 with an audio delay of -500ms (one with the negative delay being applied properly on playback). For the MKV version MediaInfo reported a -500ms audio delay. I guess MKVMergeGUI must've used a positive video delay, but at least the delay carried over to the MKV.

So to sum up that last part..... even when I applied a positive audio delay which I could verify on playback, it seemed to be ignored by MKVMergeGUI and caused ffms2 to give up completely. A negative MP4 audio delay seems to be recognised by both programs.

[j8ee]

^If you read the post above yours, sneaker has looked into this and asked the developers to check it.

[hello_hello]

^If you read the post above yours, sneaker has looked into this and asked the developers to check it.

Yeah I know.... with no mention of when it works, when it doesn't and/or how it's muxed. It seems to make a difference.

I didn't see any mention of other programs not recognising positive audio delays which work fine for a media player, but I'll re-read his post again. ;)

[brunosso]

Is possible to automatically add srt file, in folder to mux?
I have a folder with 24 avi file, and 24 srt subtitle file. I want to encode all 24 with a profile of OneClick encoder, but when i try to add the entire folder, only the video file are encoded, and not the srt file...

PS I try to rename the file like this

xxx.avi
xxx.srt

and like this

xxx.avi
xxx.Italian.srt

none of this method work...

[LigH]

If at all, then possibly rather ISO 639 language codes instead of whole english language names.