MeGUI Bug-Report Thread

[charleski]

There are older .NET 1.1 versions of megui on the SourceForge Files page
https://sourceforge.net/project/showfiles.php?group_id=156112#files.
The ones compiled for 1.1 are 0.2.3.1029a and before.

[stax76]

I know what's up with the native error dialog on startup because I learned it the hard way recently. If you run a .NET application and it crashes with the native error dialog while startup then you got a exception somewhere in the ctor of the startup form, simply use a try catch block and add some logic to handle the exception.

[MetalPhreak]

Problem can be seen in the screenshot here: http://img65.imageshack.us/img65/4308/progress0ql.jpg

The time remaining and time elapsed are both completely wrong.
This is using Sharktooths' r399 build.

[berrinam]

Me too. A fix will come soon. For the time being, turn off Autostart Queue.

[Doom9]

@lexor: you can build your own megui-x264 build.. it should be compilable under 1.1 with no changes except for the compile.bat file.. it has links to the 2.0 compiler (%windir%\Microsoft.NET\Framework\v2.0.50727\csc), replace the v2.0 directory with the name of your 1.1 directory and you should be fine. The full release however will not compile under 1.1. That way, you know you have the same code for both builds and the only thing different is the runtime.

[de66ka]

Since I've updated Megui from 02.3.1b to 02.3.2017 the Avisynth Generator doesn't work anymore. It gaves me the error "DGIndex reported......" (see snap1.jpg) when i load the *.d2v file into the generator. When I downgrad again to 02.3.1b all work fine.

[berrinam]

A fix will come soon.
Fixed

[Mutant_Fruit]

When using the AviSynth script creator and choosing an AVI file, a dodgy avs file is generated. The resulting file that is saved is loading up the "temp.avs" file as opposed to the actual video file selected. This means that if i make a few avs files with the generator, they'll all point to teh same temp.avs file, and if i delete the temp.avs file, none of em will work at all.

Gonna make a fix now assuming i can spot the error :p

[lexor]

I'm at a loss at the apathy towards this issue. I mean don't you guys share your computer with other family members? An encode that takes 12 hours for first pass and 15 hours for second, bound to conflict with your family's desire to use the mahcine. Doom I know you have win xp installed, don't you get this problem with user switching? I mean it's so easy to check, just start some job, switch users and switch back again. What's this suddent need for me to be a compiler and debugger? Someone must have old sharktooth's build lying around (sharktooth for one), I'm willing to put up time for testing an reporting, but I have neither energy nor time to pretend like I'm one of the developers.

[Sharktooth]

Another bug (MeGUI-x264):
http://www.webalice.it/f.corriga/megui/meguiibug2.png

Menues vanished and same problem as the previous bug.

[Mutant_Fruit]

@lexor: I'll try to take a look at it, but i'm really new to MeGUI, so i spend a lot of time just browsing the code trying to get a feel for it. Webpages are no bother to me, they're simple as compared to Windows applications :p

[Doom9]

I'm at a loss at the apathy towards this issue.Apathy? Why did I waste my time explaining to you then how you can compile on your own (without any programming knowledge whatsoever..) can create a .NET 1.1 build based on the latest build for your tests? Oh wait, you expect me to do that for you, including reinstalling .NET 1.1 which I already eliminated from my machine. Am I on the right track?

In addition, wouldn't it be reasonable that YOU would first try on another box before pointing the finger at us? While I'm very possessive of my box and would never let anybody else us it, just for you I created another user account. Then I started encoding on my primary account (an admin account), switched to the second one.. encoding kept going. Then I aborted, went to the second account (one with limited privileges), started megui there (the latest CVS checkout.. done just 10 minutes ago, built with the compile script that comes with it), then switched back to the account I'm typing this from. I see from the CPU usage that encoding is still going strong, in fact, it hardly takes a performance hit at all since I only have a few resource-friendly apps running. By the way the job I'm encoding is a standard x264 one with all the default settings, and my x264 build is revision 389 from Sharktooth. Bottom line, I can't reproduce it.. it works as it's supposed to.

[Mutant_Fruit]

can create a .NET 1.1 build based on the latest build
That won't work afaik. There are a good few .net 2.0 specific items in the code now, so its now impossible to compile the current source against .Net1.0 without changing the source code.

[Doom9]

That won't work afaik. There are a good few .net 2.0 specific items in the code now, so its now impossible to compile the current source against .Net1.0 without changing the source code.I tried and indeed.. but the thing is.. all errors come from classes that should be inside an #if directive and not be compiled anyway in the x264 mode..
However, the point is now moot because the problem seems unreproducible.. perhaps you can make the same experiment I did (MeGUI is still encoding on the secondary account and has been throughout my dinner).

