MeGUI development

[Sharktooth]

well, when the Adaptive Quantization will be submitted to the SVN the --aq switch will be removed and --aq-strenght 0 will be the default.

[Sirber]

so no AQ by default?

[Sharktooth]

it will be removed coz it is redundant. setting --aq-strenght to something other than 0 will enable AQ. However the patch is still not updated so until i get a new one it will continue to work as it was implemented in MeGUI.

[Doom9]

well, unless I have a timeline and can synchronize development with it, it doesn't make much sense right now to start planning. I have no big projects though, basically stuff that can be finished in one day or two.

[Doom9]

I've just updated the link to the latest sources. I hope I haven't introduced too many bugs in the new release as I might not have proper internet access to upload bugfixes next week.

[berrinam]

An addition to MeGUI I have done recently that I find useful is the option to 'Export Jobs to Batch file'. I put this in the menu, however this is probably not the best place. It exports the currently selected jobs to a batch file. The menu-handler I used is below.

private void mnuToolsBatchExport_Click(object sender, System.EventArgs e)
{
if (this.queueListView.SelectedItems.Count > 0)
{
this.saveFileDialog.Title = "Enter name of output";
this.saveFileDialog.FileName = "";
this.saveFileDialog.Filter = "Batch files (*.bat)|*.bat";
if (this.saveFileDialog.ShowDialog() != DialogResult.OK)
return;
StreamWriter output = new StreamWriter(this.saveFileDialog.FileName);
output.WriteLine(":: MeGUI generated batchfile");
foreach (ListViewItem item in this.queueListView.SelectedItems)
{
Job job = (Job)jobs[item.Text];
if (job != null)
{
// Label our jobs
output.WriteLine(":: " + job.Name);
output.WriteLine(job.Commandline);
}
}
output.Close();
}
}Feel free to include it if you want

[Doom9]

hmm.. why would you run something in batchfile instead of in MeGUI, thus losing quite a bit of functionality? even if we're thinking about problematic jobs and people unfamiliar with the commandline so that they could run a commandline and get additional error messages, those people would double click on the batchfile, it would run and then close and you lost the output again.

[berrinam]

You're right. Anyway, it was quick to write, and I found it useful when I was trying to narrow down the problem with x264+AQ, because I could set jobs, knowing some would error out, and come back later to see which ones failed where. Probably not an overwhelmingly useful function.

[hellfred]

hmm.. why would you run something in batchfile instead of in MeGUI, thus losing quite a bit of functionality? even if we're thinking about problematic jobs and people unfamiliar with the commandline so that they could run a commandline and get additional error messages, those people would double click on the batchfile, it would run and then close and you lost the output again.
The closing is not a problem, when you simply put aPAUSE in the last line. Then the cmd-Window will promt and wait for the user to "press any key.." before closing.
For me, being curious and always eager to learn how things are done, it would be nice to have the possibility to see the actual command lines, but I do know that you are most probably not very keen on having yet more bugreports form people messing with the bat-file (and not stating it).

Hellfred

[Yuri Khan]

why would you run something in batchfile instead of in MeGUI, thus losing quite a bit of functionality?
What can you do with a job queue that you can’t do with a batch file? Can you put 26 jobs in the queue, then realize you’ve made a mistake and change one setting in all the jobs at once? Can you clone a whole queue, modify a few things, and compare results afterwards? With a batch file, I can. What’s better, I can take one job in a batch file and automatically generate all the other jobs by using the first one as template.

I suppose I could do the same by editing the jobs queue XML file manually, but providing the same functionality in the GUI is very costly.

Batch files are a natural format for job queues — not only video encoding queues, but all kinds of jobs.

[Doom9]

The closing is not a problem, when you simply put aI may not use batchfiles a lot.. but that one I do know ;)

it would be nice to have the possibility to see the actual command linesBut you can.. what do you think the "show commandline" checkbox in every codec configuration window is for? Try it out.. you can see commandline changes in real time as you configure the codec. Plus, before starting each job, its commandline is dumped to the log.

What can you do with a job queue that you can’t do with a batch file?How about postponing, collecting stats, update the settings graphically (not everyboy knows the 100 cli parameters x264.exe has), move up/down without copy/paste. And as far as cloning goes, yes you can.. you'll have to edit stuff in your batchfile and you have to create jobs in the right order in the GUI. And mass update: you have to edit commandlines, line by line.. few people are actually capable of doing that. Anyway, both have their advantages but MeGUI was never meant as a glorified batchfile creator.. those who work with batchfiles shouldn't need a GUI, and those that need a GUI don't really need batchfiles.

