MeGUI: General Questions and Troubleshooting Thread

[poisondeathray]

That is what I have been doing. And that seems to work fine except the flag for the aspect ratio stays at the original 2.35 instead of saying 16/9 which is what MF6 needs to make the HDDVD_TS folders. I thought it may be a problem with MeGUI or with the standard-HD-DVD profile.


Perhaps you could open your raw avc stream (the one with the borders added) in h264info and change that information to 16/9, then import into MF6? I think this should "re-write" that information (but not re-encode)

[ThrottleAbuse]

I have tried to do that with h264info. If I set the aspect ratio to 16/9 on that 2.35 file it ends up flagged as 3.25 or something crazy which won't work. I wish I could figure this out as over last night and today I did to encodes that ended up with the wrong aspect ratio. SUCKS.

[poisondeathray]

I have tried to do that with h264info. If I set the aspect ratio to 16/9 on that 2.35 file it ends up flagged as 3.25 or something crazy which won't work. I wish I could figure this out as over last night and today I did to encodes that ended up with the wrong aspect ratio. SUCKS.

There shouldn't be any flags or aspect ratio weirdness if you don't use the avisynth creator, or --sar.

I tested a sample 1920x800, added borders, used the same encoding "standalone HD-DVD" profile in MeGUI. Using a stream analyser on a raw output it was 30x17(1:1) which is identical to retail blu-ray's. Unless there is something up with the HD-DVD spec that is different than blu-ray (in regards to aspect ratio)?

Perhaps something is up with your MF6 software? or settings?

Also, do your wmv input files have square pixels? That would skew the calculation, because all blu-ray / hd-dvd is 1:1 (I think). You would have to compensate for this, because avisynth assumes 1:1

Also, consider testing on a shorter clip instead of the full length of the movie (just use Trim(0,100) in avisynth for the 1st 100 frames), so you don't waste hours of encoding on each "test run"

[ThrottleAbuse]

I don't follow you on not using avisynth creator. If I look in MeGUI at the x264 configuration it doesn't have --sar anywhere in the settings. The thing is the encoded clip comes out with the proper aspect ratio of 1920:1080 its just the flag that needs to say 16/9 will say 2.35 or whatever the original file was even though it added boarders. Like I said before I can create a AVS script and run and encode and not have it work then use the exact same AVS script and all the same settings and run it again and it will show up flagged correctly. Absolutely no changes and it will show up with the correct flag of 16/9. That is what is so frustrating.

[poisondeathray]

I don't follow you on not using avisynth creator. If I look in MeGUI at the x264 configuration it doesn't have --sar anywhere in the settings. The thing is the encoded clip comes out with the proper aspect ratio of 1920:1080 its just the flag that needs to say 16/9 will say 2.35 or whatever the original file was even though it added boarders. Like I said before I can create a AVS script and run and encode and not have it work then use the exact same AVS script and all the same settings and run it again and it will show up flagged correctly. Absolutely no changes and it will show up with the correct flag of 16/9. That is what is so frustrating.

The problem with avisynth creator is that you have to uncheckmark all the default options like resize, anamorphic, etc... otherwise it sends the info through. If you manually did a script you avoid all this completely, so it's 1 less thing to worry about

The --sar is not in the gui, it's what you add in the extra command line for the pixel aspect ratio. If you didn't enter it, or did not use MeGUI Dar_X, Dar_Y in the avs script, you should be fine.

The only other suggestion I have is determine what is different between input files that work vs. ones that don't work, because if you used the same MeGUI procedure as you claimed, then that is the only thing that is different. The only thing that comes to my mind is the non-square pixel input I mentioned earlier (avisynth assumes 1:1), and you didn't compensate for it.

[Nightshiver]

Sharky, I'm having that problem I had last month. Mencoder is crashing, again. I'm going to try a different version. Again.

Edit1: The newest version doesn't work. As a side note, why is it only me who is having this problem with mencoder?
Edit2: build 27305 doesn't work. This is stupid....

