MeGUI Bug-Report Thread

[shon3i]

Cannot open d2v file in avisynth script creatorThe solution is: Copy DGDecode.dll from DGIndex directory to "C:\Program Files\AviSynth 2.5\plugins". I undestand why in settings->program paths->AviSynth Plugins newer used for plugins.

[Tima]

Ok, now it loads.. :)

But now there is NO script in Edit tab even after loading d2v and setting other options.
When I click on 'Preview' or 'Save' I get this:

---------------------------
AviSynth error
---------------------------
AviSynth script error:

The script's return was not a video clip.
---------------------------
ОК
---------------------------

[shon3i]

That is realy strange. I am using 2089 build and works fine.

[dimzon]

hmm anyone know what this means? I encoded the 5.1 fine but the stereo won't encode.
It means NicAc3Source can't decode your AC3 (maybe it's damaged)
Try to force directshow decoding (you must have ac3 splitter/decoder installed) for this file

[ChronoCross]

The solution is: Copy DGDecode.dll from DGIndex directory to "C:\Program Files\AviSynth 2.5\plugins". I undestand why in settings->program paths->AviSynth Plugins newer used for plugins.
it didn't use to have to work like that. in fact if you look at the script it makes it actually loads the DGdecode.dll that's in the location you specified for DGINDEX. Why would it do that if in the end you have to put it in the avisynth plugins dir for it work. seems kinda pointless.

It means NicAc3Source can't decode your AC3 (maybe it's damaged)
Try to force directshow decoding (you must have ac3 splitter/decoder installed) for this file

I figured as much. I'm actually doing this because of a thread I saw in another for doitfast for you and whatnot. I'll see if that works. thanks.

[Doom9]

it didn't use to have to work like that. Then you know more than I do. The script creator never loaded any plugins via loadplugin automatically.. I always relied on the avisynth plugins mechanism from the getgo. If it ever was different, then it would've been an error on the part of the programmer who changed that. gknot's loadplugin insanity may have been suitable at the time, but it's completely outdated now.
You don't even need dgdecode in your dgindex folder anymore.. I suppose it still gets added to the path, but in fact all d2v reading is now done via avisynth.. if you look at the d2vreader class.. it just forwards most of its calls to the avisynth class and the only logic still in the d2vreader deals with d2v script parsing

[ChronoCross]

Lets take a look at the screenshot below:

http://chronocrossdev.com/images/scriptc.png


you'll notice that it provides a LoadPlugin line which is then outputted to the avs that it actually makes. So basically what your saying is that it shouldn't be outputting that line? and that all calls are made from the avisynth plugins directory? Thanks

[ChronoCross]

now that I decided to play around with the avs creator a bit more I found a way to crash it hardcore.

load a .d2v do all the cropping and resizing. hit the analyse source button. Then before it's finished analysing save the .avs script. it'll save the script and then megui will just dissappear. the whole thing. no log output no error message, no crash report.

[dimzon]

LoadPlugin vs AviSynth plugins folder
there are very "fine" sideeffect involved by OS kernel...
there are base kernel function LoadLibrary for loading external Dll, AviSynth's "LoadPlugin" invokes it to load plugin Dll. But LoadLibrary can't load some Dll multiple time. And LoadLibrary uses filename only to determinate Dll uniqieness. So let's look @ sample.

Imaginate you have such script:

loadPlugin("c:\my\dgdecode.dll")
bla-bla-bla
bla-bla-bla


And you have dgdecode.dll in AviSynth plugins folder too.

So let's take close look @ script opening process:

AviSynth performs flder scan for it's plugin folder and load its to memory. After this step DGDecode.dll from plugins folder is already loaded to current process.
AviSynth performs loadPlugin("c:\my\dgdecode.dll"). But there already are dgdecode.dll attached to current process. In this case LoadLibrary doesn't perform loading but returns handle of already loaded Dll


this can produce a real mess when you have different versions of dgdecode.dll....

[ChronoCross]

yeah cept from what I can tell the Loadplugin thing does nothing in megui. If I don't have dgdecode in the plugins dir for avisynth the file won't load at all. so it doesn't make sense that it's there.