Also, to me a batchfile output is like making a statement that I don't trust my job handling. But I do trust it enough so I don't think even for debugging purposes it's necessary.

[Yuri Khan]

How about postponing, collecting stats
rem and move, respectively.
update the settings graphically (not everyboy knows the 100 cli parameters x264.exe has)
Well, that’s where the GUI is convenient — to build the template command line with common switches.
move up/down without copy/paste.
For me, copy/paste is at least as convenient as Move up/down buttons, and probably more so because I can copy/paste several lines at once.
And mass update: you have to edit commandlines, line by line.. few people are actually capable of doing that.
Oh no, you don’t. With batch files, you do a context search-and-replace.
Anyway, both have their advantages but MeGUI was never meant as a glorified batchfile creator.. those who work with batchfiles shouldn't need a GUI, and those that need a GUI don't really need batchfiles.
I’d say it a little differently: those who work with batch files are capable of making their own UIs tailored specifically to their own needs.

I understand that I am not in the target audience of MeGUI and have no problems with that; sorry if I said anything to offend you.

[berrinam]

EDIT: This doesn't work with x264-only or snow-only. I will fix it if you are interested.
EDIT2: Should be fixed for all modes now (it has new code for Form1, and there is a new attachment).

How about being able to create a default configuration for OneClick?

