MeGUI: bug reports and feature requests

[quantum5uicid3]

I just ran the updater to v1058, but the presets did not import. The window came up asking if I wanted to import the presets, but it was totally empty.
made a mistake with the zip file. fixed

[JoeH]

That's the way x264 applies the parameters:
--preset
--tune
user settings (will override preset and tune settings)
--profile overrides all settings

Thats the way MeGUI applies the settings if you change a value:
megui profile setting
changed user setting
if changed --preset overrides all settings
if changed --tune overrides all settings
if changed --profile overrides all settings
custom command line overrides all settings

That's not good at all, but if you understand how it works it is possible to create stable profiles.


OK. I suppose the best order, followin along with how X264 by default works, would be something like this, each overriding the previous when it applies:

x264 preset
x264 tune
megui profile setting - whenever it is not the "default" (that is, whenever it appears in the "command line" which appears inside the megui profile - that way the user can expect that the command line which appears in MeGUI will act just as it would if he were to type that command line in MSDOS)
custom command line

[JoeH]

made a mistake with the zip file. fixed

Confirmed. Works great. I deleted all other profiles and imported only these. Do we still need STx264? It might be helpful to clean up the profiles to just drop it now that we have the new ones.

[Triccotracco]

Update all to the last revisions, seems work good. A question about presets slide: why when i move from very slow to slower a --bframe 8 appear?

slide in "very slow" position:
program --preset veryslow --thread-input --output "output" "input"

now slide in "slower" position:
program --preset slower --thread-input --bframes 8 --output "output" "input"

:thanks:

[Zathor]

Update all to the last revisions, seems work good. A question about presets slide: why when i move from very slow to slower a --bframe 8 appear?

slide in "very slow" position:
program --preset veryslow --thread-input --output "output" "input"

now slide in "slower" position:
program --preset slower --thread-input --bframes 8 --output "output" "input"


Thanks, there is an error in applying the bframes in the preset slower. Will be fixed in the next update.

[TDC.net]

Hi Zathor,

thanks for reviving megui development! Really an impressive number of improvements in build 1058!

Just a small error:
When you move the megui folder to another path, all folders that are subfolders of megui are updated in the options automatically except:
-update path
-avisynth plugins path

Can't wait to test more improvements in megui thanks to your skills!

Regards,
Raist

[ircopdd]

DGSource("C:\CH010_0920_2033.dga", deinterlace=2, resize_w=1280, resize_h=720)


why use deinterlace=2
fps change to 59.94fps???
---[NoImage] avs [warning]: converting input clip to YV12
---[NoImage] avs [info]: 1280x720 @ 59.94 fps (3066 frames)

use deinterlace=1
fps Normal
fps=29.970

[Inspector.Gadget]

Because BOBBING ALWAYS DOUBLES THE FRAMERATE. That's not a MeGUI topic anyway, take it up in the existing DGNV tools thread.

[Triccotracco]

Another question about "preset setting" switch in "misc" tab of x264 configuration window: how does it work? Or better, what is the difference from "preset setting" switch and "Presets" slide on "main" tab.?

[amgeex]

Just wanted to say thanks for keeping this GUI alive, its my favorite so far and there isn't a replacement right now, so yeah, thanks a lot!!

[ACrowley]

Hello

I cant update :

Trying server: http://www.constructd.com/megui
Retrieving update file from server...
Error: Couldn't connect to server.
Error: Could not download XML file

EDIT:
Now it works...The Problem was my old megui folder from the old builds

Im glad to see megui workinf fine again :) it was my favourite gui.

Have you planned x264_x64 Support ?

[Zathor]

Have you planned x264_x64 Support ?

I already have a few features planed for the next milestone release. But of course there may be problems implementing them and therefore I will only comment on or publish an feature if it is proofed to be working (at least for me) or if I need additional input from the community (like below).


Just a small error:
When you move the megui folder to another path, all folders that are subfolders of megui are updated in the options automatically except:
-update path
-avisynth plugins path

