MeGUI Bug-Report Thread

[berrinam]

This thread is intended to be a place for everyone to post their MeGUI-related bug reports, and is also intended to be a list of known bugs, so that the some bugs are not repeatedly reported. Naturally, as MeGUI is high-quality software, written by many skilled developers, this thread should not see much activity :sly:

Before posting here, please read the bug-reporting guidelines.

Guidelines
Follow these steps, and the process of finding and fixing the bug will become much speedier. Don't follow them, and you won't find much help here.
Check the known bugs list (below) to see if your bug has already been reported. No point in filling up this thread if we already know about the bug
POST YOUR LOGFILE. MeGUI writes lots of valuable information in the logfile. Try reading the log yourself, and see if you find the error, or any outrageous values (ones which are clearly wrong). If you can solve it based on that, good for you. Otherwise, it may help someone else solving your problem.
Describe the simplest way to reproduce your problem. Imagine the people reading your instructions are idiots, so you have to tell them exactly what to do, in a fool-proof way.
No-one is going to spend 2 days running 10 encodes, on the off-chance that at the end of them, they might crash. Work out how to cause your problem to happen again, and then it is much easier for the problem to be solved.
If it is an obscure bug that happens only once in a while, and you can't work out when, try debugging it yourself:
Get Visual Studio Express (C#) from http://msdn.microsoft.com/vstudio/ex...p/default.aspx. It's free. Once you have set it up, get the latest sources for MeGUI from Sharktooth's source repository: http://files.x264.nl/?dir=./Sharktooth/megui/Sources
Then, open the MeGUI.csproj file in Visual Studio, and press Run (F5). You will then have a copy of MeGUI which should display the error and line when it crashes. So just run all your jobs in that, and see if it tells you which line the error is on.
Too much information is better than too little. Don't make the developers pry the information out of you, as it is too much work for them, and they will just ignore you.
If encoding/muxing doesn't start at all check your sources (e.g. open AviSynth script in a media player and VirtualDub, play the soundtrack in a media player, try playing the files to be muxed, etc.)
Use a build from the latest series of MeGUI releases (at the moment, 0.2.3.2137 or later). Only bugs in this series will be documented, as all known bugs are fixed before going onto a new series.
Don't post here if the problem is clearly not caused by MeGUI. If you aren't sure about which program caused the error, then there is a simple way of being pretty sure:

If MeGUI crashed, then it is almost certainly causing the problem. If MeGUI stays active, but flags the job as an error, then look at the commandline in the MeGUI log. If there are any outrageous values in the commandline (especially negative/very low/very high bitrates), then the commandline MeGUI generated had a problem, and so it is MeGUI's fault. In almost any other situation, it is the fault of an external program, so it is not MeGUI's fault.
Run your job commandline manually. If your commandline is "--bitrate 700 --level 1.3 --no-cabac --subme 6 --analyse p8x8,b8x8 --qpmin 22 --me umh --threads 2 --progress --no-psnr --output "c:\videos\video.mp4", start a commandprompt (start - run - type "cmd" without the "'s, and press enter), go to the path where you have your encoder (e.g. "cd c:\program files\ripping software\x264\"), then type the name of your encoder (e.g. x264.exe ) and paste the commandline and press enter. Alternatively, you can install the "open commandprompt here" powertoy (http://download.microsoft.com/download/whistler/Install/2/WXP/EN-US/CmdHerePowertoySetup.exe) and then you can just right click on your encoder folder in windows explorer, and select open commandprompt, type the name of your encoder and paste the commandline and press enter to get started right away.

Known bugs in series in builds 0.2.3.2137 or later
If a job (say, a mux job) errors out and 'Delete Intermediate Files' is checked, then those files will be deleted anyway, meaning there is no output whatsoever
Description: N/A
Status: Not yet solved.

Fatal error in some cases with the preview window in the AviSynth Script Creator
Description: See http://forum.doom9.org/showthread.php?p=795502#post795502
Status: Not yet solved

Queue sometimes does not proceed to next item, at random.
Description: See http://forum.doom9.org/showthread.php?p=798255#post798255
Status: sysKin is looking into it.

The matroska overhead calculation leads to undersized files
Description: See http://forum.doom9.org/showthread.php?p=809588#post809588
Status: Not yet solved

huffy mencoder commandlines have a -noodml which shouldn't be there

[Romario]

I post in file one big bug in MeGUI 0.2.3.1031, never before I havn't that problem.

Older builds works.

[Doom9]

We're off to a bad start here.. first of all you didn't post all the info we request, and second you posted a bugreport in the feature request thread.. that's definitely the wrong place so I moved it.

[Sharktooth]

I cant see the picture coz it's not approved but i think it's the tri-state bug introduced in that relase...

[Romario]

Download the picture which I provided.

[Sharktooth]

It's still not approved.

[Doom9]

I've seen it a long time ago.. it's your usual "input cannot be read" error.. but no info as to what the script looks like, if it can be played in a media player and opened in virtualdub.

[bob0r]

not updating: lossless --qp 0 show commandline
1: -
2: -
3: When selecting lossless, Show Commandline does not update to --qp 0
4: using megui-x264-svn.exe
5: -
6: -

Edit
When selecting lossless, i guess the qp box should be greyed out too, or the value changed to 0.
And possible when you enter 0, lossless will be set active (on high profile)
/Edit

not updating: Number of Threads --threads X show commandline
1: -
2: -
3: When changing Number of Threads, Show Commandline does not update to --threads X (not showing it when changing to 2 or higher)
4: using megui-x264-svn.exe
5: -
6: -

[Romario]

I've seen it a long time ago.. it's your usual "input cannot be read" error.. but no info as to what the script looks like, if it can be played in a media player and opened in virtualdub.

Ok, here how I wrote my Avisynth script:
DirectShowSource("f:\test video.mpg", fps=25)

Nothing more or less, and with build 1029 it worked without any errors. So, it is very clear that we have a bussines with strange bug.


And yes, script can, without any problems, open and play in VirtualDub Mod 1.5.4.1 and media player.

[ChronoCross]

I remember a small error I got awhile back when messing with 1 pass TIVTC vfra nd the auto seeking that megui does in the preview pane. by trying to seek using a on demand vfr it caused a buffer overflow and the application to crash. it does the same thing when seeking in vdubmod so I'm guessing it's inherint to the filter. perhaps the file you are loading in Directshowsource is suffering from the same thing in that a non-existent frame is being loaded by the preview pane. perhaps from you giving the incorrect framerate or even from megui loading it at a random spot.

Romario it is probably best if you didn't constantly bug the devs about this issue. However what I do recommend is finding another mpg sample with similarities with the sample you are currently working with and see if it occurs with all mpg files using the current release.

[godhead]

Romario it is probably best if you didn't constantly bug the devs about this issue. However what I do recommend is finding another mpg sample with similarities with the sample you are currently working with and see if it occurs with all mpg files using the current release.

Actually he just responded with the information that Doom9 requested in the other thread and has moved his request to the appropriate thread. So, please don't be too hard on him :) . But, your suggestion of trying other samples is helpful.

[Doom9]

perhaps from you giving the incorrect framerate or even from megui loading it at a random spot. The framerate doesn't matter at the initial setup.. it could be anything and it would still work. All the preview window does is get the number of frames from the source, then jump to floor(#frames/2).

Romario's error is "unsupported colorspace YUY2".. I take it that means the input has to be YV12.. it's quite simple to test that.. add a ConverToYV12() at the end of the AviSynth script (check the AviSynth wiki to see if this command is correct just in case). If it's that.. it's definitely not a MeGUI bug but a user error. In fact, MeGUI has nothing to do at all with the fact that it worked in a previous release.. it's an error that comes directly from x264.exe.. so either something changed inside x264.exe, or you changed something at the source/playback filters that are being used via directshowsource. And then there's the thing that you should run mpg files through dgindex anyway.. DirectShowSource is probably the most dangerous source loading command AviSynth offers.. and in my own experience the most error prone.

[bob0r]

not updating: turbo 2pass - 1st pass and 3pass- 1st pass
1: -
2: -
3: When selecting turbo, Show Commandline does update, then when disable it does not set previous state back
Same goes for automated pass 2 and 3, not sure how it should update on that thouigh.
4: using megui-x264-svn.exe
5: -
6: -

[bob0r]

FourCC for x264.exe is not used, is it?
How is it used, and if its used should show commandline update?

When you click config the title says: x264 Codec Configuration, i think that should be:
1 x264 Configuration or
2 x264 Encoder Configuration, but id go for option 1 :)