Two new classes attached, along with an updated MeGUISettings and SettingsForm (I doubt you've modified them -- if you have, I can just tell you the changes), and a small bit of new code for OneClickWindow and Form1 as follows:

OneClickWindow: at the end of the constructor, add // Do extra defaults config (same code as in OneClickDefaultWindow)
// strings
if (audioProfile.Items.Contains(mainForm.Settings.OneClickDefaults.AudioProfileName))
audioProfile.SelectedItem = mainForm.Settings.OneClickDefaults.AudioProfileName;
if (videoProfile.Items.Contains(mainForm.Settings.OneClickDefaults.VideoProfileName))
videoProfile.SelectedItem = mainForm.Settings.OneClickDefaults.VideoProfileName;
if (containerFormat.Items.Contains(mainForm.Settings.OneClickDefaults.ContainerFormatName))
containerFormat.SelectedItem = mainForm.Settings.OneClickDefaults.ContainerFormatName;
if (sizeSelection.Items.Contains(mainForm.Settings.OneClickDefaults.StorageMediumName))
sizeSelection.SelectedItem = mainForm.Settings.OneClickDefaults.StorageMediumName;

// bools
dontEncodeAudio.Checked = mainForm.Settings.OneClickDefaults.DontEncodeAudio;
signalAR.Checked = mainForm.Settings.OneClickDefaults.SignalAR;
splitOutput.Checked = mainForm.Settings.OneClickDefaults.Split;

// ints
if (mainForm.Settings.OneClickDefaults.SplitSize > 0)
splitSize.Text = mainForm.Settings.OneClickDefaults.SplitSize.ToString();
if (mainForm.Settings.OneClickDefaults.Filesize > 0)
fileSize.Text = mainForm.Settings.OneClickDefaults.Filesize.ToString();
horizontalResolution.Value = mainForm.Settings.OneClickDefaults.OutputResolution;

// Clean up after those settings were set
sizeSelection_SelectedIndexChanged(null, null);
containerFormat_SelectedIndexChanged(null, null);
audioProfile_SelectedIndexChanged(null, null);
VideoProfile_SelectedIndexChanged(null, null);
dontEncodeAudio_CheckedChanged(null, null);
signalAR_CheckedChanged(null, null);
splitOutput_CheckedChanged(null, null);
Form1: change mnuToolsSettings_Click to private void mnuToolsSettings_Click(object sender, System.EventArgs e)
{
#if FULL
SettingsForm sform = new SettingsForm(videoProfiles, audioProfiles, videoProfile.SelectedIndex, audioProfile.SelectedIndex);
#else
SettingsForm sform = new SettingsForm();
#endif
sform.Settings = this.settings;
if (sform.ShowDialog() == DialogResult.OK)
{
this.settings = sform.Settings;
changeVideoOutputExtention(); // this is here to prevent output extension mismatches when the x264 encoder is changed
}
}

[berrinam]

Just to alert you, I have fixed the problem with the above code.

[Doom9]

I'm hoping you've tested the actual functionality more than the -new.zip you've attached.. it lacked that adapted menu code to open the settings window, and the x264 release wouldn't build without changes either.

[berrinam]

@Doom9: Did you include the code in my post as well as the attached files? It woked fine for me when I did. NB: v2.2.9 seems to be missing the OneClickWindow code which I posted.

[Doom9]

Did you include the code in my post as well as the attached files? No, for some reason I took your first sentence as "you can just copy in the files and be done with it unless you have made changes to the oneclick and main form".

Turns out I should've bothered to actually read your whole post. Sorry about that :(

[redfordxx]

I am compressing x264 using MeGUI. I have queue of cca 10 encodes.
Select last job and use "move down button". The selection disappears. Once more pressing the down button and got this.See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: index
at System.Windows.Forms.SelectedListViewItemCollection.get_Item(Int32 index)
at MeGUI.MeGUI.MoveListViewItem(ListView& lv, Boolean moveUp)
at MeGUI.MeGUI.downButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
megui-x264
Assembly Version: 1.0.2131.35386
Win32 Version: 1.0.2131.35386
CodeBase: file:///C:/Program%20Files/x264/megui-x264.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
babduss4
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
fhdzw45o
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
yegudxpo
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.Up is the same.
Maybe some1 is interrested...

[Sharktooth]

RDO for B-Frames should be disabled when b-frames = 0.
Needs CABAC.

[bond]

Trellis should be disabled when --subme < 6 (no RDO).afaik you dont need subme6 when wanting to use trellis
but you do need cabac to use trellis!

[Sharktooth]

mooo :D

[Doom9]

are you trying to confuse me? now I don't know what to code anymore

[Sharktooth]

i edited my post with the right "conditions".

[Doom9]

RDO for B-Frames should be disabled when b-frames = 0.Done.
but you do need cabac to use trellis!It was like that already.

Did I miss anything else? (I got the up/down think taken care of as well).

[Sharktooth]

i was convinced disabling cabac didnt disable trellis...
damnit i already got a pair of googles... maybe i need better ones...

[Sharktooth]

fix for B-RDO behaviour in conjunction with b-frames
in x264ConfigurationDialog.cs

...

else if (this.x264NumberOfBFrames.Value == 0)
{
this.x264AdaptiveBframes.Enabled = false;
this.x264WeightedBPrediction.Enabled = false;
this.x264PyramidBframes.Enabled = false;
this.bRDO.Enabled = false;
x264BframePredictionMode.Enabled = false;
x264BframeBias.Enabled = false;
}

...

and


...

if (this.x264NumberOfBFrames.Value >= 1)
{
this.x264AdaptiveBframes.Enabled = true;
this.x264WeightedBPrediction.Enabled = true;
this.x264PyramidBframes.Enabled = false;
if (this.x264SubpelRefinement.SelectedIndex >= 5) // RDO & B-frames are enabled, enable RDO for B-frames
this.bRDO.Enabled = true;
if (!x264BframePredictionMode.Enabled)
x264BframePredictionMode.Enabled = true;
if (!x264BframeBias.Enabled)
x264BframeBias.Enabled = true;
}
...

and


...
private void x264SubpelRefinement_SelectedIndexChanged(object sender, System.EventArgs e)
{
if (this.x264SubpelRefinement.SelectedIndex >= 5 & this.x264NumberOfBFrames.Value >= 1) // RDO & B-frames are enabled, enable RDO for B-frames
this.bRDO.Enabled = true;
else
this.bRDO.Enabled = false;
this.showCommandLine();
}
...


The trellis thing is more tricky... i'll think about it tonight.

New binaries: http://forum.doom9.org/showthread.php?p=739329#post739329

[Sharktooth]

In CommandLineGenerator.cs:
switch (xs.EncodingMode)
{
case 0: // ABR
sb.Append("--bitrate " + xs.BitrateQuantizer + " ");
break;
case 1: // CQ
sb.Append("--qp " + xs.BitrateQuantizer + " ");
break;
case 2: // 2 pass first pass
sb.Append("--pass 1 --bitrate " + xs.BitrateQuantizer + " --stats " + "\"" + xs.Logfile + "\" ");
break;
case 3: // 2 pass second pass
case 4: // automated twopass
sb.Append("--pass 2 --bitrate " + xs.BitrateQuantizer + " --stats " + "\"" + xs.Logfile + "\" ");
break;
case 5: // 3 pass first pass
sb.Append("--pass 1 --bitrate " + xs.BitrateQuantizer + " --stats " + "\"" + xs.Logfile + "\" ");
break;
case 6: // 3 pass 2nd pass
sb.Append("--pass 3 --bitrate " + xs.BitrateQuantizer + " --stats " + "\"" + xs.Logfile + "\" ");
break;
case 7: // 3 pass 3rd pass
sb.Append("--pass 3 --bitrate " + xs.BitrateQuantizer + " --stats " + "\"" + xs.Logfile + "\" ");
break;
case 9: // constant quality
sb.Append("--crf " + xs.BitrateQuantizer + " ");
break;
} // now add the rest of the x264 encoder options
Where's "case 8" ?!? It should be Automated 3pass... guess that's why it doesnt work well...

[Doom9]

Where's "case 8" ?!? It should be Automated 3pass.Yup, but you never get there because when generating jobs, the first job generated will be a 3 pass first pass, the 2nd will be a 3 pass 3rd pass and the 3rd one will be a 3pass 2nd/3rd pass depending on your settings.

[Sharktooth]

ok... then the problem is in "turbo"... damnit i dont even know c#...

[Randall]

looks like case 3 does nothing as well... just a comment. and you should probably have a default case no?

I know a little bit of C#. Where is "turbo" located?

[Doom9]

I don't feel like coding but it's going to take me longer to tell you how megui works than for me to locate and fix whatever is broken.. it's all menial things, a few lines per problem max. don't worry about that switch, it does what it should and I don't need a default case if I know beforehand what values that are going to arrive in that switch.

[Randall]

sorry man I was only looking a one function there. ;) i know what you mean about explaining how some software works. sometimes it's easier to just go in there and fit it yourself. my co-worker spent like 20 minutes one time explaining a fix that i needed to make that ended up being a one-liner. d'oh!