[shon3i]

@dimzon why settings->program paths->AviSynth Plugins newer used for plugins. same thing with decomb and dgindex

[Doom9]

settings->program paths->AviSynth PluginsThat's a pure information value.. I think I'll get rid of it come the next stable build. I almost never get tired of saying that I won't move away from using the avs plugin directory before my corpse is starting to rot.

[dimzon]

@dimzon why settings->program paths->AviSynth Plugins newer used for plugins. same thing with decomb and dgindex
It shows actual aviSynth plugin dir in registry. When you change it your resistry will be changed automatically. I prefer to keep this field for informative and utilitary reasons, bcz some software can change aviSynth plugin dir without your agreement and even aknowledjment

[shon3i]

Ok. But i change to GordianKnot directory where i store plugins and then megui can't use this plugins.

[dimzon]

Ok. But i change to GordianKnot directory where i store plugins and then megui can't use this plugins.
Maybe you must restart MeGUI

[shon3i]

Maybe you must restart MeGUI
I tryed but is same. decomb must be in "C:\Program Files\AviSynth 2.5\plugins".

[Doom9]

decomb must be in "C:\Program Files\AviSynth 2.5\plugins".So must every other plugin unless you manually add a loadplugin line to the avisynth script. And that is never going to change. AviSynth 2.5 even permits multiple versions of the same plugin in the plugins directory and offers a means to differentiate between them when you access plugin functions. The loadplugin plethora in gknot is really oudated and megui will never go down that road. To make you less confused, the avisynth plugins indicator will be gone in the next stable release.

[Sharktooth]

@berrinam:
this:In the Bitrate Calculator, editing the target filesize (in MBs) is refreshing with the wrong event
Description: If you delete everything in the textbox to type a new number, MeGUI flags this as zero immediately upon the keypress, and opens a popup saying the target is too small. This is annoying as you need to constantly press enter. It would be better to catch the focuschanged event (dunno what it's actually called) and the enter pressed event (likewise).
Status: Not yet solved.
got fixed as well in 2093

[berrinam]

Updated the first post.

[ChronoCross]

Jobs with errors are still flagged as 'done', instead of 'error'
Description: MeGUI 0.2.3.2066 flags jobs as done instead of error when there is an error. However, the job quere still stops.
Status: Not yet solved.

Is this only in relation to x264? I haven't seen it do it with any other codec or format.

[Sharktooth]

it could be

[berrinam]

It's my fault. At the time, it happened to me on everything, so I just assumed that everyone could reproduce it. As a result, I didn't file a proper bug-report and just posted it directly on that list. I'll do some testing later to see if I can reproduce it now, and if not, I'll remove it from the list.

[Raithmir]

I managed to get CVS figured out and download the source. Trying to debug the shutdown feature, it seemed to be hitting the shutdown function but not working. Would it perhaps be easier to use WMI to shutdown? Something like this? http://www.dotnet247.com/247reference/msgs/1/7455.aspx

[ChronoCross]

tired it. doesn't work.

[KiraDouji]

@Doom9 - here is a patch to fix the two bugs we discussed. Please review.
http://richardberg.net/bin/temp/filechecking-bugfixes.rar

How would one use this patch, exactly? :confused:

- Kira

[berrinam]

How would one use this patch, exactly? :confused:

- Kira
Here's a tip -- it wasn't addressed to you, and the bugs are no longer present. End result? You don't need to worry about it.

[KiraDouji]

Here's a tip -- it wasn't addressed to you, and the bugs are no longer present. End result? You don't need to worry about it.

But there's definately still a bug... :sly: MeGUI keeps reading my 24 FPS audio as 23.999999whatever and therefore throws my audio and video off sync. I apologize if I misread the information provided, as I am merely searching for a solution to this issue. If you have one, I'd be glad to hear it.

And before you ask, yes I have the most current version, and yes I KNOW that my audio is 24 FPS.

- Kira

[dimzon]

@KiraDouji
Read http://forum.doom9.org/showthread.php?t=105160 first and REPOST BUG REPORT as REQURED

[KiraDouji]

@dimzon *sigh* That's how I got to this thread in the first place. After reading this thread I thought there was a fix, but appearantly I need to REPOST BUG REPORT because it is REQUIRED. Okay. Got it. Sorry.

- Kira

[Doom9]

MeGUI keeps reading my 24 FPS audio Audio has no framerate............

[bob0r]

Sorry, but for the 3rd time i feel i have to mention this bug, as nobody has answered if this is a bug or not (or only cosmetic, like i8x8 will just be ignored)

Commandline not updated, or is this by new/old/new/old/new design?

2097 still exists:

x264 > config > Quantization > Macroblock Options:
When you select --8x8dct (Adaptive DCT) (after selecting high profile) the option I8x8 becomes available, when you select it, you get: --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct
Now when you unselect --8x8dct (Adaptive DCT), you get: --analyse p8x8,b8x8,i4x4,i8x8
i8x8 is still enabled in the commandline(wrong), but greyed out in the gui(correct).

Edit:
fixed

[Sharktooth]

moo... i fixed all that billions of years ago...
and it has been refactored another billions of times... and everytime there's a new bug.
i'll look at it tomorrow, however x264 ignores i8x8 if 8x8dct is not specified.

[berrinam]

I've fixed it in 0.2.3.2098. I thought I had last time, and I posted saying that I thought I had fixed all bugs. Since no-one replied, I assumed it was fine. Sorry I missed that again.

I don't know where the commandline isn't being updated.

[Sharktooth]

this: http://forum.doom9.org/showthread.php?p=792764#post792764
belongs to this thread.

[berrinam]

Fixed. Added to the list anyway.

[max-holz]

I have just tried Rev. 0.2.3.2102 and I notice this issue, when I'am trying to modify x264 Video Profile (I use Sharktooth's rev. 21) after clicking Ok button in x264 Encoder Configuration no video profile is selected in Video Profile combobox and my modications are not saved in the profile.

