MeGUI Bug-Report Thread

[cyberbeat]

Don't know if these bugs have been reported, but in 2180:

* In the script creator: If the preview window is closed then reopened autocrop will cause a crash.

Please look into these.

I am using build 2180...

1) Actually, just pressing PREVIEW before clicking on AUTOCROP will cause it to crash.

2) AutoCrop seems to have an issue with one scenario. I use the "Non mod16 encoding" so there is no resizing or excess cropping. I then click on AUTOCROP to remove the borders. More often than not it will but "0" for the left border and "2" for the right border. This causes a problem with non Mod16 encoding because the width has to be a multiple of 4 or you get an error. I encode MP4 video with MP4 AAC audio into the MP4 container. I just change the right side to 0 most of the time.

3) There seems to be something weird happening when you select an audio file with delay on the main MeGUI input screen. I create my AVS script for my video and have it save and load it to the main screen. I then select my audio track from the same directory. When I click on config, the delay time has not updated. If I reload the audio file, it then seems to work even while changing profiles. On my next encode, when I load audio from a different directory, it seems to keep the setting of the last file. Is this intended behavior that I have missed while lurking through the discussions or should it be updating always? I am encoding right now. So, if you need more details, I will try to get some more information on what is causing it.

Thanks and great job everyone! I have been lurking on the threads for many weeks and am glad that I finally signed up and am trying to take part in some discussions. :)

[lexor]

hi guys, I'm not sure this is a bug, probably just a suboptimal design decision, but with the autoupdate it keeps telling me there is a new neroaacenc, but then it tells me it's not on the server, but update pops up every time I start megui. something should be done about stuff like that, and I don't mean to simply put the file there, I think it should check if stuff for update actually exists on the server before offering to update.

Thank you for the really nice app, btw!

[Sharktooth]

@lexot: :search:

[Doom9]

well.. I think it's a good idea that we remove neroaac from the autoupdater completely.. it doesn't like like there's going to be a solution for the licensing issue any time soon.

[Sharktooth]

there is...
im adding (in the free time) FTP support to autoupdater. it will be able to get files (and check for updates) from nero FTP...

[~bT~]

In the meantime... just right click and disable check for update for Nero. No more false alarms until u enable it again and hopefully by then Sharx may have sorted the ftp bit.

[cyberbeat]

1) Actually, just pressing PREVIEW before clicking on AUTOCROP will cause it to crash.


I got around this by adding the following code:
In "private void previewButton_Click(object sender, System.EventArgs e)" around line 1000 in AviSynthWindow.cs before the line "player.disableIntroAndCredits();"
reader = player.Reader;

One thing I am not sure about is when you press the PREVIEW button after a CROP, it will show a cropped preview. If you AUTOCROP at this point, it will have new values based on the cropped preview instead of the original footage. (At least, I think that is what is going on.) Would it not be better to have AUTOCROP always use uncropped footage and only let the Mod16 items affect it?


2) AutoCrop seems to have an issue with one scenario. I use the "Non mod16 encoding" so there is no resizing or excess cropping. I then click on AUTOCROP to remove the borders. More often than not it will but "0" for the left border and "2" for the right border. This causes a problem with non Mod16 encoding because the width has to be a multiple of 4 or you get an error. I encode MP4 video with MP4 AAC audio into the MP4 container. I just change the right side to 0 most of the time.

I got around this by adding the following code: (was not sure if this would be appropriate or if it should be a part of VideoUtil.cs)
In "private void autoCropButton_Click(object sender, System.EventArgs e)" around line 1446 in AviSynthWindow.cs after the line "cropBottom.Value = final.bottom;"
if (Mod16Method == mod16Method.nonMod16)
{
while ((cropLeft.Value + cropRight.Value) % 4 > 0)
{
if (cropLeft.Value > cropRight.Value)
{
if (cropLeft.Value > 1)
{
cropLeft.Value = cropLeft.Value - 2;
}
else
{
cropLeft.Value = 0;
}
}
else
{
if (cropRight.Value > 1)
{
cropRight.Value = cropRight.Value - 2;
}
else
{
cropRight.Value = 0;
}
}
}


3) There seems to be something weird happening when you select an audio file with delay on the main MeGUI input screen.
I have not even tried looking more into this one yet...