[bob0r]

Done what? :) title or fourcc explaination? :p

Edit your previous post, then ill delete this msg, to keep this thread clean.

[Sharktooth]

When you click config the title says: x264 Codec Configuration, i think that should be:
1 x264 Configuration or
2 x264 Encoder Configuration, but id go for option 1 :)
Done (option 2) for x264, snow and xvid.

EDIT: i forgot lavc... updated now.

Also fourCC is not a x264 option so it will not be shown in x264 command line.

[Sharktooth]

not updating: turbo 2pass - 1st pass and 3pass- 1st pass
1: -
2: -
3: When selecting turbo, Show Commandline does update, then when disable it does not set previous state back
Same goes for automated pass 2 and 3, not sure how it should update on that thouigh.
4: using megui-x264-svn.exe
5: -
6: -
This is not a bug. Those settings are set to accelerate the first pass when clicking turbo. MeGUI does not remember what happens when one option excludes other ones so you have to manually set them back to what are your preferred values in the second (or third) pass.

[Doom9]

This is not a bug.umm.. isn't that a case tri-state should also handle, not only levels and avc profiles? turbo shouldn't change anything in the GUI, just in the commandline.

[Sharktooth]

tri-state is a delicate thing. i made some changes to some conditions to restore the default values when a higher level or some options that enables a group are selected and when clicking on Config, MeGUI crashes without any message and wont let me debug too...
i will revert those changes back btw...