[ankurs]

still no help people ?

relating to this post : http://forum.doom9.org/showpost.php?p=1215502&postcount=3295

[buzzqw]

check if you have a dgdecode.dll in c:\program files\avisynth25\plugins

.. better.. search all your hard drives for DGDecode.dll and remove ALL

then use the only one bundled/downloaded by megui

BHH

P.S remember to rebuild the d2v project

[jamos]

I know this is not a Megui question perse, but thought maybe here someone who messes with megui has the answer.

Have a fresh install of Vista Ultimate 64 sp1 with all patches. Installed Megui with all defaults. Of course AVC files load fine in preview from my AVS scripts, but when loading VC-1 mt2s files with AVS scripts I get a timeout error when waiting for graph in avsynth. I am assuming that the default directshow cannot load VC-1 files. So I installed new beta builds of FFDshow and then check the VC1 option on installation. Now the video will load when loading the AVS script but its distorted. So I uninstalled FFDshow and installed MKVsplitter (Haali) latest version, which now loads the VC-1 video fine but when loading a AVC video the AVC video is distorted! Has anyone had luck getting a fliter that loads and works both AVC and VC-1 video files with Vista 64? P.S. using XP 32 bit and MKVsplitter I can load both types and run them no problem but the speed is more than half as slow.

Thanks

[poisondeathray]

I know this is not a Megui question perse, but thought maybe here someone who messes with megui has the answer.

Have a fresh install of Vista Ultimate 64 sp1 with all patches. Installed Megui with all defaults. Of course AVC files load fine in preview from my AVS scripts, but when loading VC-1 mt2s files with AVS scripts I get a timeout error when waiting for graph in avsynth. I am assuming that the default directshow cannot load VC-1 files. So I installed new beta builds of FFDshow and then check the VC1 option on installation. Now the video will load when loading the AVS script but its distorted. So I uninstalled FFDshow and installed MKVsplitter (Haali) latest version, which now loads the VC-1 video fine but when loading a AVC video the AVC video is distorted! Has anyone had luck getting a fliter that loads and works both AVC and VC-1 video files with Vista 64? P.S. using XP 32 bit and MKVsplitter I can load both types and run them no problem but the speed is more than half as slow.

Thanks

I'm on XP, but I experienced distortion this with certain ffdshow builds using different libavcodec versions. I use WMV Decoder DMO to decode VC-1 content now, it has fewer problems decoding VC-1 in my experience. If your decode is foobar, then the encode will be similarly corrupted. It comes with WMP11 or Windows Media Format SDK 11 if you don't want to install WMP11. You can change the merit of the decoder in graphstudio.

Assuming your playback material is OK, sometimes switching containers "fixes" the corruption. I've experienced both cases where either .mp4 or .mkv had corruption issues on playback , but for some reason muxing into the other container or .m2ts or .ts fixed it.

[jamos]

I'm on XP, but I experienced distortion this with certain ffdshow builds using different libavcodec versions. I use WMV Decoder DMO to decode VC-1 content now, it has fewer problems decoding VC-1 in my experience. If your decode is foobar, then the encode will be similarly corrupted. It comes with WMP11 or Windows Media Format SDK 11 if you don't want to install WMP11. You can change the merit of the decoder in graphstudio.

Assuming your playback material is OK, sometimes switching containers "fixes" the corruption. I've experienced both cases where either .mp4 or .mkv had corruption issues on playback , but for some reason muxing into the other container or .m2ts or .ts fixed it.


thanks for the reply. I do have WMP11 installed (comes with Vista xp1) do i need the sdk also? because stock MEGUI install will not even decode VC-1 files in Vista 64 (graph never opens). Would love to get this right without having to mess with builds of ffdshow. I have tried switching containers but they are all the same corruption (ie used tsmuxer to change from m2ts to ts etc.)

thanks

Also am not using mkv files these are m2ts files direct from good BD VC-1 sources.