Sorry if this should not have been posted here... I am just an anxious encoder!

cyberbeat

[OverlordQ]

When I try to use autoencode and specify additional content, once I click Queue, it throws an error:

System.THrowHelper.ThrowKeynotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at MeGUI.baseMuxMindow.convertLanguagesToISO()
at MeGUI.AdaptiveMuxWindow.getAdditionalStreams(SubStream[]& audio, SubStream[]& subtitles, String& chapters, String& output, ContainerFileType& cot)
at MeGUI.AutoEncodeWindow.queueButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)

then it just goes further back into System.Windows.Forms

[foxyshadis]

What language are you trying to rip? Or if it doesn't even get that far, what languages are on the DVD? One of them must be unknown to MeGUI.

[OverlordQ]

What language are you trying to rip? Or if it doesn't even get that far, what languages are on the DVD? One of them must be unknown to MeGUI.

English and Spanish, English Dolby 5.1 Surround EX, English Dolby 2.0 Surround Spanish Dolby 2.0 Surround. I've already ripped the VOB of the section I want.

[Doom9]

@OverlordQ: you have to be more specific.. I tried one audio stream set to english, one audio stream set to spanish and it works out fine here.. you must be doing something else. Note that I enter the autoencode with just an avs selected, no audio and I don't configure anything in the autoencode window.

I found an error in the divxmux muxer: serve it with an avi containing avs.. the muxer errors out with
ERROR: DIVXMUX_INVALIDFORMAT File: D:\DVDs\DVDVolume\VIDEO_TS\test.avi but the stdout/stderr reader doesn't flag this as an error.

And one in the adaptive muxer: select an .264 file, then select an ac3 audio.. at this point the only possible container format is mkv.. yet still all three are listed.
Then press go and naturally it doesn't work out.. in fact you get an exception.

[spunch]

I was wondering if there's any point of further improving the automatic deinterlancer in MeGUI.

MeGUI has a great automatic deinterlancer. I have no idea how it works but for the most part it manages to do a great job, it's just sometimes it picks the entirely wrong deinterlacer, making the clip look worse than the interlaced original.

I know nothing is perfect but i noticed some problematic clips can deinterlace fine with just slight modifications to the avisynth script.

I could provide you with many short clips that seem to have this problem. Let me know if it is practical.

[Doom9]

I could provide you with many short clips that seem to have this problem. Let me know if it is practical.This is berrinam's domain but I'm sure he'd appreciate some material.

[berrinam]

I certainly would like some examples where it doesn't work. If you can narrow it down to a 1-minute sample, that would be great, but if not, then I can make do with bigger samples. PM with details about the clips if you want. Thanks

[carlo_0000]

i don't know if it's alredy sayed but i have a bug to