[Romario]

Romario's error is "unsupported colorspace YUY2".. I take it that means the input has to be YV12.. it's quite simple to test that.. add a ConverToYV12() at the end of the AviSynth script (check the AviSynth wiki to see if this command is correct just in case). If it's that.. it's definitely not a MeGUI bug but a user error. In fact, MeGUI has nothing to do at all with the fact that it worked in a previous release.. it's an error that comes directly from x264.exe.. so either something changed inside x264.exe, or you changed something at the source/playback filters that are being used via directshowsource. And then there's the thing that you should run mpg files through dgindex anyway.. DirectShowSource is probably the most dangerous source loading command AviSynth offers.. and in my own experience the most error prone.

Thank you for explanation, but could you provide me exact way to convert YUY2 to YV12 output, because I am so new in AviSynth scripts.:o

Doom9, why DirectShowSource is " probably the most dangerous source loading command AviSynth offers ", can you tell me?:scared:

I can tell you that that MPG file worked fine with 0.2.3.1029 build, and I don't change anything in that MPG source file, everything is same as earlier.

It seems that something is changed in x264.exe.

[Sharktooth]

as doom9 said add ConverToYV12() at the end of your avisynth script.

[Richard Berg]

The command is ConvertToYV12(). If the source is interlaced, be sure to use ConvertToYV12(interlaced=true)

[Romario]

Ok, I will try with that.

[charleski]

Another bug:
MP3 audio output is disrupted: If you select MP3 as an output format in the main form and then go to configure it, on returning the format is reset to NAAC mp4.

I'll fix this.

[Fixed in 0.2.3.1037 - turns out it was an issue with rogue profiles with empty names]

[charleski]

DirectShowSource is " probably the most dangerous source loading command AviSynth offers ", can you tell me?:scared:

DirectShowSource is easily the flakiest part of Avisynth, and the bit I wish the Avisynth developers would work on. In many cases it just doesn't work and returns 'the filter graph manager won't talk to me' errors even though DirectShow is quite capable of rendering the file (this even happens if you feed it a filtergraph previously rendered by graphedit...).

If you have an avi file, then Avisource(<filename>) is probably a more robust method of loading it into Avisynth.

[Romario]

No, I don't have an avi file, only MPEG2 files.

Can I use Avisource instead DirectShowSource, for mpg files?

[berrinam]

For mpg files, use index them with DGIndex first, and then use mpeg2source. MeGUI will do this automatically for you. Go to Tools->D2V Creator, select your input file, and check the other settings, check 'On completion load files', then press queue. Run the job from the main window. You can now configure your file properly.

[Sharktooth]

In x264 config, setting the turbo option in a first pass mode changes GUI options (macroblock options) which it shouldn't
Description : Checking turbo will get rid of all macroblock options (correct), but unchecking it will leave it that way (incorrect). Also, the P4x4 option is diasbled after unchecking turbo.
Status : Fixed in 1040

[bob0r]

Will this update show commandline also?

(And dont worry, files.x264.nl is being fixed with some updates and have stuff load @ startup, last uptime 300+ days, now power outage also :p)

[Sharktooth]

What you mean?

[jmk]