Thanks for the feedback. I will change that behavior.
I would like to change it so that all of the file and path settings will be tied up so that the files have to be in the tools directory at the specified location. That's the way most of the other GUIs work and I think it's the best solution in order to keep it simple and with less problems (like the UAC problem when the files have to be copied in a special directory). What do you and all others think?

Another question about "preset setting" switch in "misc" tab of x264 configuration window: how does it work? Or better, what is the difference from "preset setting" switch and "Presets" slide on "main" tab.?
Both do more or less the same. If you move the slider the settings will be applied all over the tabs. The "preset setting" will write them back to the tabs in case you have changed a preset setting like the number of reference frames and do not want to move the slider.

[XhmikosR]

Zathor: Although I don't use MeGUI for the last one year or so, I'd like to thank you for trying to fix a great tool for a lot of users out there. One question: Can't you get SVN access? Maybe ask Kurtnoise or Doom9? It would be nice to have all of your changes in the trunk.
I patched the source with your patch, updated the AssemblyInfo for MediaInfoWrapper and meGUI and updated MediaInfo.dll to 0.7.25 and compiled a new installer for those who used the old one.
You can find it here (http://www.mediafire.com/?ty1mjgmgmum). (no changes have been made to the installer except just the version bump which means it still needs administrator privileges like the old one)

[ACrowley]

@Zathor

x264 cmd encoding Status window displays the current Bitrate (%,Frame,FPS,kbp/s,eta Time)
Megui doesnt show it. Its very important when you ask me .

Please, can you add this Info in the Megui Proccess/Status Window ?

[Zathor]

x264 cmd encoding Status window displays the current Bitrate (%,Frame,FPS,kbp/s,eta Time)
Megui doesnt show it. Its very important when you ask me .
Please, can you add this Info in the Megui Proccess/Status Window ?
Ok, I ask you: Why is it important to know? :-)
Sorry, but I cannot see an improvement if you know the current bitrate. What benefit do you have if you know it during the encoding process?

Can't you get SVN access? Maybe ask Kurtnoise or Doom9? It would be nice to have all of your changes in the trunk.

It took some days but :
kurtnoise13 added zathor to the meGUI project.
2009-12-14 13:31:53 CET by kurtnoise13

Thanks to Kurtnoise I am now able to commit my source code and have access to the official MeGUI update server. I need to change a few things before I am able to commit the source code and update the files on the server.

In the meantime I invite you all to test the current build and give me feedback about problems/bugs. Especially the upgrade path 1051 --> 1058 and 1057 (official) --> 1058 is important. I would like to commit a version which is as bug free as possible.

[detmek]

Hi. Just to say, thank you, Zathor, for fixing and continuing development of my (our) favourite GUI. I didn't test much 1058 but, so far, works good.
And, thanks to Kurtnoise and Sharktooth for previous development.

[TDC.net]

Thanks for the feedback. I will change that behavior.
I would like to change it so that all of the file and path settings will be tied up so that the files have to be in the tools directory at the specified location. That's the way most of the other GUIs work and I think it's the best solution in order to keep it simple and with less problems (like the UAC problem when the files have to be copied in a special directory). What do you and all others think?


Perfect idea! I vote for that! If you really want to customize something as a user, just copy the custom files there ;)

Ok, I ask you: Why is it important to know? :-)
Sorry, but I cannot see an improvement if you know the current bitrate. What benefit do you have if you know it during the encoding process?

I totally agree! current info such as estimated total size, remaining time and fps is enough.

R

[ACrowley]

[QUOTE=Zathor;1352803]Ok, I ask you: Why is it important to know? :-)
Sorry, but I cannot see an improvement if you know the current bitrate. What benefit do you have if you know it during the encoding process?
[/CODE]

Ofcourse i can use a Bitrateviewer after encoding

Usefull or not..i think megui could view all x264 Status informations, why not

[Kurtnoise]

Usefull or not..i think megui could view all x264 Status informations, why not
it's already in the log...

[nakTT]

it's already in the log...
Hi Kurt, glad to see you here.

[Zathor]