it s when video file name is named with èéàç ... it bugs (can't open or save to .d2v

[Doom9]

I named a d2v file öäüéàèçê.d2v and it worked. Same with öäüéàè°°ç.d2v. However, I never quite understood the fixation of certain people of pushing the envelope in naming files in all kinds of weird ways.. computers do have character limitations.. what one program can handle, another can't and if you have complex integrated systems, you're going to cause chaos by using the whole character set. Just as an example, MS Project Server has a long list of unsupported special characters.. you may be able to use them in MS Project client, but if you add the server, you have other requirements (e.g. webservices need xml escaping, the SQL Server doesn't support certain things, the OLAP cube doesn't support certain things). Bottom line is: if you want it to work everywhere, stick to ASCII. Anything else, you will inevitable fall flat on your face sooner or later.

[Sharktooth]

ehrr... èéàç is ascii...

[Doom9]

not really.. it's extended ASCII.. standard ASCII only uses 7 bits and doesn't support any of the special character widely used in western languages.

[PhAtfiSh]

Build 0.2.3.2180 (updated everything)

The bitrate calcualtor does not calculate the overhead for audio streams in an AVI container (only one i tested, i got a 4mb oversized encode because of it). Unless i missed something... selecting different audio types in the drop-down menu has no effect on the bitrate.

The muxer is very buggy, it truncates my xvid/vbr mp3/avi mux by about 70mb leaving it unplayable.

Sorry if these have been mentioned before.

On another note, i like the work you guys are doing, but it seems to me some pretty major features for an encoding app are still very buggy (and have been for a while); id like to see the current features stable before anything else is added.

[Doom9]

The muxer is very buggy, it truncates my xvid/vbr mp3/avi mux by about 70mb leaving it unplayable.It might be divxmux.. we have no control over third party products. BAsically, if you run the commandline megui dumps in the log and it gives you the same results.. either the commandline is wrong (unlikely but okay) or it's divxmux.

and have been for a whileLike? I doubt you're creating AVC in MP4.. that is unofficially the thing megui does and it has been working for the better part of 1.5 years.

[PhAtfiSh]

Ok true, im not using it for AVC/MP4, i use it for XVID/AVI.

that is unofficially the thing megui does and it has been working for the better part of 1.5 years.

I still find bugs in the AviSynth script creator. On at least three occasions i have had it do wierd things with the cropping; the preview window shows it over cropped, but the actual file is under cropped.

It may have done something strange to the aspect as well on one occasion, i cant rember. I have a d2v that doesnt crop correctly right now. I guess logs wont be much help for debugging that? The bitrate calc has a problem in the latest build with calculating overheads for AVI. It just seems to me problems with the bitrate calc or basic avs generation shouldn't be around at this point.

Every now and then i have to load up gknot to make sure megui isnt lying to me :)

It might be divxmux..

Yes you are correct, divxmux screws up when run through the command line too. I guess ill go moan to someone else about that.

[CraigBjorn]

I've been attempting to use MeGUI 0.2.3.2180 to convert dvd .VOB files to X264 for use on an ipod. I been using the arstechnica (http://arstechnica.com/guides/tweaks/ipod-video.ars/6) tutorial to get the basic setup. However, after starting the encode, Microsoft (XP SP1) finds an error

==========
Error signature
EventType:clr20r3 P1:megui.exe P2: 0.2.3.2180 P3:44bc9a71
P4:system.windows.forms P5: 2.0.0.0 P6: 4333aefa P7: 1508
P8: 12f P9: system.argumentnullexception
==============================================

which forces MeGUI to quit and no error appears in the MeGUI log. From what little I can tell, the error occurs either during or after the use of DGIndex. I'm not sure if it's a problem with MeGUI or with the current setup. Any help would be great.

[Doom9]

I have a d2v that doesnt crop correctly right now. I guess logs wont be much help for debugging that?No.. we need a snippet from the source for that.. long enough so that you can use it to trigger the problem.

On at least three occasions i have had it do wierd things with the cropping; the preview window shows it over cropped, but the actual file is under cropped.Can you back this up with the sources? You know how it goes.. a bug is a bug if it can be reproduced, even if it's you have to go there to try it on a specific environment (I spent a day in the last 3 weeks trying to track down a weird issue in a software we sold to a client.. the first thing I asked was the scenario, followed by the time and then the trace file.. after that I was able to verify that the problem does indeed exist and begin trying to track down why it happens). A blanket statement "it didn't work on 3 occasions" doesn't help.. on the contrary, if you call something a bug, you better be able to back it up or it's just being mean (keep in mind, you didn't pay for megui).