i hve a problem with the autocrop feature in the avisynth script generator dialog. somehow it can not find the right crop values for "2001: a space odyssey". how does it work anyhow?

and another thing thats odd: i recently started using the "SAR" feature. what i do is that i select "auto-detect" aspect ratio on one click mode (since i have some odd ones here, "2001..." for example seems to have the actual ar of 2,15:1). so far everything seems fine. if i check the final muxed files with mp4box -info i can see the that the video track has an aspect ration set. but somehow these values are to large for mplayer or vlc for example:

Track # 1 Info - TrackID 1 - TimeScale 25 - Duration 01:22:16.560
Media Info: Language "und" - Type "vide" - Sub Type "avc1" - 123412 samples
MPEG-4 Config: Visual Stream - ObjectTypeIndication 0x21
AVC/H264 Video - Visual Size 640 x 384 - Profile Unknown @ Level 5.1
Pixel Aspect Ratio 640:1067 - Indicated track size 640 x 384
Self-synchronized


thx for this grat program,
jmk

ps: can anyone explain, or point me in the right direction, how i can change the aspect ratio in these files? and why does it say 640:1067 and not something like 2,35:1 ???

[berrinam]

@jmk: You haven't given enough information. Read the guidelines in the first post of this thread.

Just clearing up a few other things:
-auto-detect in oneclick is actually supposed to read Auto-Detect Later, but the end of it is chopped off. You see, there are two stages at which the Aspect Ratio can be found out: immediately, when you load the file, or later, after you've pressed Go, and it's done some processing. Now, normally, it will detect the Aspect Ratio immediately upon loading the file, and set it to the correct value (ie 16:9, 4:3, 1:1), but if something goes wrong, then it will default to Auto-Detect Later. If you think it is detecting it wrong, then it is probably set wrong on the DVD. In that case, what you want to use is the 'Custom' option, so that you can enter 2.35 yourself. If you are sure that it is correct on the DVD, then post a MeGUI bug report with everything asked for on the first post of this thread.

-You don't seem to be aware of the difference between Pixel Aspect Ratio (PAR) and Aspect Ratio, or Display Aspect Ratio. There are links about it Q17 of the x264 FAQ on the x264 win32 daily builds sticky.

[Doom9]

and as far as autocrop goes.. you know we need a vob sample to reproduce that ;) but I'm not ruling out the code works for everything.. for instance your black bars could be less than black (for instance if you pick the wrong color range in dgindex), or if you have a lot of black scenes, the algorithm can't tell between what's black bars and what's part of the movie..

[nurbs]

Since I haven't used autocrop lately I don't know if this is still an issue, but I noticed that on pictures that it should not crop at all it always crops 2 pixels form the right. I'm sorry I couldn't check, but I just read this and I am not at the PC I use for encoding till friday.

[berrinam]

Cropping must be in multiples of two, and autocropping favours over-cropping by one line to under-cropping by one line, so as to ensure removal of the borders. Perhaps this is causing what you are talking about. OTOH, it could actually be a bug. I'll wait for confirmation of this.

[Doom9]

In the x264 config, starting from the default settings, if you uncheck chroma, the commandline doesn't update. The same goes for bime.. seems showcommandline isn't called when those two options are changed.

[Sharktooth]

I already fixed that... how come it's back?

It's now re-fixed... and CVS is updated

[Raithmir]

0.2.3.2001 - AVISynth creator

Should enabling the deinterlace, noise filter, and colour correction tick boxes load the appropriate dll in the script for you? It doesn't for me, hence I just get a black narrow band when previewing the script. Using the load dll bit on the edit tab I would expect to just add the relevant load line to the existing script, but it deletes everything else.

MPEG2 deblocking checkbox does nothing?

ticking IVTC checkbox, then ticking the deinterlace box should remove the IVTC settings and add the selected deinterlace option, but it keeps the IVTC settings.

When does the AVI options section get enabled? or is that a future feature?

[Raithmir]

Loading the MeGUI snow version complains about the video profiles on startup ("is this a valid profile?" etc.).

[berrinam]

Should enabling the deinterlace, noise filter, and colour correction tick boxes load the appropriate dll in the script for you?Not everyone agrees on this, but in the current mode of operation, it shouldn't. The AviSynth plugins directory is very useful, and if you put your plugins there (why wouldn't you?), you don't need the loadplugin lines.

Using the load dll bit on the edit tab I would expect to just add the relevant load line to the existing script, but it deletes everything else.Bug confirmed and added to the list