My work around for now is if i need to reencode a VC-1 source I install MKVsplitter, then uninstall it after I am done for the more common AVC sources.

In general what I am doing is taking 1080p sources and reencoding them to 720p AVC-HD using megui and tsmuxer.

Edit: I have found the CCCP 2008-09-21 Codec pack fixed my issue now I can load both AVC and VC-1 sources (as well as MKV) with no issues in Vista 64. Now to get the 64 bit version of Avsynth and the 64 multithread version of x264 working is my next project.

[73ChargerFan]

I installed AviSynth_080912.exe which seems to have deleted (?) the plug-ins needed to run MeGUI.

MeGUI has the correct path to "C:\Program Files\AviSynth 2.5\plugins", which has only 4 files in it.

I'm still getting errors, and "Force (re)install" doesn't put any files in the plugins directory.

Can the install be repaired?

Edit:
"Force (re)install" downloaded new zip files to the update cache directory, so I sorted by date and unzipped 13 new files to the plugins directory, and things seem okay now.

Shouldn't reinstall have unzipped them, or the update function could have known files were missing?

[Sharktooth]

the problem is avisynth 2.58 is not supported yet.

[Nightshiver]

Well, I finally found a fix. mencoder version 27743 works.

[jamos]

the problem is avisynth 2.58 is not supported yet.

I am using 2.58 with megui and have no issues, so i am not sure what Chargerfan is doing wrong as my plugin dir for 2.58 has all the files 2.57 had. chargerfan you installing 2.58 from here http://sourceforge.net/project/showfiles.php?group_id=57023&package_id=105994&release_id=625750 ? Best way to install megui clean is uninstall avisynth and megui and make sure the directories are deleted. then install avisynth, then install megui again. if you have other codecs messing you up use http://www.cccp-project.net/download.php?type=cccpi the insurgent to tell you what you have and then uninstall those..could be your avisynth install is not in the right place or in many places.

[73ChargerFan]

MeGUI is working fine for me now, doing mpeg2->x264 & ac3->nero aac transcoding.

I'm using the latest development build of Avisynth 2.58 & ffdshow-tryouts nightly 11-14-2008.

mpeg2 720x480 16/9 , x264/mp4 target always seems to set the AR to 1.5 ??? I fix by muxing in mkvmerge.

jamos - I wanted to try out the latest ripbot264, but it said I didn't have avisynth installed so I grabbed the latest from sourceforge.

[citanuL]

Is there any way, possibly in MeGUI's "Custom command line", to set "Zone Options" type settings as featured in XviD encoder GUI ?

[stony8]

can anyone help me on this one? I have no idea what went wrong....

thanks

---------------------------
Fatal error
---------------------------
MeGUI encountered a fatal error and may not be able to proceed. Reason: Value cannot be null.

Parameter name: path1 Source of exception: mscorlib stacktrace: at System.IO.Path.Combine(String path1, String path2)

at MeGUI.OneClickPostProcessor.fillInAudioInformation()

at MeGUI.OneClickPostProcessor.postprocess()

at MeGUI.OneClickPostProcessor.postprocess(MainForm mainForm, Job job)

at MeGUI.core.gui.JobWorker.postprocessJob(Job job)

at MeGUI.core.gui.JobWorker.<>c__DisplayClass8.<UpdateGUIStatus>b__5()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

[Sharktooth]

@citanuL: zones options are available in the main form. otherwise you can specify the needed encoder switches/options in the custom commandline box.

@stony8: you didnt specify the audio input.

[stony8]

@stony8: you didnt specify the audio input.

ehm, I used the oneclick encoder, and there was audio input

however, I fiddled around with the avs. I deleted the <crop> from the avisynth template (avisynth configuration dialog) some time ago. moved it back again, and it worked.

strange, as I cant relate this to audio.


other issue I found: I have ripped a DVD where automatic interlace detection fails. when "automatic deinterlacing" is checked in oneclick encoder advanced config, it will also generate a fatal error.
solution: uncheck! but not a ehhh userfriendly way of telling there something wrong with the rip :)