he bitrate calc has a problem in the latest build It might not hurt giving the version number to be on the safe side.. I know I don't do it myself but it's good practice. Anyway, you said the latest version.. was it okay at some point? If so, which revision (we can go back through the revisions, find out what changed and that gives a good starting point as to what has been broken). I vaguely recall having a problem with the AVI Bitrate calculation at some point too.. so it might be this problem has never been properly noted and thus gone unfixed for quite a while. And the fact that most developers aren't using AVI, and most users neither, certainly doesn't help discovered if there are bugs in that department :(

I guess ill go moan to someone else about that.Please do. it's better if the actual users complain... if it doesn't help, you can give me a shout and if I can reproduce the problem I'll tell the DXN guys myself..

@CraigBjorn: Is this a crash message? It doesn't sound like the fatal error message and any catchable errors should be catched and shown in a message "A fatal error has ocurred and megui might not be able to continue"... also, you gave very little information on your setup (what you did from the start of megui.exe... ) and where exactly it happened.. you should also try the simplest scenario imaginable (if you have an avs file, load it, then press queue and start encoding).. and then gradually turn to more complex scenarios until you can put the finger on what exactly makes it crash.

[foxyshadis]

That's the event log error for an unhandled fatal exception. A screenshot of the stack trace message would be much more helpful. But also follow Doom9's suggestion.

[PhAtfiSh]

0.2.3.2180 is the build i just updated to, 0.2.3.2111 was the one i was using previously (bit of a big jump there sorry). The bitrate calc for avi worked fine in 2111 but in 2180 it has the problem with avi overheads.

I vaguely recall having a problem with the AVI Bitrate calculation

For the movie i have here Gknot calculates:

866 (kbps) with both interleaving and frame overheads (the value that will hit the 700mb target).
871 (kbps) with vbr mp3 interleaving overhead.
874 (kbps) with frame overhead.
880 (kbps) with no frame or interleaving overheads.

MeGUI calculates:

874 (kbps) whatever options i select.

Given the Gknot values (which should be trusted imo) MeGUI is calculating the frame overhead, but not any audio interleaving overhead.

The same appears true for AC3 audio as well, MeGUI calculates the frame overhead but not the interleaving overhead.


Can you back this up with the sources?

I deleted the d2v/vob that caused the cropping bug by mistake yesterday (doh!). Ill re-rip that movie when i have time and try and make a small sample that the bug can be recreated with.

[Sharktooth]

avi muxing is not working as expected so do not expect any updates to the bitrate calculator until we fix the muxer issues.

[~bT~]

avi muxing is not working as expected so do not expect any updates to the bitrate calculator until we fix the muxer issues.
I made a post here about this about 3 weeks ago...been a long time time but Im just using a workaround.

[PhAtfiSh]

do not expect any updates to the bitrate calculator until we fix the muxer issues

I would rather have a working bitrate calc than a muxer. Muxing in VdubMod is not really that much of a problem. But having my encodes come out the wrong size, and then having to use another program to calc the bitrate and put that into MeGUI is.

[Doom9]

@PhAtfiSh: most revisions don't concern the calculator.. I may have a look (I use megui as bitrate calc for everything) when I get back from my business trip.

[cyberbeat]

1) Actually, just pressing PREVIEW before clicking on AUTOCROP will cause it to crash.

I got around this by adding the following code:
In "private void previewButton_Click(object sender, System.EventArgs e)" around line 1000 in AviSynthWindow.cs before the line "player.disableIntroAndCredits();"
reader = player.Reader;

One thing I am not sure about is when you press the PREVIEW button after a CROP, it will show a cropped preview. If you AUTOCROP at this point, it will have new values based on the cropped preview instead of the original footage. (At least, I think that is what is going on.) Would it not be better to have AUTOCROP always use uncropped footage and only let the Mod16 items affect it?

2) AutoCrop seems to have an issue with one scenario. I use the "Non mod16 encoding" so there is no resizing or excess cropping. I then click on AUTOCROP to remove the borders. More often than not it will but "0" for the left border and "2" for the right border. This causes a problem with non Mod16 encoding because the width has to be a multiple of 4 or you get an error. I encode MP4 video with MP4 AAC audio into the MP4 container. I just change the right side to 0 most of the time.

I got around this by adding the following code: (was not sure if this would be appropriate or if it should be a part of VideoUtil.cs)
In "private void autoCropButton_Click(object sender, System.EventArgs e)" around line 1446 in AviSynthWindow.cs after the line "cropBottom.Value = final.bottom;"
if (Mod16Method == mod16Method.nonMod16)
{
while ((cropLeft.Value + cropRight.Value) % 4 > 0)
{
if (cropLeft.Value > cropRight.Value)
{
if (cropLeft.Value > 1)
{
cropLeft.Value = cropLeft.Value - 2;
}
else
{
cropLeft.Value = 0;
}
}
else
{
if (cropRight.Value > 1)
{
cropRight.Value = cropRight.Value - 2;
}
else
{
cropRight.Value = 0;
}
}
}


These issues still exist in build 2181... Bumping the message for feedback.

Thanks,
cyberbeat

[kurt]

although I unticked packed bitstream for xvid encoding, the resulting avi stream is packed (according to mpeg4modifier).

Looking at the command line shows, that -nopacked is missing.

[ToS_Maverick]

0.2.3.2155.
When I select a profile for x264 and hit config, it sometimes loads the wrong profile for editing, so I must manually select the profile again to edit it. Certainly not a fatal bug, but it can be annoying in a list of many profiles ;)
I've noticed this issue since .2153, maybe before.