0.3.1.1058 dev
- [MeGUISettings] update_cache location and avisynth plugin location can not be changed anymore
- [x264Settings] changed the default *scratchpad* settings to x264 default (preset and some other settings have been wrong)
- [x264ConfigurationPanel] changed b-frames value in preset slower

Uploaded a new build to the first posting. It's a small step on the way to the stable release. Do not expect new features until the stable commit. Beside bug fixes I will only remove the possibility to change the program path of the auto downloaded tools.

[nakTT]

0.3.1.1058 dev
- [MeGUISettings] update_cache location and avisynth plugin location can not be changed anymore
- [x264Settings] changed the default *scratchpad* settings to x264 default (preset and some other settings have been wrong)
- [x264ConfigurationPanel] changed b-frames value in preset slower

Uploaded a new build to the first posting. It's a small step on the way to the stable release. Do not expect new features until the stable commit. Beside bug fixes I will only remove the possibility to change the program path of the auto downloaded tools.
Is the b-frames for preset slower has been changed from 8 to 3 (the way it was)? Thanks.

[Zathor]

Is the b-frames for preset slower has been changed from 8 to 3 (the way it was)? Thanks.
There has been an logical error preventing to update the value if the value has been different from 0. Do not ask... it has been fixed.

[nakTT]

There has been an logical error preventing to update the value if the value has been different from 0. Do not ask... it has been fixed.
Sorry. Thanks.

:thanks:

[MatLz]

Hi!
It seems AQ can't be disabled, even with the usage of the custom command line --aq-mode 0, mode 1 is used. Mode 2 seems to work.

[Zathor]

Hi!
It seems AQ can't be disabled, even with the usage of the custom command line --aq-mode 0, mode 1 is used. Mode 2 seems to work.

- [x264ConfigurationPanel] subme 10 instead of 9 will force trellis 2 and aq-mode > 0
- [x264ConfigurationPanel] removed dependency between mb-tree and aq-mode
- [x264Encoder] fixed aq-mode command line generation (aq-mode 0 has never been appended)
Update in the first post. There have been a few wrong settings regarding aq-mode...

Sorry. Thanks.
Why do you say "sorry"? I am very grateful for your problem reports. :thanks:

[MatLz]

Sorry I missed that...
:stupid:

[Zathor]

Sorry I missed that...
:stupid:
No, I have fixed it after your problem report! Thank you very much! :-)

[Theliel]

thank you Zathor for your work.

many ppl forget much times the work behind a proyect like MeGui. Of course, thank anyway (and always) to Kurtnoise and Sharktooth and many others.

[shon3i]

I am wery happy to see MeGUI alive ;) Zathor, thank you for hard work and of course all greetings to main developers (berrinam, Sharktooth, dimzon51, Kurtnoise13) for great application for years :)

@Zathor, i must you note that Blu-Ray profiles which came with MeGUI is out of spec.

Can i suggest you instead fixing those profiles, make one completly new option insade x264 settings which will correct settings if are out of spec from bd standard.

[Zathor]

@Zathor, i must you note that Blu-Ray profiles which came with MeGUI is out of spec.
In which way it is out of spec? At least the bluray 2-pass looks good. Btw you have to look in the command line below - the GUI values may change when using the preset slider but they will be overridden by the custom command line.

Can i suggest you instead fixing those profiles, make one completly new option insade x264 settings which will correct settings if are out of spec from bd standard.
Some kind of device preset is indeed required. At the moment you have to put the device settings in the custom command line.

[Carpo]

Zathor any chance you could look at getting CUVIDServer.exe to be found by megui, every time it comes up with the error it cant find it, even if you tell it where DGIndexNV.exe is, i am assuming (probably incorrectly) that megui assumes it to be in the same place.

Thanks :0)

[Zathor]

Zathor any chance you could look at getting CUVIDServer.exe to be found by megui, every time it comes up with the error it cant find it, even if you tell it where DGIndexNV.exe is, i am assuming (probably incorrectly) that megui assumes it to be in the same place.
As stated last weekend I will add support for the new DGIndexNV. As soon as I start to implement this all CUVIDServer.exe calls have to be renewed. Because of the big changes needed it will not be included in the next official and stable release.