[Sharktooth]

yeah.. definatly an unhandled exception.
please report the bug in the megui bugtracker on sourceforge.

[Richardw322]

I hope someone can help me here, I am a noob when it comes to this stuff. I can transcode MPEG to MKV/x264 with no problem, but I want to try AVI to MKV/x264, and I am having trouble getting started. Do I need to demux the file first? If so, with what? I tried without demuxing and MEGUI doesn't want to transcode the sound (MP3) to AC3. It just errors out. I just need a push to get started.

BTW, as for why I would do this, to learn. I learn best by doing something.

[~bT~]

I hope someone can help me here, I am a noob when it comes to this stuff. I can transcode MPEG to MKV/x264 with no problem, but I want to try AVI to MKV/x264, and I am having trouble getting started. Do I need to demux the file first? If so, with what? I tried without demuxing and MEGUI doesn't want to transcode the sound (MP3) to AC3. It just errors out. I just need a push to get started.

BTW, as for why I would do this, to learn. I learn best by doing something.

try ripbot264 for that kind of encoding.

[Sharktooth]

richard, what are the steps or procedure you did to import the avi file?
usually you can open the avi file in the avs creator, remove the audio=false in the avisource filter and feed the avs to both video and audio input and re-encode to whatever format you want.

[Richardw322]

richard, what are the steps or procedure you did to import the avi file?
usually you can open the avi file in the avs creator, remove the audio=false in the avisource filter and feed the avs to both video and audio input and re-encode to whatever format you want.

That is the step I was missing!! Thank you Sharktooth, I left the audio=false step out. No wonder it threw an error!! I am an idiot (as a friend likes to tell me). Can I do that at the same time and enque both together? Reason I ask is, in the guide I have been using they are 2 separate steps.

I guess it's not that simple. I removed the line and tried to reencode just the audio. (I didn't want to wait for the video to reencode to check the audio.) Now I get an error message "No Compatible ACM codec to decode 0X2000 audio stream to PCM. The audio is AC35.1, and it plays fine in both WMP and MPC-HC.

[NiGHTsC]

Anyne has an idea why my video is few seconds faster than the audio and the subtitle?
original video is a VOB and when I encode it into a MP4 using MeGUI, the video is always few seconds faster.
Maybe there's some delay info in the VOB file and MeGUI isn't able to read?
I've also tried lmx264GUI from LeiMing and same thing happent.

This is the VOB and MP4 files.
http://nightsc.googlepages.com/DVD2_09.vob
http://nightsc2.googlepages.com/DVD2_09.mp4

and the profile I used in lmx264GUI

@x264.exe --progress --no-psnr --no-ssim --cqm flat --no-fast-pskip --mixed-refs --scenecut 40 -I 250 -i 25 --sar 1:1 --threads auto --nr 0 -f 0:0 -b 2 --direct "temporal" --bime --b-adapt 1 --b-bias 0 --b-pyramid -w --deadzone-inter 21 --deadzone-intra 11 --aq-mode 1 --aq-strength 1 --chroma-qp-offset 0 --direct-8x8 1 --psy-rd 1.0:0.0 -p 1 --stats "I:\lmx264gui-20080925\bin\stats\DVD1_01.vob.stat" -B 2000 --qpmin 10 --qpmax 51 --qpstep 4 --qcomp 0.600000 --ipratio 1.400000 --pbratio 1.300000 -A none -r 1 -m 1 --me dia --ratetol 1.000000 --vbv-init 0.9 -o nul "I:\lmx264gui-20080925\bin\avs\DVD1_01.vob.avs" 2>&1|lputs.exe "I:\lmx264gui-20080925\bin\log\DVD1_01.vob.txt"
@x264.exe --progress --no-psnr --no-ssim --cqm flat --no-fast-pskip --mixed-refs --scenecut 40 -I 250 -i 25 --sar 1:1 --threads auto --nr 0 -f 0:0 -b 2 --direct "temporal" --bime --b-adapt 1 --b-bias 0 --b-pyramid -w --deadzone-inter 21 --deadzone-intra 11 --aq-mode 1 --aq-strength 1 --chroma-qp-offset 0 --direct-8x8 1 --psy-rd 1.0:0.0 -p 3 --stats "I:\lmx264gui-20080925\bin\stats\DVD1_01.vob.stat" -B 2000 --qpmin 10 --qpmax 51 --qpstep 4 --qcomp 0.600000 --ipratio 1.400000 --pbratio 1.300000 -A p8x8,p4x4,b8x8,i4x4 -m 5 --me hex --merange 24 -r 3 --ratetol 1.000000 --vbv-init 0.9 -o "I:\!TENNIS\DVD1_01.mp4" "I:\lmx264gui-20080925\bin\avs\DVD1_01.vob.avs" 2>&1|lputs.exe "I:\lmx264gui-20080925\bin\log\DVD1_01.vob.txt"
@bepipe.exe --script "import(^I:\lmx264gui-20080925\bin\avs\DVD1_01.vob.avs^)" | neroaacenc.exe -if - -of "I:\!TENNIS\DVD1_01.audio.mp4" -ignorelength -br 40000