[Sharktooth]

confirmed

[Sharktooth]

another 2 bugs:

1-trellis doesnt get grayed out when cabac is disabled
2-cq and crf values are always reset to 26 when entering the x264 config dialog (even if they get saved into the profile)

Note: i fixed those bugs some ages ago and they keep returning...

[nexus]

I still get the turbo-exception with build 0.2.3.2102:

http://forum.doom9.org/showthread.php?p=793428#post793428

[bond]

found a bug in megui with faac encoding:

the faac encoder is set to output raw adts .aac files, tough megui forces the .mp4 extension on that files
obviously you cant rename .aac to .mp4

the faac encoder needs to be set to output a .mp4

[shon3i]

Maybe is not a bug but will be useful. When select M.E. Algorithm Daimond or Hexagon then M.E. Range to greyout.

[Sharktooth]

not a bug, you cant set ME range for diamond or hexagon.

[berrinam]

I still get the turbo-exception with build 0.2.3.2102:

http://forum.doom9.org/showthread.php?p=793428#post793428
I don't. I can't see your picture either, and you haven't said exactly how you created it, so I can't do anything until you do. Why don't you try reading the guidelines at the beginning of this thread?

[berrinam]

I have just tried Rev. 0.2.3.2102 and I notice this issue, when I'am trying to modify x264 Video Profile (I use Sharktooth's rev. 21) after clicking Ok button in x264 Encoder Configuration no video profile is selected in Video Profile combobox and my modications are not saved in the profile.
confirmed
I can't reproduce what you are saying. It works fine for me, and it doesn't forget any of my settings. The only unusual thing is that it has no profile selected when you open the config dialog again. However, I think this is actually Doom9's intent, to make it clearer when using settings not involved in profiles.

EDIT: I found out what you mean, and I still think this is intentional. You mean that you select your profile in the main window, then press config. Then you make your changes and then press ok. Did you realise that in the encoder config dialog, your profile isn't selected either? You see, there are two ways to contain settings. The first is through profiles and the second is through what MeGUI calls currentVideoCodecSettings. The second doesn't have a name, and just has whatever the last settings were. It doesn't need to be in a profile, and to make this clear, Doom9 (I think) made no profile selected when you opened the dialog, so it should be obvious that you weren't editing a profile.