MPEG2 deblocking checkbox does nothing?Not true. It's called mpeg2 deblocking because it is only for mpeg2 sources. Have a look at the mpeg2source(...) line when you press it -- it adds 'cpu=4'.

ticking IVTC checkbox, then ticking the deinterlace box should remove the IVTC settings and add the selected deinterlace option, but it keeps the IVTC settings.Confirmed and added to the list

When does the AVI options section get enabled? or is that a future feature?When you load an AVI file.

Loading the MeGUI snow version complains about the video profiles on startup ("is this a valid profile?" etc.).Only for non-Snow profiles. It makes sense, doesn't it? Why should MeGUI-Snow be able to load x264/xvid/lavc profiles? If you want that functionality, use the full version.

[Raithmir]

Not everyone agrees on this, but in the current mode of operation, it shouldn't. The AviSynth plugins directory is very useful, and if you put your plugins there (why wouldn't you?), you don't need the loadplugin lines.

So you're saying if I've got the plugins directory configured then the encode should work fine... but that preview won't work?

Only for non-Snow profiles. It makes sense, doesn't it? Why should MeGUI-Snow be able to load x264/xvid/lavc profiles? If you want that functionality, use the full version.

True. I just stick the three exe's in the same folder. Perhaps an additional tag could be added to the profile xml files to state whether the profile is for x264 or snow etc., then the x264 ones could just be ignored if you chose to run the snow only exe. I appreciate in typical usage you'd probably only use one of the exe's exclusively, so I supose it's a minor thing.

[Raithmir]

Actually, I've figured out why I was just getting a black band. My plugins path in the registry (HKLM\SOFTWARE\AviSynth\) was pointing to an old location. Corrected that and it now works.

[Doom9]

erhaps an additional tag could be added to the profile xml files to state whether the profile is for x264 or snow etc.If you look at the profiles, it's already there, however I see no point in opening each profile manually first and check what type of VideoCodecSettings it includes, then based on that decide if I really want to load it or not. I think it's kinda obvious that the snow edition can only handle snow profiles and that the x264 edition can only handle x264 profiles.. it's like if you try to play a video for which you don't have the proper codec installed.. it just won't work.

[godhead]

If you look at the profiles, it's already there, however I see no point in opening each profile manually first and check what type of VideoCodecSettings it includes, then based on that decide if I really want to load it or not. I think it's kinda obvious that the snow edition can only handle snow profiles and that the x264 edition can only handle x264 profiles.. it's like if you try to play a video for which you don't have the proper codec installed.. it just won't work.

What if the profiles were just placed under the appropriate subdirectories so we could load off those and if they fail, fall back to the root directory? Or do you not think it's worth it?

[The Link]

If you look at the profiles, it's already there, however I see no point in opening each profile manually first and check what type of VideoCodecSettings it includes, then based on that decide if I really want to load it or not. I think it's kinda obvious that the snow edition can only handle snow profiles and that the x264 edition can only handle x264 profiles.. it's like if you try to play a video for which you don't have the proper codec installed.. it just won't work.
Perhaps I don't understand the issue completely but what about making the "Video Profile" dropdown menu dependent on the state of the "Codec" dropdown menu. Hmm ... perhaps this is more a feature request (wrong thread?).

[Doom9]

but what about making the "Video Profile" dropdown menu dependent on the state of the "Codec" dropdown menu.Personally I name my profiles with the codec name.. I rather not have to select the codec first just so that I can then select a profile.. that kinda seems redundant seeing that profiles already contain which codecs they are meant for.

And yes, that would be a feature request, though the above is my answer to it.

[The Link]

Personally I name my profiles with the codec name.. I rather not have to select the codec first just so that I can then select a profile.. that kinda seems redundant seeing that profiles already contain which codecs they are meant for.

And yes, that would be a feature request, though the above is my answer to it.
Since it's just a minor thing in the end I can live with that. But it quite much confused me that the codec dropdown menu depends on the profile dropdown but not the other way round. So you can change the codec settings of a different codec than the visible (but unrelated) codec profile indicates.

[digidragon]

When aborting an encoding, MeGUI shuts down. I don't have the 'Shutdown at end of coding' checkbox checked.

(version 0.2.3.2)

[Doom9]

@digidragon: what about the corresponding checkbox in the settings?

[digidragon]

The 'Shutdown at end of coding' checkbox in the settings dialog is also unchecked.