[Sharktooth]

default case isnt needed coz the value is retrieved from a drop down list that already has a default value.
turbo is not an x264 option. it's a checkbox in the x264ConfigurationDialog.
When ShowCommandLine() is called it checks if Turbo is enabled or disabled...
private void checkBox_CheckedChanged(object sender, System.EventArgs e)
{
this.showCommandLine();
}
... but i must be blind coz i cant find where the showCommandLine function is...

EDIT: found it.... eheh

[Doom9]

the best thing you can do right now to help is try out combinations of the gazillion options there are, so that this week-end I have a list of all the cases that still need work and I can solve them all together..
@Sharktooth: you're looking in the wrong place.. it's more productive if you focus on trying to find more issues in the GUI.

[Randall]

use ctags http://ctags.sourceforge.net/ to dump out all of the functions, then you can jump right to it with your favorite editor. I use gvim.

[Sharktooth]

ok. the big problems are:
1) trellis dropdown gets enabled if you exit the dialog and re-open it coz it's default enabled on load...
a check should be added the _Load event to esabilish if CABAC is enabled or not... and consequently enable/disable trellis dropdown.
2) the disabled controls remains in the command line generation (if they're checked or different than default value).

[Sharktooth]

3) when rising b-frames from 0 to 1 P4x4 checkbox control gets disabled (grayed out) even with unrestricted level.

EDIT: however navigating into megui code is a pain in the ... :|

[Randall]

find . \( -name '*.cs' -a -print \) | ctags -L - will save your life. after that just open up any source file with gvim, highlight the function you wanna find, do a "ctrl ]" and you're there. no more headaches or grepping everywhere for code. http://cantor.ee.ucla.edu/~jsab/vim_ctags_cpp.html

[Doom9]

the disabled controls remains in the command line generation (if they're checked or different than default value).which ones?

[Sharktooth]

which ones?
every grayed out but still checked or different from default control.
example: select high profile... select custom partitions... check all MBs.. then select baseline profile... select show commandline.
8x8dct and I8x8 are still in the commandline even if baseline profile grayed them out and should have removed them...

[charleski]

I'm not sure what the rules are for submitting development suggestions and code - I looked through the pages on this thread and couldn't find anything so I hope it's OK to just post this.

While playing around with the profiles Sharktooth posted I got the idea that it would be nice to be able to do so in a 'safe' manner, so that you could go back to the original without having to re-extract it from an archive. Since it's clear that doom9 just loves writing GUI code I downloaded VC# 2005 Express and had a go at doing the modification myself.

I thought I'd present what I have working at the moment and ask the following questions:
1) Are you interested in this sort of stuff?
2) Is there anything I'm doing horribly wrong? - I noticed that VC#Express had to convert the project before opening it. Also, I learnt programming in Pascal (i.e. many years ago), but I think my modifications are in line with acceptable object-oriented practice.
3) Should I be doing anything else in terms of managing code versions?