[berrinam]

another 2 bugs:

1-trellis doesnt get grayed out when cabac is disabled
2-cq and crf values are always reset to 26 when entering the x264 config dialog (even if they get saved into the profile)

Note: i fixed those bugs some ages ago and they keep returning...
Both fixed in 0.2.3.2104.

[berrinam]

found a bug in megui with faac encoding:

the faac encoder is set to output raw adts .aac files, tough megui forces the .mp4 extension on that files
obviously you cant rename .aac to .mp4

the faac encoder needs to be set to output a .mp4
Added to the buglist.

[Doom9]

the way I read the faac manpage:
MP4 specific options:
-w Wrap AAC data in MP4 container. (default for *.mp4 and *.m4a)if your output extension is .mp4, then -w is implied and used automatically.

[max-holz]

I can't reproduce what you are saying. It works fine for me, and it doesn't forget any of my settings. The only unusual thing is that it has no profile selected when you open the config dialog again. However, I think this is actually Doom9's intent, to make it clearer when using settings not involved in profiles.

EDIT: I found out what you mean, and I still think this is intentional. You mean that you select your profile in the main window, then press config. Then you make your changes and then press ok. Did you realise that in the encoder config dialog, your profile isn't selected either? You see, there are two ways to contain settings. The first is through profiles and the second is through what MeGUI calls currentVideoCodecSettings. The second doesn't have a name, and just has whatever the last settings were. It doesn't need to be in a profile, and to make this clear, Doom9 (I think) made no profile selected when you opened the dialog, so it should be obvious that you weren't editing a profile.

Thanks Berrimam now I understand how to procede :D , still I don't understand the meaning of this change :confused:

Ciao

[Doom9]

Did I perhaps break something with profiles? Here's how it should work (and keep in mind.. in a refactoring phase, I can't fix bugs, verify bugs, do anything but make my mess work again.. the current change is extremely hard to achieve because of all the intelligence that's placed into the software.. suddenly, megui will be much smarter than the average user because it will understand what each encoder can do, and more importantly what each muxer can do, and it can interconnect muxers to achieve the output you want, even if it means going through multiple muxing steps.. many people would not be able to achieve that without considerable help).

Anyway: I had seen some complaints about profiles getting updated when they shouldn't, so I figured I'd make it GKnot style (a lot of people still clamor for GKnot this GKnot that where GKnot does it in a suboptimal way.. but then don't see where GKnot was copied 1:1 in other areas). In GKnot, a profile is updated when you change another one.. the same applies in MeGUI (in the codec configuration dialogs). When you select a profile in the main GUI, its settings are applied. If you press config now, the profile you had selected should be selected in the config dialog. If you change the codec before pressing config, the selected profile should be empty (because the codec doesn't correspond to the codec of the profile you have previously chosen). Then if you press config, of course no profile is selected either. Then if you select/create a profile in the config dialog and press OK, it should be selected in the main GUI. And if you select a job and press load, no profile should be selected (because jobs have settings and not profiles.. profiles are just settings with a name.. and since you can change settings independently of a job, it would lead to disaster if a job had a profile.. imagine creating a job, then deleting the profile before encoding, your encoding attempt will crash miserably, and imagine deleting a profile, then creating another one with the same name but for another codec.. now suddenly your desired muxed output cannot be achieved anymore because there is no muxpath for it). Not all of that is currently possible, parts of that I'm still working on and they will be available whenever (and it can take several more weeks until this happens) I commit my changes.

Perhaps it would be more logical to have a "update selected profile" button in each codec configuration dialog so you can control when a profile is updated? That way, it would be clear to everyone when a profile is updated, and you can control the point when you really want an update to happen, and can switch between profiles all you want safely because updates only happen when you press the update button. What do you think? So then basically you have the new button that creates a profile from the current settings shown on screen, and an update button to overwrite a profile's settings with the settings currently in screen.

[Sharktooth]

We already have a "Safe profile alteration" option.
I think it's better to restore the previous behavior.