[lexor]

Well I'll be damned, it is fft3dgpu that's incompatible with user switching, but I did test it without that filter before though, and it would still break, now it does not. I reinstalled Std package since then though. Perhaps that first time it crashed it corrupted some files while writing to them? Dunno, anyway sorry for the inconvenience.

And for the record I never asked anyone to compile anything for anyone at any point, all I wanted was old .7z or Sharktooth's, that's all.

I'll go bug fft3d dev now :)

[Pasqui]

Since a few versions (0.2.3.2017 if I remember correctly) I do not get the FPS displayed in the Progress Status window when encoding with x264. All the other parameters (current video frame, video data, projected filesize, time elapsed and time remaining) are correctly displayed with version 0.2.3.2022.

[Mutant_Fruit]

what exactly is the problem, it seems to show up fine for me.

Are you using the full version, or x264 specific version? Show a screenshot of the problem if you can.

[Doom9]

@Pasqui: they use a comma as decimal separator in your country, correct?

[Pasqui]

I'm facing the fps bug with the complete megui version on a French WinXP (where the separator between digits is a comma and not a dot).
Here is the picture:
http://img304.imageshack.us/img304/7537/statuswindow7cf.gif (http://imageshack.us)

[Doom9]

Do you remember the old problem where you never got a status update? This is the same.. the fps parser chokes because I forget to force the neutral locale that uses the dot as decimal separator. But I set up all line parsing to catch all errors and just return 0.. that's why you get the rest of the updates. The progress is directly calculated by MeGUI and not taken from the x264 commandline.. that's why you have that.

[Pasqui]

Do you remember the old problem where you never got a status update? This is the same.. the fps parser chokes because I forget to force the neutral locale that uses the dot as decimal separator. But I set up all line parsing to catch all errors and just return 0.. that's why you get the rest of the updates. The progress is directly calculated by MeGUI and not taken from the x264 commandline.. that's why you have that.
Thanks for the info. I thought it was probably due to our "evil" comma ;)

[berrinam]

Menues vanished and same problem as the previous bug.
Do you mean by same problem as the previous bug the 'no jobs waiting. nothing to do' error message? That hasn't been fixed yet

[Pasqui]

Using deinterlace detection on a 4:3 vob file, I got the following error: "unexpected value". Here is the log file:

[charleski]

Well I'll be damned, it is fft3dgpu that's incompatible with user switching
What did I say in my first post about this? &$%£

There are some basic tactics to adopt in diagnosing any fault, and the first is to isolate it. Remove anything that might be contributing to the problem until you have the most basic configuration possible that still fails. Obviously fft3dgpu won't survive user-switching (!!!!) - the status of the GPU is not preserved across user-states. The miracle of fft3dgpu is that it works at all, as it's running on such a wide range of different hardware while interfacing through DirectX while the host processor and bus is running flat-out. If it works, great, if it doesn't just use the original host version.

[Doom9]

@Pasqui: as soon as I upload my latest sources, the FPS indication will be back for those locales not using a dot as decimal separator.

[Doom9]

hot damn.. CVS is screwing me again.. tortoise crashes when I try to run an update and pretty much anything.. how the heck am I suppose to add my changes now?

[berrinam]

Which version are your sources based on?

[Doom9]

based on the build I last checked in.. so that's 2012. I'm not quite sure what I'm supposed to do now.. I have 28 changes files.. I managed to add the new ones, and that doesn't break anything, but I'm scared as hell to do anything else and break everything.

[berrinam]

Gee, 2012 is quite a long time ago...

One thing you could do, but I know you're not going to like it, is start a new folder with the latest source, and individually merge each file (assuming you have WinMerge, it's not TOO hard a job).

Alternatively, I've just generated a patch from version 2012 to 2023, so perhaps that could be applied to your version. Maybe that would be slightly less work

[Doom9]

@berrinam: please have a look here: http://forum.doom9.org/showthread.php?t=95863&page=63 . And do you have MSN?

[Pasqui]

@Pasqui: as soon as I upload my latest sources, the FPS indication will be back for those locales not using a dot as decimal separator.

Thanks Doom9, it's working fine now :D

[AgentX]

AviSynth script generator has a cosmetic bug:

In Mpeg Options you can read Colour Correctio.
Obviously it should be Colour Correction.

[AgentX]

Crash on 'Analyse' because of missing Decomb.dll. This should be caught
Description: N/A
Status: Fixed in version 0.2.3.2020