this bug still happens in .2181, just for info ;)

[foxyshadis]

Thanks kurt, I fixed that, should be in next update.

ToS, can you do anything to reproduce it more reliably than "Sometimes"? Because it's never happened to me in a year.

[ToS_Maverick]

of course i can. i just thought it must be obvious, it happens all the time here!

normally i just use sharktooth's x264 presets in megui. recently i made 2 own presets, just small changes from "HQ-Slower".

1st preset is HQ-Slower-CRF, same as the original, just changed from bitrate mode to CRF.

2nd preset is HQ-Slower-SA, same as slower, set avclevel to 3 and had to uncheck p4x4.

now if i select HQ-Slower-SA and click on config, megui displays HQ-Slower-CRF. if i select ...-CRF it displays HQ-Slower and so on. it jumps to the next preset above the one i selected.

[check]

Just noticed: after booting up MeGUI where there are old completed jobs in the queue, the fps values for these jobs are correct to more than 2dp (to 15dp).

[foxyshadis]

Ah, if it happens every time then what may be the case if that what you think they are isn't what was actually saved in them. MeGUI's always had somewhat less than intuitive profile behavior, eventually I'll look at creating a better model, but here's how it works atm:

You select your profile and hit config. Make your changes, etc, notice that nothing's in the profile box at the bottom. Hit okay, the config is set but not saved to any profile.

Now, if you were to change the profile in that dropdown, say to PD-iPod, and you make a change, then hit okay. Now those changes are actually saved within the profile. Change the profile, hit config, and come back to iPod, it still has your changes.

With this in mind, what I suspect happened was: You created your profile, hit new to save it, and then made some more changes and hit okay, thus overwriting the profile. (Maybe it was at the time, maybe later.) Or something like that, but you should be able to remake and resave them, just being careful that you don't accidentally overwrite them.

Because it is so error-prone and unintuitive, I intend to come up with a better interaction model soon.

Bug report: Unchecking lossless in x264 panel doesn't re-enable bitrate. Oops. I'll get it if no one does before me.

[Sharktooth]

lossless thing fixed in 2183.

[ToS_Maverick]

foxyshadis, i know about the profile edit and save behaviour in megui.

to create my two custom profiles, i selected slower in the config window and clicked new.

the point is, after selecting a profile in the megui-main window and clicking config, megui displays the next profile above the current one. not only the settings of the above profile, it's also selected in the dropdown box!

[kurt]

thx for the latest patches, foxyshadis :)

but custom commandline option for xvid doesn't work properly, does it?
for example if I untick qpel and add -qpel second pass aborts. Same for -par 4... --> log displays all encraw options

btw: an option for autoshow commandline would be great (or maybe saving the status when closing megui)

Edit: tested a bit more and now it works, when putting a space character before the first command...
-qpel -par 4

[Sharktooth]

k... going to fix it right now... :)

EDIT: done (2184)

[kurt]

wow, that was fast - thx, sharktooth :)

[foxyshadis]