Do you have a workaround like starting the CUVIDServer.exe yourself before MeGUI starts?

[shon3i]

Btw you have to look in the command line belowHah, i didn't look ;) sorry, it's fine. I thinked about some option which will prevent user from changing. For example if user set vbv-maxrate higher than 15000, automaticly to disable Max Keyint should be larger than blu-ray specs specified.

[Triccotracco]

Another note about presets slide cursor(this is my matter :D): when i move from ultrafast until slower "--aq-mode 0" (that is correct for ultrafast) remain.

cursor in ultrafast position:
program --preset ultrafast --thread-input --aq-mode 0 --output "output" "input"
cursor in slower position:
program --preset slower --thread-input --aq-mode 0 --output "output" "input"

[Carpo]

As stated last weekend I will add support for the new DGIndexNV. As soon as I start to implement this all CUVIDServer.exe calls have to be renewed. Because of the big changes needed it will not be included in the next official and stable release.

Do you have a workaround like starting the CUVIDServer.exe yourself before MeGUI starts?

thats what i have been doing, with 1051 its hit and miss - 1056 and above its pure miss, i can wait :)

[Zathor]

- [x264Encoder] fixed aq-mode in all presets
- [DialogManager] minor change to the CUVIDServer call
- [MeGUISettings] + [SettingsForm] all automatically installed tool paths cannot be changed anymore

thats what i have been doing, with 1051 its hit and miss - 1056 and above its pure miss, i can wait :)

Please try the new build. Link is in the first post. I have made only a very minor change but maybe together with the new path system it will work. Please try it with a clean installation - but expect the real fix later. Oh, by the way: Please specify in the settings the path to either the VC1 or MPG dgindex NV tool.

Another note about presets slide cursor(this is my matter :D): when i move from ultrafast until slower "--aq-mode 0" (that is correct for ultrafast) remain.
Thanks, it has also been fixed.

[Carpo]

Oh, by the way: Please specify in the settings the path to either the VC1 or MPG dgindex NV tool.

Thanks, it has also been fixed.

Thought DGIndexNV.exe did them all as its the new merged version of his tools?

Edit: went and got beta 11 still not working, i will do the 2 backups i have to do manually and sit and wait till you have time to sort out megui - its no biggy :)

[rack04]

- [MeGUISettings] + [SettingsForm] all automatically installed tool paths cannot be changed anymore

Would you consider changing this back to the way it was? I don't like having multiple copies of the same programs floating around. I would like to be able to specify paths to x264, dgindex, dgavcindex, mp4box, tsmuxer, mkvmerge, eac3to, dgdecode, and dgavcdecode. Thanks.

[Zathor]

Thought DGIndexNV.exe did them all as its the new merged version of his tools?

Edit: went and got beta 11 still not working, i will do the 2 backups i have to do manually and sit and wait till you have time to sort out megui - its no biggy :)
Yes, DGIndexNV is the "one for all" tool but it is not supported by MeGUI at the moment.

Would you consider changing this back to the way it was? I don't like having multiple copies of the same programs floating around. I would like to be able to specify paths to x264, dgindex, dgavcindex, mp4box, tsmuxer, mkvmerge, eac3to, dgdecode, and dgavcdecode. Thanks.
Today it is no problem at all to waste this little space - especially if you are encoding HD videos.
The more experienced user lost the ability to change the path. On the other hand the more inexperienced user lost the possibility to have problems due to the configurable path settings.
Every one of the other GUIs (at least all I know) has the tools in the program folders and the path is not changeable at all. But I would never do things only because all other do them. I have to be sure that this is the right thing. Therefore I would like to have additional feedback. To revert the changes is no problem at all and only a matter of minutes (thanks to source control)

[Aoshi101]

After installing one of the older builds of MeGUI like 1051 or 1056, you can take everything that was supplied in this new build by Zathor and copy it over into the MeGUI directory on your C drive. Say yes when it asks to copy over files currently there. Now when you try to use your taskbar shortcut or your start menu shortcut, it will work fine and you don't have to worry about reconfiguring paths and such. Very simple copy paste.