Well, I just tried it in 0.2.3.2024 and MeGUI still does crash silently.
I should copy that Decomb.dll somewhere. :rolleyes:

EDIT:
Okay, now I know what's going wrong.
It's not the decomb.dll, but it seems that AviSynth doesn't support Unicode characters in directory names.
Look, I'm using a spanish Windows system, and the 11th line in the temporary autodeinttemp-avs.avs fails:

<snip>
file="C:\Documents and Settings\AgentX\Configuración local\Temp\interlace.log"
<snip>
c = WriteFile(c, file, "a", "sep", "b")
<snip>

Being a spanish system, there's a "ó" and a several spaces in the filename.
One of these make trouble.
BTW, I'm using AviSynth 2.56 (sep 4 2005).
Temporary solution, use file="%SystemDrive%\interlace.log".

[Doom9]

ie. user installs it in "c:\windows" and uninstaller removes whole "c:\windows". That's not a GUI bugreport though, is it? However, it teaches people the hard way that the windows directory is not meant for software installation ;)

[foxyshadis]

Odd, though, sharktooth fixed that ages ago. (Someone else did the same to their system32 folder.) He must have updated the installer or something.

[Doom9]

btw, here are two known and already fixed (not yet in the CVS) bugs:

1) FPS indication for xvid_encraw is completely wrong in the queue
2) elapsed and projected end time can go out of whack in video encoding and muxing.

[berrinam]

Well, I just tried it in 0.2.3.2024 and MeGUI still does crash silently.
I should copy that Decomb.dll somewhere. :rolleyes:

Temporary solution, use file="%SystemDrive%\interlace.log".
See if you can break version 0.2.3.2026:D
I've put a lot of error catching around, because no AviSynth bug should cause MeGUI to crash.

[AgentX]

See if you can break version 0.2.3.2026:D
I've put a lot of error catching around, because no AviSynth bug should cause MeGUI to crash.
I would like to, but on Sourceforge there's still 0.2.3.24 :(

[starkebn]

In the Audio Encoding section setting a encoding profile then switching to Audio Radio button 2 will set the same profile. Changing the profile will then also change it for radio button 1.

In the MP4 muxer Audio section setting a name then switching to radio button 2 will keep the same name. Changing the name will then also change it for radio button 1.

This happens in 2.3.2024 as well.

[Avish]

I hope I've posted in the correct thread...;)

I'm using all the latest versions: meGUI 14th Jan Version, DGIndex 1.4.6b4, x264 13th Jan Version.

Here is the script created using AviSynth script generator :

LoadPlugin("N:\Softwares\Audio-Video-related\Video related\DVD_related\XviD_Encoding_Tools\dgmpgdec146b4\dgdecode.dll")
mpeg2source("M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.d2v")
tfm(d2v="M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.d2v").tdecimate()
#crop
LanczosResize(720,320)
#denoise

Here is what MeGui says after doing Deinterlacing Analysis:
Source type: Source is declared telecined.
Source is declared tff by a margin of 234 to 15.

& then it automatically chooses TIVTC option...

When i press preview...there is nothing in it...just a thin black stripe...

Then I saved the script, queued it, clicked Srart...it finished in 1-2 seconds giving me this error:

avis [error]: unsupported input format (DIB )
could not open input file 'M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.avs'
desired video bitrate of this job: 1298 kbit/s - obtained video bitrate: 0 kbit/s

Here is a complete log from meGUI:

Next job job2 is a video job. encoder commandline:
--bitrate 1298 --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --subme 6 --trellis 1 --analyse all --8x8dct --me umh --progress --no-psnr --output "M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.mkv" "M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.avs"
successfully started encoding of job job2
job commandline: --bitrate 1298 --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --subme 6 --trellis 1 --analyse all --8x8dct --me umh --progress --no-psnr --output "M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.mkv" "M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.avs"
----------------------------------------------------------------------------------------------------------

Log for job job2

avis [error]: unsupported input format (DIB )
could not open input file 'M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.avs'
desired video bitrate of this job: 1298 kbit/s - obtained video bitrate: 0 kbit/s
----------------------------------------------------------------------------------------------------------

I searched what is TIVTC in the forum, downloaed it & put the dll in avisynth plugin folder & also in the meGUI folder...but still the same thing...same error...

Just 2 days back I successfully encoded War of the Worlds using the meGUI ...but this time its not working... am I doing somthing wrong guys ?? pls Help me...

[Doom9]

When i press preview...there is nothing in it...just a thin black stripe...Open the script in a media player.. it will show you the error. It seems you forgot about point 5 in the reporting guidelines (good job otherwise):
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.)