I wrote a changelog which I'll append here:

10-Nov-2005

Altered the way in which MeGUI handles changes to the video configuration in the x264 dialog. The aim is to allow n00bies like me to tinker with proper profiles such as the ones released by Sharktooth without overwriting them and forgetting what settings they've changed.

There is a new option in the MeGUI Settings dialog: Safe Profile Alteration.

If this is checked, upon exiting the dialog by clicking OK after having changed any of the encoder settings APART from bitrate, SAR and zones, the program will create a new profile called "<old profile name>Tweaked" which contains the new settings. The user may subsequently revert back to the old profile at any time as it remains intact.

I excluded bitrate, SAR and zones from the protection as I thought those were elements that users might want to alter according to the particular video being encoded.

At the moment this profile protection only operates on the x264 configuration.

Modified files:

x264ConfigurationDialog.cs (the bulk of the new code)

SettingsForm.cs
SettingsForm.rsx
MeGUISettings.cs
Form1.cs
(these 4 are altered to present the new Safe Profile Alteration setting and pass it to x264ConfiurationDialog)

I have not fully tested this yet, though it seems to work on the tests I've done so far. I just wanted to see if there's interest in me carrying on with this and expanding the protection to the other codecs as well. The changes were made on the 0.2.3.1b version of MeGUI.

Link to modified code (http://homepages.nildram.co.uk/~cajking/MeGUI-src.0.2.3.1b MODIFIED.rar)

[Doom9]

@charleski: unfortunately there are two things that need to be sorted out before I can upgrade the project to Visual Studio 2005 (I suppose it doesn't matter if I use Pro (have to for work) or Express): One is I need to make sure I can still compile the project for .NET 1.1 (I'm sure I'll dump that requirement sooner than later), and what goes along with it is to find out if I can have the old and new visual studio installed in parallel.

Also, I see the solution to all this deactivation crap as one method that contains the whole activation/deactivation logic and which is called with each show showcommandline call, as well as when a profile is loaded (opening of the window). What is causing problems right now is mostly that the deactivation crap is in the various event handlers for the various gui events.. so when you load a profile, there's a variety of things that go on and that interfere with each other (so I also have to deactivate the firing of any events until the whole profile has been loaded). Then I also have to make sure there's corresponding logic in the commandlinegenerator.. and that's that. But having the logic in two places is always prone to error.. but it's the only way to handle triple state for GUI elements that just have two states.

[charleski]

OK, thought it would be alright since you advertised the Express series on the front page :).

If you look at my code you'll see that I had to stick a profileAltered flag into the event handlers as well :/. I wasn't too happy about that, but the logic needs some way of knowing if the user has modified the settings in order to work sanely. An alterantive would be just to compare the current settings to those stored in the profile on exiting the dialog though. Which, now I think of it, might be a neater solution.

[Sharktooth]

@charleski: unfortunately there are two things that need to be sorted out before I can upgrade the project to Visual Studio 2005 (I suppose it doesn't matter if I use Pro (have to for work) or Express): One is I need to make sure I can still compile the project for .NET 1.1 (I'm sure I'll dump that requirement sooner than later), and what goes along with it is to find out if I can have the old and new visual studio installed in parallel.
Yes, it's possible. use command line compilers from the SDKs and modify the paths to point the 1.1 framework. You can even use the 2.0 compilers with 1.1 libs. It's what i did to compile the MeGUI binaries for .NET 1.1.
For what concerns having both VS 2003 and VS 2005, it should be possible coz they install in different folders, but i dint try it coz i migrated all projects to 2005.

[Sharktooth]

I forgot to say Auto-3pass is buggy... expecially with turbo option (look at the command lines).

[Randall]

Manual 3-pass encoding without turbo should be fine though correct?

[Sharktooth]

it should

[charleski]

I've fixed a bug in my code and altered it so it no longer uses a flag in the event handlers. Instead I created a new method in x264Settings that checks whether one set of encoder settings is substantially different to another.

The link given above points to the latest version.

[Tima]

When encoding XviD for more than 24 hours, MeGUI's status displays running time as "actual_time mod 24_hours". Remain time is OK.

I used unpatched 0.2.3.1b, encoding XviD with latest Celtic Druid's build of Mencoder.

[Sharktooth]

"latest Sharktooth's build of mencoder"??!?
not really... i never uploaded any build of mplayer/mencoder made by me.