Im sure alot of you figured it out, this is for those who didn't realize it or haven't tried.

[stax76]

Yes, DGIndexNV is the "one for all" tool but it is not supported by MeGUI at the moment.

Is there any managed GUI where it works?

Would you consider changing this back to the way it was? I don't like having multiple copies of the same programs floating around. I would like to be able to specify paths to x264, dgindex, dgavcindex, mp4box, tsmuxer, mkvmerge, eac3to, dgdecode, and dgavcdecode. Thanks.

From developers view very very bad idea, using AviSynth plugin auto loading also very bad idea, download feature, very doubtful. I've been there and have done this and will never go back.

[nakTT]

Why do you say "sorry"? I am very grateful for your problem reports. :thanks:
I just thought I don't want you to get mad at me over my noob question. Glad to know that you are not easily mad. Not like some other guy.

:thanks:


P/S: I can't seems to get the latest update. Just now I tried to update and there is nothing new other than my current 1058. Please help.

[Guest]

Is there any managed GUI where it works? I've been asking myself that question also. Nvidia has no clue about the failures and neither do I. :(

[ACrowley]

it's already in the log...

ofcourse ....but i often take a look to the current Bitrate/Frames when i encode in CRF Mode.
And sometimes i can decide if i should take a lower/higher CRF Value. For example when the Bitrate is to high/low and the Output File becomes to big/small for my needs.

Thats why i think the x264 Status Information about the Bitrate usefull.

[BuckMaster]

Today NV update driver to GeForce/ION Driver Release 195.81 BETA...maybe have some bug fixes :D

[JoeH]

Every one of the other GUIs (at least all I know) has the tools in the program folders and the path is not changeable at all. But I would never do things only because all other do them. I have to be sure that this is the right thing. Therefore I would like to have additional feedback. To revert the changes is no problem at all and only a matter of minutes (thanks to source control)

My personal preference would be both to:
1. Do not allow the paths to be changed
2. Continue to offer the option to download a version which is complete, and has all the tools included.

[Adub]

Zathor
That small input bug still exists in 1058. It appears with any profile and slider position. Simply try and edit the crf value or psy-rd values by punching in the numbers on your keyboard and you will see what I am talking about. It's pretty annoying.

[Triccotracco]

another 4 "cosmetic" bugs: start from x264 defaults (verified with x264 --fullhelp) I move the preset slide and verified the parameter changes according x264 --fullhelp.

Preset Ultrafast:
cabac toggle should be disable (command line ok)

Preset Veryfast:
I8x8 should be enable with adaptive DCT that come with profile high (command line ok)

now the last two notes:
with "Defaul Settings" button on "Misc" tab --subme 6 appear, should be 7.

the right title of context help for "Weighted Prediction for P-Fr." is "P-frame Weighted Prediction"

hoping that my observations are ok, thank you again Zathor!

[Zathor]

Simply try and edit the crf value or psy-rd values by punching in the numbers on your keyboard
I reverted the event handler back to the old one. The problem with the old handler is that the value will be only processed if the control lost the focus or the up/down slider is used. Btw I changed ALL NumericUpDown events so that the user experience is the same for all controls.

hoping that my observations are ok, thank you again Zathor!

:thanks: It should be fixed now.

- [AvsReader] workaround for DGMultiSource added. The program will crash less frequently. Patch by neuron2
- [ProfileManager] save the profiles during closing of MeGUI even if the profile folder could not be deleted
- [UpdateWindow] update check is able to find missing files
- [x264ConfigurationPanel] changed a few preset/tuning settings, changed NumericUpDown event

- [AvsReader] workaround for DGMultiSource added. The program will crash less frequently. Patch by neuron2
With this fix the program did not crash for neuron2 (1024MB GPU). On my system (256 GPU) the crash appeared later... I am now able to enqueue the job, close MeGUI and start the job. Far away from perfect and therefore the CUVIDServer is recommended (no crash at all).