and MeGUI

--pass 2 --bitrate 490 --stats ".stats" --ref 3 --mixed-refs --no-fast-pskip --bframes 2 --b-pyramid --bime --weightb --trellis 1 --analyse p8x8,b8x8,i4x4,p4x4 --merange 24 --threads auto --thread-input --progress --no-psnr --no-ssim --output "" ""


Thank you.

[nok32]

hi,
first post. i have been using megui very successfully to encode x264 with the HQ CQ preset, until i attempted a late 1960s era avant-garde film with a high grain. the encoding time and end filesize almost tripled. is the best solution for this and similar films to just use a 2-pass encode and set a max filesize? i am shooting for something in the 1gb range, and the CQ setting of 22 has generally been fine for delivering that filesize. my next attempt will use a higher 'grain filter' setting and then probably a 2-pass encode. any other suggestions on dealing with this type of film?
thanks!

[Kurtnoise]

Anyne has an idea why my video is few seconds faster than the audio and the subtitle?
original video is a VOB and when I encode it into a MP4 using MeGUI, the video is always few seconds faster.
Maybe there's some delay info in the VOB file and MeGUI isn't able to read?
I've also tried lmx264GUI from LeiMing and same thing happent.

This is the VOB and MP4 files.
http://nightsc.googlepages.com/DVD2_09.vob
http://nightsc2.googlepages.com/DVD2_09.mp4

you have to deinterlace this first...in the avisynth creator, check "my source is anime", source type: interlaced, field order: top field first, select yadif as deinterlacer.

then, retry an encode & remux.