Oops, I remember making that mistake before and reminding myself to remember it (I keep thinking it's serialized instead of just written out for some silly reason). ^^; Thanks for fixing.

ToS, drat, my guess was wrong. So just selecting a profile and hitting config, the listed profile will differ? Hmm, what about on the main form, if you look at it while the config dialog is open? Has it changed there (so at least both are in sync with each other) or do they differ? If they're the same, can you do every action slowly and see if you can identify when it switches? And this isn't a beta version of .Net 2 I presume? Perhaps you could zip up all your profiles and settings and I'll see if I can reproduce it using them.

[ToS_Maverick]

after hitting config, the profile in the config window changes. the selected profile in the main window is still the same.

example:
mainwindow profile: HQ-Slower-SA
click on config
still -SA in main window but
in the config window: HQ-Slower-CRF

if you want to check out my megui, here's (http://www.infinitpower.com/files/x264.zip) the link.

[Rumbah]

I have just noticed a bug in the latest version.
I have a PAL mpeg2 video file. I used the option D2V Creator in MeGUI and selected the mpv file. It created the D2V file, but in the resulting D2V file it was set as a 23,.. -> 29,.. fps file although it is a normal 25 fps mpeg file. The result was that my final mp4 file had a display rate of 30 fps and that was too fast.

If I use dgindex manually, I get a correct D2V file and the resulting mp4 file is fine.

[sjchmura]

m2AudioAC3Source error on 5.1 AC3 files:

I see others have had this problem and the "fix" involves forcing directshow.

the proble: if I do that with Nero 7 filters or the new Ac3 I ONLY GET 2.0 sound. It is set in MEGUI to "keep original channels".

I check my AC3 streams and they ahve no errors. About 70% of Ac3 streams work FINE - the other 30% bomb with the error

[Doom9]

@Rumbah: what you report makes no sense to me.. megui does not touch the framerate unless dgindex reports a film percentage higher than your force film treshold.. then the output will be 23.976.. under no other circumstance will megui ever touch the framerate. Could you open your megui created d2v file in a text editor (like notepad) and past the last line of the file? Then, you also need the provide the full log of the whole process. I think the most productive way to get an improvement in this area would be to cut the AC3 streams properly in the area that cause the problem, then provide the stream for nic so that maybe he can do something about it.

@sjchmura: nic's ac3 audio source isn't as easy going on input as besweet.. it complains often and loudly, but this isn't megui's fault. The thing using DirectShow is that whatever is configured will be used.. so if you play the AC3 file in a DirectShow player, unless the output is 5.1, your megui output will not be 5.1 either.

[dngnta]

@Doom9 & Rumbah: I have encountered the same problem. It's caused by the recent (today's?) update to DGIndex. My video is 100% video, but DGIndex sets force film on it and sets the framerate to 24 fps. The resulting .d2v looks like this: (DGIndex 1.4.8)

Field_Operation=1
Frame_Rate=23976 (24000/1001)

...

FINISHED 100.00% VIDEO

I then replaced megui\tools\dgindex\dgindex.exe with the .backup file and re-did the d2v through MeGUI. (DGIndex 1.4.7)

Field_Operation=0
Frame_Rate=29970 (30000/1001)

...

FINISHED 0.00% FILM

This works correctly and as expected. All the other lines are identical between the two .d2v files. The command line is the same both times (-AIF=[F:\tmp\test.mpg] -OF=[F:\tmp\test] -exit -minimize -OM=2).

Is there any other information I could possibly supply that would lead to this bug being fixed? Although I guess this isn't MeGUI's bug..

[dngnta]

This, however, probably is MeGUI's bug :-)

I hit the AutoEncode button, selected File Size = 2 CD, checked Split Output and set it to 700. However, the resulting file got split into hundreds of pieces, each of them around 700 kB, not MB as one would expect based on the indication in the Automatic Encoding dialog.

(The command line MeGUI used had -splits 700 in it. In fact, the files are sized 700 000 bytes maximum, so the correct switch should have been -splits 734000 or thereabouts (700*1,024*1,024*1000))

Everything is updated to today's versions.

[foxyshadis]

You should just post the DGIndex bug in a new thread here:
http://forum.doom9.org/forumdisplay.php?f=5

Is the split acting on mp4 or mkv? In mkvmerge you have to specify units or it'll use bytes, so I guess mp4. Oh yeah, I see the command in mp4box now. Actually it's only 700*1024 though, or 716800. (Since kB is already assumed.)

[Doom9]

I'm afraid there have been commandline changes in mp4box and mkvmerge in the past and they were just picked up when something broke.. e.g. in mkvmerge, it appears --split is now to be used and the MB indicator has to be different as well.