[foxyshadis]

Was the loss of the bitrate calc in x264 conditional intentional, or an accident? Because it's the best and I'd hate to lose it there.

[berrinam]

Was the loss of the bitrate calc in x264 conditional intentional, or an accident? Because it's the best and I'd hate to lose it there.
Is this due to the following bug?
MeGUI-x264 has no menus
Description: See http://forum.doom9.org/showthread.php?p=768048#post768048
Status: Not yet solved


In the Audio Encoding section setting a encoding profile then switching to Audio Radio button 2 will set the same profile. Changing the profile will then also change it for radio button 1.This is intentional.

In the MP4 muxer Audio section setting a name then switching to radio button 2 will keep the same name. Changing the name will then also change it for radio button 1.

This happens in 2.3.2024 as well.
This was fixed in 0.2.3.2026. Just wait for a new release

[Avish]

Open the script in a media player.. it will show you the error. It seems you forgot about point 5 in the reporting guidelines (good job otherwise):
No I didnt forgot about it...Here is the error MPC showed :
TFM: d2v file is not a d2v file or is of unsupported format!
(M:\DVDs\Indiana Jones & The Last Crusade\Indi_3.avs, line 3)

I thought that it's not mentionable enough...coz when i deleted the line 3 in script, it showed me the preview perfectly (ofcourse without deinterlacing) ;)
so the error must be in the TIVTC thing...which I cant figure out...

And yes, all the source files are playing perfectly (the soundtrack & the files to be muxed, etc)

[Doom9]

I thought that it's not mentionable enough...coz when i deleted the line 3 in script, it showed me the preview perfectly (ofcourse without deinterlacing)since you have the error in playback, obviously it's also the problem in encoding ;) So in turn, this is an AviSynth script problem, nothing that would relate to MeGUI or x264. I have no idea why decomb is in the script but isn't used.. or perhaps my filter knowledge is just too limited (all the scripting problems just go to show why the ideal script only contains 3 lines)

[Avish]

since you have the error in playback, obviously it's also the problem in encoding ;) So in turn, this is an AviSynth script problem, nothing that would relate to MeGUI or x264. I have no idea why decomb is in the script but isn't used.. or perhaps my filter knowledge is just too limited (all the scripting problems just go to show why the ideal script only contains 3 lines)

:confused: Then what should I do with this TIVTC thing which the meGUI automatically chooses after its deinterlacing analysis...whom should I ask about this ?? Pls guide me in the right direction ;)

[berrinam]

I implemented the source detection, and it automatically adds what you had to the script. The script generated for you seems in order, and it follows the instructions given in TIVTC's guide. This script works for me, so I'm not sure what's up. You should try making sure that (a) you made the d2v file with the latest version of DGIndex, and (b) you have the latest version of TIVTC.

If it still doesn't fix it, you can delete the d2v=whatever.d2v bit inside tfm(), but the guides recommend that parameter be set, so that's what I did.

EDIT: When I update to the most recent version of DGIndex, I get the same error as you. Time to do what I said immediately (whoops, didn't mean to stop there) above this paragraph: remove the d2v=whatever.d2v bit. I will also update MeGUI accordingly.

[berrinam]

Ok, I have updated the script generation. It now no longer adds the d2v=whatever.d2v bit inside tfm(). This is compatible with the newest version of DGIndex, but I'm not sure what happens with previous versions. The net result is that you should use DGIndex 1.4.6 or newer.

Obviously, the new binaries aren't up yet, but the change should be included in 0.2.3.2029, whenever it is released.

[Avish]

Ok, I have updated the script generation. It now no longer adds the d2v=whatever.d2v bit inside tfm(). This is compatible with the newest version of DGIndex, but I'm not sure what happens with previous versions. The net result is that you should use DGIndex 1.4.6 or newer.

Obviously, the new binaries aren't up yet, but the change should be included in 0.2.3.2029, whenever it is released.
:thanks: That was really fast... I'll try it out as u said & will report back immediately...

BTW Thanks for this great GUI...:) Its getting better & better...:)

[Avish]

If it still doesn't fix it, you can delete the d2v=whatever.d2v bit inside tfm(), but the guides recommend that parameter be set, so that's what I did.

EDIT: When I update to the most recent version of DGIndex, I get the same error as you. Time to do what I said immediately (whoops, didn't mean to stop there) above this paragraph: remove the d2v=whatever.d2v bit. I will also update MeGUI accordingly.

Removing the d2v bit from script worked just fine :) Thanks...