I got this (http://www.mediafire.com/?ymn4ugzmjtb)...

[Kurtnoise]

hi,
first post. i have been using megui very successfully to encode x264 with the HQ CQ preset, until i attempted a late 1960s era avant-garde film with a high grain. the encoding time and end filesize almost tripled. is the best solution for this and similar films to just use a 2-pass encode and set a max filesize? i am shooting for something in the 1gb range, and the CQ setting of 22 has generally been fine for deliering that filesize. my next attempt will use a higher 'grain fuleter' setting and then probably a 2-pass encode. any other suggestions on dealing with this type of film?
thanks!
could you upload a vob sample of your source ?

[Richardw322]

I think I found my problem. I loaded the file into VirtualDub and it threw an error over the audio in the file. "Truncated or invalid compressed audio format detected (16 bytes should be 18) Then when I try to play in Virtual it says "No audio compresser could be found". Funny thing is it plays fine in MPC and WMP. MPC reports it as AC3 5.1. Just my luck to pick a broken file to play with.

[NiGHTsC]

you have to deinterlace this first...in the avisynth creator, check "my source is anime", source type: interlaced, field order: top field first, select yadif as deinterlacer.

then, retry an encode & remux.

I got this (http://www.mediafire.com/?ymn4ugzmjtb)...
select yadif as deinterlacer.
do you mean this? cause I can't find "yadif" in "Deinterlace"
http://img356.imageshack.us/img356/6549/10640582qd3.jpg
Thanx alot!

[~bT~]

I think I found my problem. I loaded the file into VirtualDub and it threw an error over the audio in the file. "Truncated or invalid compressed audio format detected (16 bytes should be 18) Then when I try to play in Virtual it says "No audio compresser could be found". Funny thing is it plays fine in MPC and WMP. MPC reports it as AC3 5.1. Just my luck to pick a broken file to play with.
ac3acm codec is what u need.

[Kurtnoise]

select yadif as deinterlacer.
do you mean this? cause I can't find "yadif" in "Deinterlace"

download it first via the updater.

[NiGHTsC]

download it first via the updater.
Hm, I just update everything in MeGUI and the video still has the same problem

this is the AVS I used.
DirectShowSource("I:\DVD2_09.vob",fps=29.97000002997,audio=false)
Load_Stdcall_Plugin("C:\Program Files\megui\tools\yadif\yadif.dll")
Yadif(order=1)
#crop
#resize
#denoiseThe profile I used is from SharkTooth, Unrestricted 2pass Anime_Toons Insane

[Kurtnoise]

you have to create a d2v file (in the d2v creator) instead of loading directly the vob file...

[nok32]

could you upload a vob sample of your source ?

sure!
http://www.mediafire.com/download.php?z3vewddz2mm
thanks for helping.

[NiGHTsC]

you have to create a d2v file (in the d2v creator) instead of loading directly the vob file...
hm, d2v...could this be done in a batch?
cause I have at least 10 VOBs to encode, that's why I used AVS and lmx264GUI.

Thanx again.

[Taurus]

sure!
http://www.mediafire.com/download.php?z3vewddz2mm
thanks for helping.
Pretty noisy and distorted your source.
If you dont care to much on sharpness, try "Heavy Noise" (Convolution3D) in AVS Creator and set "Mmeg2 Deblocking".
You can even try to manually set "cpu=6" in the editor.
Read the DGIndex manual about this switches.
It gets a little blurry this way, but at crf=18 I've got your source down to 33% @full resolution.
Or give other avisynth filters a chance...:p

[nok32]

thanks taurus,

would convolution3d + crf=18 give better results than spline36 + crf=22? i don't have the convolution3d filter installed, but i am getting about 34% using the 'fast' CQ preset, spline36, heavy filter and deblocking.

i am wondering if a 2-pass encode might not be better for such grainy film, though. any advice on CQ vs. 2-pass, when it comes to this sort of film?

[Kurtnoise]

hm, d2v...could this be done in a batch?

check the box "on completion load all files" if those files are the same movie...

[Taurus]

would convolution3d + crf=18 give better results than spline36 + crf=22? i don't have the convolution3d filter installed, but i am getting about 34% using the 'fast' CQ preset, spline36, heavy filter and deblocking.

Heavy Noise = convolution3d("movielq")
Spline36 is just a resizer
I'm not into old scratchy films, so maybe you can gather some more help in the AviSynth section in this forum?
It was just a shot in the dark from my side.
Try your sample with different settings and see what pleases you most.
And of course the duration of this film matters.
Without further information on the sbject I would say, stay close to 1.5gb on this source.
As a sidenote: Fantasic how x264 works on this grainy, scattered source!

[Richardw322]

ac3acm codec is what u need.

Thanks for the tip. I became obsessed with hgetting this to work yesterday. After installing the AC3ACM codec, I ran it through VirtualDub, and copied AVI to AVI. The new AVI file went through MEGUI like a champ.

[NiGHTsC]

check the box "on completion load all files" if those files are the same movie...
It seems that as long I use D2V the video would be fine even without that interlace options in AVS...
but it just can't load files in a batch, unfortunately ><!!
that "on completion load all files" simply load the video into AVS, that's all.

so the conclusion is, if I want to do it with D2V, I have to load videos one by one and with MeGUI until lmx264GUI support D2V?

[nok32]

Heavy Noise = convolution3d("movielq")
Spline36 is just a resizer
I'm not into old scratchy films, so maybe you can gather some more help in the AviSynth section in this forum?
It was just a shot in the dark from my side.
Try your sample with different settings and see what pleases you most.
And of course the duration of this film matters.
Without further information on the sbject I would say, stay close to 1.5gb on this source.
As a sidenote: Fantasic how x264 works on this grainy, scattered source!

i used the heavy noise filter and the 'balanced' 2-pass preset (@ 1500kbps, 1.5gb total filesize) and the film looks pretty good. i think using CQ is too sensitive to the grain and assumes that it needs a super-high bitrate, so 2-pass turns out to be a better option for older grainier material when filesize is an issue. or at least, that is my n00b conclusion. in any case, i am happy with the results i have. thanks!

[MrVideo]

@MrVideo: i dont know why you have problems with HD videos but sincerely, i dont understand why you care about AR when you dont need to singnal the AR or use 1:1...

If the selection has no bearing on encoding 1080i to 720p H.264 or 720p MPEG-2 to H.264, then I won't worry about it and ignore that it likes to choose PAL.

I'll just ignore it and do the encoding.

What I, and the other poster, would like fixed is the grayed text in the status GUI. There is nothing wrong with our monitors. Gray text is gray text and there isn't any reason for it to be gray. Please change the status GUI output so that all of the boxes have black text. It will be greatly appreciated.

Thanks.

[citanuL]

@citanuL: zones options are available in the main form. otherwise you can specify the needed encoder switches/options in the custom commandline box.

Maybe I wasn't specific enough. For instance, how would I greyscale a 1min portion in the middle of a 3min video? MeGUI doesn't seem to respect those zone settings of my installed XviD. Could you please ellaborate or explain "main form." or point me in direction to find more info on custom commandline box usage.

[MrVideo]

If the selection has no bearing on encoding 1080i to 720p H.264 or 720p MPEG-2 to H.264, then I won't worry about it and ignore that it likes to choose PAL.

Turns out the aspect ratio does need to be correctly determined. Here is why. The correct aspect ratio is needed in order for the recommended resize ratio to work.

For example, by default MeGUI thinks that 1080i video is PAL. So, when I turn on resize and put 1280 in the left box and click on recommended, it puts 704 in the other value. Oops.

One must have the correct aspect ratio, so this really does need to be fixed so that other options in the same GUI works correctly.

It knows that it is 1080 HD video, so obviously it is 1.78:1 (industry standard is not 1.778:1). How difficult is it to add 1.78:1 to the main list, and have it automatically detect that ratio?

[Snowknight26]

When I open any avs twice (by either dragging/dropping, clicking the ... [browse] button twice and/or using the reset button) in MeGUI then try to add an audio track to the bitrate calculator, MeGUI freezes.

[invy]

BUG:
When trying to mux into mp4, the damn mp4box thing always generates an error when it reaches 100% and finishes. The resulting file is perfectly OK, but it's damn annoying still because it doesn't advance to the next job in the queue, because I have to click the Microsoft's "Don't Send" box first.

This happens on and off, but mostly "on". It seems to have to do with a certain component that is outdated or something because if it happens at all, it usually happens after using the updater.

[~bT~]

BUG:
When trying to mux into mp4, the damn mp4box thing always generates an error when it reaches 100% and finishes. The resulting file is perfectly OK, but it's damn annoying still because it doesn't advance to the next job in the queue, because I have to click the Microsoft's "Don't Send" box first.

This happens on and off, but mostly "on". It seems to have to do with a certain component that is outdated or something because if it happens at all, it usually happens after using the updater.it happens due to spaces in the filename.