MeGUI: bug reports and feature requests

[Zathor]

The correct place for bug reports and feature request is the Project page, but if you want to discuss them first you can do it here. However remember: without opening a bug report or feature request at the project page it is likely that we forgot about it. After all we are humans, aren't we?

Project page
http://sourceforge.net/projects/megui/

Bug reports (http://sourceforge.net/tracker/?group_id=156112&atid=798476)
Feature requests (http://sourceforge.net/tracker/?group_id=156112&atid=798479)
Support (http://forum.doom9.org/showthread.php?t=105920)

Update server for latest stable build
http://megui.org/auto/stable/

Update server for latest development build
http://megui.org/auto/

Recommended install instructions:
1. Install Avisynth 2.5.8 (if not already installed)
2. Install latest Matroska Splitter: http://haali.su/mkv
3. Install ffdshow: http://ffdshow-tryout.sourceforge.net/
4. Download the recent MeGUI build: http://sourceforge.net/projects/megui/
5. Extract the file (recommended to not extract it in the program files directory - use e.g. C:\Tools\MeGUI)
6. Run the program megui.exe and let it update all necessary files from the above mentioned server (stable is default).

This build does not require write access outside of the program directory. Therefore it is easy to use in a more restrictive environment. It is even possible to have several versions installed independently.

[Zathor]

- [ProgressWindow] added Windows 7 taskbar progress

Link removed. Please download above.

Please try this version on a OS before Windows 7 and without .NET 3.5 and post the result. The progress window "should" work without problems and of course without the taskbar progress but I can not test it myself.

[prOnorama]

@ Zathor: thanks a lot I will try it out. :)

PS: please do not use RapidShare alone for hosting, a lot of the time I get "There are no more download slots available for free users right now. " even if I want to download a small file. So I can't try it out now.

MediaFire is a good alternative.

[Zathor]

@ Zathor: thanks a lot I will try it out. :)

PS: please do not use RapidShare alone for hosting, a lot of the time I get "There are no more download slots available for free users right now. " even if I want to download a small file. So I can't try it out now.

MediaFire is a good alternative.

Thank your for the feedback. I have uploaded the file to mediafire.

[j8ee]

It crashes when I try to start it...

edit:

http://thumbnails23.imagebam.com/5877/c2278158764204.gif (http://www.imagebam.com/image/c2278158764204)

I think you get the idea without an error message translation.

box is XP SP3 32 bit, .net 1.1, 2.0 SP1, 3 SP2 and 3.5 SP1

[Puncakes]

You, my good sir, have my most heartfelt, and deepest thanks.

j8ee: It would be best if you provided some details as to the machine you're attempting to use it on(e.g OS, 32/64bit, .NET installed). Also, host your error image somewhere like http://imageshack.us/ and post the link to it, rather than waiting for a mod to approve it. I'm on Win7 32bit, with .NET 3.5 as well, so I can't provide much in the way of testing, but it certainly works great for me.

Once again, thank you very much, Zathor.

[ncatt]

Zathor Hi, thanks for this fixed version. Just a suggestion: do not put the files on rapidshare. In recent days I always see this message: "There are no more download slots available for free users right now. If you don't want to become a premium member, you might want to try again later." And if i try again later the same message pops up. It's annoying. Mediafire is much better. :thanks:

[Zathor]

It crashes when I try to start it...

I think you get the idea without an error message translation.

box is XP SP3 32 bit, .net 1.1, 2.0 SP1, 3 SP2 and 3.5 SP1

Thanks, it seems to be not working on non Windows 7 OS. Please use the build from the first post until I have a newer build. The version does not have any modifications in the progress window.

[j8ee]

Oh, now I saw that you wanted a test without .net 3.5. Anyway, 3.5 is an auto-update as far as I know, so most XP users have it.

[Zathor]

Oh, now I saw that you wanted a test without .net 3.5. Anyway, 3.5 is an auto-update as far as I know, so most XP users have it.

I added a few checks if the OS is Windows 7 (or above). Please try the new build again (it is in the first post).

Additionally I changed a small thing in profile handling
- [x264Config] the advanced settings will be applied to the command line independent of the advanced settings checkbox

[quantum5uicid3]

I didn't notice it at first, but it's still not saving the following settings after you create a new preset and close the x264 configuration dialog.
--ref
--bframes
--deblock
--no-cabac
--no-deblock
--ipratio
--pbratio
--deadzone-inter
--deadzone-intra
--qcomp
--aq-mode
--aq-strength
--psy-rd
--no-dct-decimate

and the --no-mbtree checkbox is not working properly

xp sp3 3.5 .net, someone confirm please.

[Zathor]

I didn't notice it at first, but it's still not saving the following settings after you create a new preset and close the x264 configuration dialog.
--ref
....

and the --no-mbtree checkbox is not working properly

xp sp3 3.5 .net, someone confirm please.
Did only a quick check with --ref. And yes, I can confirm the problem. On the other hand the --no-mbtree checkbox is working properly for me. In the fastest 3 presets --no-mbtree is always active and therefore it can not be activated (note to myself: disable the button if using these presets)

[quantum5uicid3]

yeah that was it with --no-mbtree, i just left the preset on fast and was going through all the settings one by one to see which saved and which didn't

[Zathor]

yeah that was it with --no-mbtree, i just left the preset on fast and was going through all the settings one by one to see which saved and which didn't

It should be fixed now and the build is in the first post. Please check if all settings can be loaded now.

[quantum5uicid3]

thanks, good work! the only thing left before testing more extensively, does "Credits Quantizer" still correspond to any x264 option (I don't see it doing anything and can find no reference in the command line options)? and the --rclookahead field still doesn't seem to change the commandline.

[stax76]

x264 GUIs involve complexity, some settings depend on other settings which again depend on other settings and sometimes it's very difficult to disable all controls accordingly. With such issues the first thing you would do is check the x264 docs on what other settings the setting depend taking also the settings of the preset and tuning into account. --rc-lookahead don't has dependencies and interactions documented so it's a simple bug.

[quantum5uicid3]

yeah i checked if it corresponded with mbtree or vbv settings, but it doesn't. "Credits Quantizer" apparently is only used if you "set the credit starting point in the preview window." overlooked it before, thanks.

[j8ee]

Using the build in the first post, I have the same crash as before. On my laptop I don't have the .net Swedish language packs installed, so the error message is in English this time.

XP SP3, .net 2.0 SP2, 3.0 SP2 and 3.5 SP1

http://thumbnails20.imagebam.com/5882/410d9158818147.gif (http://www.imagebam.com/image/410d9158818147)

[Zathor]

Using the build in the first post, I have the same crash as before. On my laptop I don't have the .net Swedish language packs installed, so the error message is in English this time.

XP SP3, .net 2.0 SP2, 3.0 SP2 and 3.5 SP1

(hopefully) finally fixed. Please try the new build. If not, please provide a few more details (which kind of job crashed, ...)

...and the --rclookahead field still doesn't seem to change the commandline.

I have changed the input handling in the new build. It did already changed the command line for me before, but maybe this change solves your problems.

[j8ee]

Seems to work now, I haven't been using it yet, but at least it starts! Nice work, many thanks!

edit: Hmm, disabling mb-tree isn't saved in a profile. It's checked when I load the profile again, and looking at the xml it says <NoMBTree>false</NoMBTree>.
edit 2: Correction - as far as I can see, none of my settings are saved at all. The changed settings are for ipod compliance: --profile baseline --level 3 --crf 20.0 --thread-input --ref 2 --vbv-bufsize 10000 --vbv-maxrate 10000 --no-mbtree --me umh --partitions p8x8,b8x8,i4x4 (which I think is the default, but I'm not quite sure)

edit 3: OK... it seems like loading the profile manually in the drop down menu in the config dialog brings up the correct commandline. I haven't made any test encodes to see if it's actually used yet, but I'll do that soon. Still, that the cabac checkbox does nothing makes me a little suspicious.

[Zathor]

edit: Hmm, disabling mb-tree isn't saved in a profile. It's checked when I load the profile again, and looking at the xml it says <NoMBTree>false</NoMBTree>.
edit 2: Correction - as far as I can see, none of my settings are saved at all. The changed settings are for ipod compliance: --profile baseline --level 3 --crf 20.0 --thread-input --ref 2 --vbv-bufsize 10000 --vbv-maxrate 10000 --no-mbtree --me umh --partitions p8x8,b8x8,i4x4 (which I think is the default, but I'm not quite sure)

edit 3: OK... it seems like loading the profile manually in the drop down menu in the config dialog brings up the correct commandline. I haven't made any test encodes to see if it's actually used yet, but I'll do that soon. Still, that the cabac checkbox does nothing makes me a little suspicious.

Both problems have been fixed (at least partially). Please try the new build and post again if any problem arise.
Cabac does nothing because in baseline profile it is already disabled. Please have a look at http://mewiki.project357.com/wiki/X264_Settings. If you find other settings which does not match with the GUI feel free to address them here.

[bluebebe]

thanks for the patch. everything is working fine now.

[showergel]

So as of today, it has been 42 days without a single code commit on MeGUI's Sourceforge.net portal. This sudden stop by all members of the team seemingly has the symptom of some argument/disagreement.

This morning I looked at x264.nl and MeGUI has been removed from their home page. Hmmmm...

Anyway, if this is really going to be the next evolution of MeGUI, then perhaps you can check the code out of MeGUI's SVN and start a new project page. You'll also get hosted there and won't have to worry about posting to rapidshare, etc.

There is precedent for this; ffdshow became ffdshow-tryouts on sourceforge.

[Cisco7]

I hope Kurtnoise and his co-workers will continue their incredible work on MeGUI or maybe qualified people could take care of the project and his evolution. Others GUIs are so annoying, smartless. MeGUI has been made by the users for the users. Please keep up your bloody good work, please keep us informed of your intention.

[Zathor]

MeGUI has so much potential to be the universal GUI for many aspects of multimedia encoding. The only purpose of my builds is to keep the project up and running (more or less) until the hard time is over and Kurtnoise or another one of the staff will continue their work. Maybe a few of my modifications are helpful for them.

I have no intention to take over this project. Beside a lack of time the most important thing is that I know that my programing skills are good enough for easy things in a supporting role - but way too weak for such a project in general.

I do not know why the project is on hold and I do not want to know it. There are surely reasons why this happened and why it has not been spread widely. My only hope is that the project has been suspended and not terminated.

Best wishes!

[mozzle]

You've done a good thing here, Zathor.

Thank you.

[Triccotracco]

Good work Zathor! Thank you very much!
:thanks:

[Zathor]

- [HDBDStreamExtractor] fixed a crash bug
- [HDBDStreamExtractor] input and output path will be preselected if the window stays open
- [BitrateCalculator] added experimental M2TS support

The M2TS support for the calculator is experimental and is based upon the "6 percent rule" (http://forum.doom9.org/showthread.php?p=1223719). Because this is only an educated guess I appreciate your feedback.

Additionally I have added a x264 BluRay profile as an example. The profile is based upon http://forum.doom9.org/showthread.php?t=149711 and http://mewiki.project357.com/wiki/X264_Settings. The profile has the goal to fulfill the bluray specs and be playable on most standalone players. A few remarks:
--nal-hrd requires a patched x264
--b-pyramid strict can not be aplied while mbtree is enabled but it should work sometime in the future. Please ignore the warning in the log.

The profile has been created as I understand the profile management should work. Feel free to start a discussion if you think that it should work the other way around. The custom command line "locks" the settings you want to force while you can change the quality/speed with the preset slider. The "advanced settings" tabs have been disabled in order to not confuse the more inexperienced users.

[JoeH]

I hope Kurtnoise and his co-workers will continue their incredible work on MeGUI or maybe qualified people could take care of the project and his evolution. Others GUIs are so annoying, smartless. MeGUI has been made by the users for the users. Please keep up your bloody good work, please keep us informed of your intention.

+1. Thanks to Kurtnoise, Sharktooth and team for the single most useful X264 tool around. We all look forward to seeing it continue to thrive!

[Warbucks81]

- [HDBDStreamExtractor] fixed a crash bug
- [HDBDStreamExtractor] input and output path will be preselected if the window stays open
- [BitrateCalculator] added experimental M2TS support

The M2TS support for the calculator is experimental and is based upon the "6 percent rule" (http://forum.doom9.org/showthread.php?p=1223719). Because this is only an educated guess I appreciate your feedback.

Additionally I have added a x264 BluRay profile as an example. The profile is based upon http://forum.doom9.org/showthread.php?t=149711 and http://mewiki.project357.com/wiki/X264_Settings. The profile has the goal to fulfill the bluray specs and be playable on most standalone players. A few remarks:
--nal-hrd requires a patched x264
--b-pyramid strict can not be aplied while mbtree is enabled but it should work sometime in the future. Please ignore the warning in the log.

The profile has been created as I understand the profile management should work. Feel free to start a discussion if you think that it should work the other way around. The custom command line "locks" the settings you want to force while you can change the quality/speed with the preset slider. The "advanced settings" tabs have been disabled in order to not confuse the more inexperienced users.

Thanks for the patched build. I assume this same profile would be good for creating MKV's for media player type devices.

[Zathor]

Thanks for the patched build. I assume this same profile would be good for creating MKV's for media player type devices.

Yes, every device that’s able to play BluRay compliant streams should be able to play back these files. At least it did work for me in the past for PS3, some standalone players and my streaming capable TV. Nevertheless there may be devices where you have to use a more restrictive profile (e.g. limit vbv bitrate). And you should not crop the files because some devices have problems if its is not 1920x1080 or 1280x720.

[j8ee]

Profiles are not deleted, and --ref 2 is not saved for me in a profile, it goes back to default 3 (it says 2 in the xml though). edit: After the fourth restart and manual deletion of some profiles --ref 2 is loaded in the profile.

[Zathor]

Profiles are not deleted, and --ref 2 is not saved for me in a profile, it goes back to default 3 (it says 2 in the xml though). edit: After the fourth restart and manual deletion of some profiles --ref 2 is loaded in the profile.

I can reproduce both problems. The deletion is fixed but I will upload a new build only after I have found the second problem.

[Zathor]

Profiles are not deleted, and --ref 2 is not saved for me in a profile, it goes back to default 3 (it says 2 in the xml though). edit: After the fourth restart and manual deletion of some profiles --ref 2 is loaded in the profile.

Both problems have been addressed in the build below.

Because of the greater changes regarding the file handling I do not want to change the link in the first post at the moment.

Link removed. Please have a look at the first posting.

- [MeGUISettings] change the default auto update server list to development
- [MeGUISettings] the update_cache location has been changed to a sub dir of the program dir
- [MeGUISettings] the avisynth plugin location has been changed to a sub dir of the program\tools dir
- [AviSynthWindow] + [AvisynthWrapper] LoadPlugin will be called for every DLL in the megui avisynth plugin dir
- [x264Config] changed the order the settings will be applied initially

This build does not require anymore write access outside of the program directory. Therefore it should be now much easier to use it in a more restrictive environment. It is even possible to have several versions installed independently.

Because I do not know if this is the way to go I would like to have feedback. The next step would be to disable the manual selection of the update_cache, avisynth plugin dir and maybe all other tools which will be installed automatically.

By the way: it is now possible - and I recommend it - to extract the zip file in an empty directory. It will be updated automatically through the development update server. Afterwards you have to update a few files manually (e.g. x264, mkvtools, eac3to, ...).

[SacredCultivator]

Thanks for this patched build, my question is in regard to the update server... Even under Development, which server would you be using?

[kool]

Thank you Zathor for this great work,

A question, I'm on Win 7 32 Bit OS and don't have meGUI and Avisynth install yet, now when I want to install meGUI, which version you recommend Win 7?

Thanks in advance.

[Zathor]

Thanks for this patched build, my question is in regard to the update server... Even under Development, which server would you be using?

I have not changed the servers in any way and I use at the moment the first one. But both servers seems to have identical files. Nevertheless you have to update a few files yourself (most important x264.exe and so on).

A question, I'm on Win 7 32 Bit OS and don't have meGUI and Avisynth install yet, now when I want to install meGUI, which version you recommend Win 7?

Avisynth 2.5.8 and the MeGUI build posted above (http://forum.doom9.org/showthread.php?p=1350501#post1350501)

[JoeH]

Avisynth 2.5.8 and the MeGUI build posted above (http://forum.doom9.org/showthread.php?p=1350501#post1350501)

I just installed this - it works GREAT! Thanks!

Here are the installation instructions I followed. As I had a few difficulties getting it installed, and finally found a safe and sure method, I thought I'd post it here:
1. Install the standard version 1056 from SourceForge
2. Update all parts using the "Stable" servers except the 1056 core
3. Change update server to development. Update all parts again except the 1056 core (if you do this without doing step 2 first you will get an error).
4. Copy the files that Zathor has prepared and select replace all.
When you open up MeGUI you will have a fully functional 1057 install, with full support for the new X264 features! Fantastic!

Zathor - thanks for your hard work. Here is a small feature request. I always ouput MKV files, but MeGUI always defaults to MP4 on the main screen. It would be great if MeGUI would save the last selected format, or had an option to set the default.

[szabi]

Also many :thanks: for it.

[nakTT]

Zathor - thanks for your hard work. Here is a small feature request. I always ouput MKV files, but MeGUI always defaults to MP4 on the main screen. It would be great if MeGUI would save the last selected format, or had an option to set the default.
You can set MKV as default by going to:

Options>Settings>Extra Config>Configure Auto Encode Default>

And choose the container that you like.

[Zathor]

Here are the installation instructions I followed. As I had a few difficulties getting it installed, and finally found a safe and sure method, I thought I'd post it here:
1. Install the standard version 1056 from SourceForge
2. Update all parts using the "Stable" servers except the 1056 core
3. Change update server to development. Update all parts again except the 1056 core (if you do this without doing step 2 first you will get an error).
4. Copy the files that Zathor has prepared and select replace all.
When you open up MeGUI you will have a fully functional 1057 install, with full support for the new X264 features! Fantastic!


Thanks for your reply.

With the newest build it is even easier to install:
1. Install Avisynth 2.5.8 (if not already installed)
2. Extract my build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually (x264.exe, ...)

[nakTT]

Thanks for your reply.

With the newest build it is even easier to install:
1. Install Avisynth 2.5.8 (if not already installed)
2. Extract my build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually (x264.exe, ...)
May I know which one U mean by "newest build"? Is it the one at the 1st post or the one at the 2nd page?

:thanks:

[forum king]

thanks mate

i have used the latest development build of urs ..
but tell me when i usesd to use 1051 with unrestricted 2 pass profile the settings were that of SLOWER
in mean like this :
program --profile high --pass 2 --bitrate 1000 --stats ".stats" --ref 5 --b-adapt 2 --b-pyramid --direct auto --deblock -1:-1 --trellis 2 --partitions all --me umh --thread-input --output "output" "input"

but in this one ( the new patched 1057 build the settings in that same profile are FAST..
program --profile high --preset fast --pass 2 --bitrate 1000 --stats ".stats" --thread-input --deblock -1:-1 --no-dct-decimate --output "output" "input"


what should be done ( does it mean that in the new megui build and x264 build SLOWER stuff is more faster or i need to drag the slider to slower to get the same settings.. and quality as that of unrestricted 2 pass

[Triccotracco]

May I know which one U mean by "newest build"? Is it the one at the 1st post or the one at the 2nd page?

:thanks:

The one in the first page, is true that at 2nd page there is a newer version but with a lot of changes, if I understand well.

Also for me patched 1057 version works fine & faster (used with x264 rev.1360 Jeeb's build)

Thank you again!

[forum king]

The one in the first page, is true that at 2nd page there is a newer version but with a lot of changes, if I understand well.

its very clearly mentioned on page 1



Stable build
http://www.mediafire.com/download.php?hj23mmmlmux

Development build with the additional changes below
http://www.mediafire.com/download.php?mfwnemetzt4



i have used the developmemnt build and its working great...

[nakTT]

The one in the first page, is true that at 2nd page there is a newer version but with a lot of changes, if I understand well.

Also for me patched 1057 version works fine & faster (used with x264 rev.1360 Jeeb's build)

Thank you again!
I see. I have just downloaded the unpatched one.

I'm interested to know about the "faster" bit for the patched 1057. Hope you can share your experience in a little bit detail.

:thanks:

[quantum5uicid3]

better solution...

[forum king]

well guys :( i am giving up
looks like i cant use the latest megui builds and the benefits of x264.
i have done everything as was said here and at the troubleshooting thread..
but it just wont work out..
i used the latest build by Zathor ( the 2nd one ) and installed it in a separate folder..
used unrestricted 2 pass HQ with SLower settings
it will do the first pass and give a STANDARD ERROR STREAM error upon second always..
sometimes the same error on first pass as well..


can someone please please please guide me how should i go about it all.. i have been trying to do this from last 3 days in TOTALO vain.

it looks i ll have to go back to 1051 :(

[quantum5uicid3]

stop trying to use the old presets. theyre no longer applicable

[forum king]

stop trying to use the old presets. theyre no longer applicable

o damn !!!
then which one is equivalent to unrestricted 2 pass now ..
i need something equivalent to that with no blurred edges and no pixelations at all.
thanks

[quantum5uicid3]

your gonna have to create your own presets, because nobody has taken time to do so yet. putting the preset slider on "slower", change the mode to automated twopass, uncheck the turbo, and entering the bitrate will be pretty damn close to what you were doing before

do what i said in my post above, so you can get all the old junk out of the way. you'll have a fresh new megui with no presets, then use this information to create your own presets based on your needs.

http://mewiki.project357.com/wiki/X264_Settings

you don't need to understand all of it, the default values and the presets built into x264 is all you need to be aware of

here's the settings you need if you want compatibility with a certain device
http://forum.doom9.org/showthread.php?t=149711

[forum king]

your gonna have to create your own presets, because nobody has taken time to do so yet. putting the preset slider on "slower", change the mode to automated twopass, uncheck the turbo, and entering the bitrate will be pretty damn close to what you were doing before

do what i said in my post above, so you can get all the old junk out of the way. you'll have a fresh new megui with no presets, then use this information to create your own presets based on your needs.

http://mewiki.project357.com/wiki/X264_Settings

ok as you say dear Sir !!! :)
but if i am right turbo used to be on in the past ,
BTW i am kinna noob in all this , setting it up would be so damn diff for me..
cant i just set it up as it was earlier in the unresticted 2 pass .. i have screenshotts of the 1051 version presets settings,


EDIT also , u said first to install 1056 then ur build ..
do we have to update 1056 first and then install ur build or how ?

also the 1309 x264 is there in ur update should i also replace this with 1360 from x264.nl

please forgive me noobiness , but my head is now aching with all this :P
regards
Glenn

[quantum5uicid3]

turbo turns the options way down for the first pass. what i'm telling you is that the defaults in conjunction with presets built into x264 really replace the need for sharktooth's presets. setting up x264 is nowhere near as complicated as it was before.

do you even need to hit a specific file size?

[kool]

a very 1th error I get under Win 7, I have installed as Zathor says

With the newest build it is even easier to install:
1. Install Avisynth 2.5.8 (if not already installed)
2. Extract my build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually (x264.exe, ...)

Error 1: happen when I select all profile and hit on import.

http://i49.tinypic.com/3160nev.png

Error 2: same as error 1

http://i46.tinypic.com/vsm683.png

Error 3 & 4 at the same time when I want to close meGUI.

http://i46.tinypic.com/nlyjcy.png

http://i49.tinypic.com/20az5g8.png

[forum king]

turbo turns the options way down for the first pass. what i'm telling you is that the defaults in conjunction with presets built into x264 really replace the need for sharktooth's presets. setting up x264 is nowhere near as complicated as it was before.

do you even need to hit a specific file size?yes
actually i am trying to make some dvds and and some HD content to a lower size like around bitrate of 600 to 700..

[quantum5uicid3]

ok as you say dear Sir !!! :)
but if i am right turbo used to be on in the past ,
BTW i am kinna noob in all this , setting it up would be so damn diff for me..
cant i just set it up as it was earlier in the unresticted 2 pass .. i have screenshotts of the 1051 version presets settings,


EDIT also , u said first to install 1056 then ur build ..
do we have to update 1056 first and then install ur build or how ?

also the 1309 x264 is there in ur update should i also replace this with 1360 from x264.nl

please forgive me noobiness , but my head is now aching with all this :P
regards
Glenn

no

1. uninstall and remove any traces of megui
2. install 1056, but dont even run it (this is just to provide the uninstaller and shortcuts, im lazy)
3. download and install the package of 1057 i put together ( it is fully up to date so no need to copy x264)

[forum king]

no

1. uninstall and remove any traces of megui
2. install 1056, but dont even run it (this is just to provide the uninstaller and shortcuts, im lazy)
3. download and install the package of 1057 i put together ( it is fully up to date so no need to copy x264)
yupp i have done it like that..
now the issue is how to make a profile which can rip on the same grounds as the unrestrcited 2pass was doing earlier in earlier builds.

[quantum5uicid3]

like i said before, putting the preset slider on "slower", change the mode to automated twopass, uncheck the turbo, and entering the bitrate will be pretty damn close to what you were doing before. leave turbo checked if you'd like but if your encoding down below 1000kbps, your gonna need to squeeze as much as you can out of it

[quantum5uicid3]

kool, i had problems with the audio presets as well. thats why i made that package. ru using 32 or 64bit windows 7?

[forum king]

Thanks Q :)
i donno anything about the options and yes i generally encode below 700 bits almost always :P so if u say it shouls be unticked then it ll be unticked dear Sir :)
what about deblocking strength coz i found thats thew only thing that has changed in this..
in earlier presets it used to be -1:-1 but tyhe default in that lone preset now is 0:0 should i change that..

if u can suggest anything which will be beneficial for ripping on low bit rate and getting good quality then please :)

regards

Glenn

[quantum5uicid3]

the defaults are all very well rounded at this point. i don't think i would worry about changing anything if i were you. if you would like to tweak, this really explains everything you need to know.
http://mewiki.project357.com/wiki/X264_Settings

I would consider playing with crf, if you don't need to hit an exact file size. it sounds more like you just wanna keep the bitrates pretty low. The problem with using the exact same bitrate for every source is that some are going to be more complex than others. I would consider experimenting with crf values between 25-30(im just guessing,higher crf=lower bitrate), so just keep raising your crf until the video doesn't look good enough to you anymore and then stick with the highest acceptable value.

[forum king]

the defaults are all very well rounded at this point. i don't think i would worry about changing anything if i were you. if you would like to tweak, this really explains everything you need to know.
http://mewiki.project357.com/wiki/X264_Settings

I would consider playing with crf, if you don't need to hit an exact file size. it sounds more like you just wanna keep the bitrates pretty low. The problem with using the exact same bitrate for every source is that some are going to be more complex than others. I would consider experimenting with crf values between 25-30(im just guessing,higher crf=lower bitrate), so just keep raising your crf until the video doesn't look good enough to you anymore and then stick with the highest acceptable value.

yes you are right ,
now i am getting why same bitrate doesnt give better quality with diff sources.
about deblocking well i guess -1:-1 gives ok results as it has been like that on all SLOWER profiles till date..
abiut the size well i try to make em small with bit rates in the range of 500 on an av for a dvd and for HD i try like 600 to 700.
but yeah my friends always ask me for a smaller size possible LOL

also Turbo is by default on in automated 2pass , you cant unchk it i have just noticed.

[nakTT]

In order to keep the MeGUI project running I have fixed a few of the problems with the latest version. Most of them are related to the recent changes in the x264 command line syntax and the not updated config gui in MeGUI.

Hopefully Kurtnoise/Sharktooth/... will continue their work on this great program. Kudos to them!

0.3.1.1057 patched build
- [x264Config] add support for weighted P prediction. Requires x264 revision 1327 or higher.
- [x264Config] fix issues with weighted B prediction
- [x264Config] fix an issue where custom profile settings may be lost
- [x264Config] very minor cosmetic changes
- removed the default UAC elevation prompt. Instead it will only be elevated if the app dir or avisynth plugin dir is not writeable
- [Util] + [FileUtil] incompatible xml files (e.g. profiles) will be moved to a backup dir
- fixed the problem of the incompatible x264 profiles. As a result the old B-Pyramid setting will be disabled
- [OSInfo] fixed a problem with the .NET detection
- [MuxStreamControl] preselect language if the filename contains the language name
- [x264Config] fixed a few input validate problems
- [x264Config] the advanced settings will be applied to the command line independent of the advanced settings checkbox
- [x264Config] a few profile settings could not be loaded
- [x264Config] extended input handling
- updatecopier.exe will be called elevated
- [x264Config] disable cabac and mbtree checkbox if setting disabled in profile or preset
- [x264Config] custom command line settings will replace settings in generated command line
- [HDBDStreamExtractor] fixed a crash bug
- [HDBDStreamExtractor] input and output path will be preselected if the window stays open
- [BitrateCalculator] added experimental M2TS support

Patch code is included, full source code can be requested if necessary. I do not know the GPL in every detail. If this is not sufficient please drop me a line and I will upload the full source files.

I did not change the version number for obvious reasons.

Feel free to address other/new problems, but I can not promise that I am able to solve them.

Stable build
http://www.mediafire.com/download.php?hj23mmmlmux


Hi Zathor,

First of all I want to thank you for continuing the MeGUI development.

I'm now using Stable Build version of your MeGUI. The first problem that I instantly notice is that when I select "Automated 2pass" in the x264 setting, the checkbox for "Turbo" seems to be checked by default and can't be unchecked. Please advice.

:thanks:

[quantum5uicid3]

as a workaround, just create the 1st and 2nd pass separately

[nakTT]

Thanks for the suggestion but I guess I would rather wait for the fix.

:thanks:

[rack04]

In the Blu-ray profile the default for partitions shouldn't be --partitions all. Also, --profile high is default. In the rate control tab the values for vbv buffer and vbv max bitrate are not passed to command line.

[quantum5uicid3]

In the Blu-ray profile the default for partitions shouldn't be --partitions all. Also, --profile high is default. In the rate control tab the values for vbv buffer and vbv max bitrate are not passed to command line.

are you sure --partitions all isn't supported by the bluray profile?

the other two problems u mentioned are fixed in the development build

[stax76]

--partitions all must be supported since RipBot264 uses it for it's Bluray profile.

[quantum5uicid3]

the reason why it looks like you can't change the vbv options is he set it up to where anything you specify in custom commandline options overides any attempted change in the gui. so the bluray compliancy settings are essentially locked on the profile he created.

[rack04]

are you sure --partitions all isn't supported by the bluray profile?

the other two problems u mentioned are fixed in the development build

I never said it wasn't supported. I just said that when you select default it retains --partitions all. I would rather the preset dictate when --partitions all is used.

EDIT: Actually I read my post again and can see how you made that assumption.

[quantum5uicid3]

same thing as vbv, --partitions all is forced in the custom command line.

and --profile high for that matter

[Frosty5689]

I noticed how megui passes a parameter to neroencaac.exe that creates a fake chapters in the mp4/m4a container. If this could be fixed so it doesn't create fake chapters,it'd help muxing mp4 and uploading to youtube without using mp4box as a cli.

[szabi]

I use this collection to keep compatibility with different devices. click (http://spreadsheets.google.com/pub?key=tYGTjNd0dG6P_A9z-YkFzFg&output=html).

[Zathor]

Waaah, so much postings :cool:

May I know which one U mean by "newest build"? Is it the one at the 1st post or the one at the 2nd page?
I recommend the "development build" but because of the rather big changes compared to the "stable" build there may arise problems. Up to now I do not know about problems.

thanks mate
i have used the latest development build of urs ..
but tell me when i usesd to use 1051 with unrestricted 2 pass profile the settings were that of SLOWER
in mean like this :
program --profile high --pass 2 --bitrate 1000 --stats ".stats" --ref 5 --b-adapt 2 --b-pyramid --direct auto --deblock -1:-1 --trellis 2 --partitions all --me umh --thread-input --output "output" "input"

but in this one ( the new patched 1057 build the settings in that same profile are FAST..
program --profile high --preset fast --pass 2 --bitrate 1000 --stats ".stats" --thread-input --deblock -1:-1 --no-dct-decimate --output "output" "input"

what should be done ( does it mean that in the new megui build and x264 build SLOWER stuff is more faster or i need to drag the slider to slower to get the same settings.. and quality as that of unrestricted 2 pass
Sorry, I did not use 1051 for a very long time. But as i read the changelog correctly the presets have been introduced in 1053 and are in x264 since 1206 (or so). Therefore you will get a different command line with the both MeGUI versions. The default preset setting is medium and therefore the command line created by 1051 will be slower compared to the one from 1057 patched. Additionally "--trellis 2 --partitions all --me umh" affect also speed/quality. If you want to have a high quality profile just use 1057 patched and move the slider to the right (placebo has the best quality / worst speed)

I made a simple installer to hopefully make things easier for people.
Thank you very much. May I request to add the newer eac3to? :)

i used the latest build by Zathor ( the 2nd one ) and installed it in a separate folder..
used unrestricted 2 pass HQ with SLower settings
it will do the first pass and give a STANDARD ERROR STREAM error upon second always..
sometimes the same error on first pass as well..

Please send me the error stream text (per PM for example). I can only fix it if I can reproduce it or I am able to make a educated guess.

a very 1th error I get under Win 7, I have installed as Zathor says

Error 1: happen when I select all profile and hit on import.

Error 2: same as error 1

Error 3 & 4 at the same time when I want to close meGUI.

Thanks for the report. Will try to reproduce (and fix) it later.

I'm now using Stable Build version of your MeGUI. The first problem that I instantly notice is that when I select "Automated 2pass" in the x264 setting, the checkbox for "Turbo" seems to be checked by default and can't be unchecked. Please advice.
I have to check this later, too. At the moment I do not know at which event/setting it should be activated or disabled.

I never said it wasn't supported. I just said that when you select default it retains --partitions all. I would rather the preset dictate when --partitions all is used.
I followed this thread and link in the first post. It looks like --partitions all is required or at least recommended for the BluRay profile. http://forum.doom9.org/showthread.php?t=149711

Additionally I have added a x264 BluRay profile as an example. The profile is based upon http://forum.doom9.org/showthread.php?t=149711 and http://mewiki.project357.com/wiki/X264_Settings. The profile has the goal to fulfill the bluray specs and be playable on most standalone players. A few remarks:
--nal-hrd requires a patched x264
--b-pyramid strict can not be aplied while mbtree is enabled but it should work sometime in the future. Please ignore the warning in the log.

The profile has been created as I understand the profile management should work. Feel free to start a discussion if you think that it should work the other way around. The custom command line "locks" the settings you want to force while you can change the quality/speed with the preset slider. The "advanced settings" tabs have been disabled in order to not confuse the more inexperienced users.

[JoeH]

You can set MKV as default by going to:

Options>Settings>Extra Config>Configure Auto Encode Default>

And choose the container that you like.

Thanks - I wasn't aware of that and I'll keep it in mind. However, that works for autoencode and is helpful, but it still doesn't change the default on the main screen, which is useful when you are putting multiple items into the Queue. It would still be helpful to be able to set the default (or just have it remember last selected, either way) on the main screen.

[forum king]

Dear Zathor and Quantum i have a suggestion :

you guys are so good at it and now as the thread is getting so many replies , why dont you guys gradually take over and develop megui builds which are compatible as the big guys are busy, i mean something like a full fledged patch over the latest build which takes care of the major issues.

I can tell you for sure that more than 50% of megui users are suffering since the updates have stopped and since the messups have started..

it took me whole 3 days to figure it out and i am a member since 1 year ..

guys please consider this , i am asking on behalf of all the affected folks.

regards

Glenn :)

i am still testing the second patch of urs dear zathor which quantum has made into a consolidated exe. will revert ....

[bluebebe]

why are the main developers of megui gone?

[Triccotracco]

a very 1th error I get under Win 7, I have installed as Zathor says

Error 1: happen when I select all profile and hit on import.

Error 2: same as error 1

following Zathor's instructions:

1. Install Avisynth 2.5.8 (if not already installed)
2. Extract the build to a new/empty directory
3. Run the program and let it update all necessary files from the development server.
4. Update some files manually if needed (x264.exe, ...)

also for me during first execution of Megui's update
I solve this issue restart Megui again forcing the update of "STAudio" restart again Megui and finally update Tx264 & TXviD :confused::confused: .... yes I know a little bit confused procedure but works!

[kool]

kool, i had problems with the audio presets as well. thats why i made that package. ru using 32 or 64bit windows 7?

32 Bit, and other thing when I checked avisynth plugin directory it was empty, expect 3 avisynth plugin.

[Zathor]

also for me during first execution of Megui's update
I solve this issue restart Megui again forcing the update of "STAudio" restart again Megui and finally update Tx264 & TXviD :confused::confused: .... yes I know a little bit confused procedure but works!
Problem found and fixed (in the next upload). These two files are simply not at the http://megui.org/auto/ location. I have removed this mirror until the update server is updated. Is someone able to provide a new update server with the latest packages?

[Zathor]

32 Bit, and other thing when I checked avisynth plugin directory it was empty, expect 3 avisynth plugin.
Which one? The one from avisynth or megui\tools\avisynth_plugins?

a very 1th error I get under Win 7, I have installed as Zathor says

Error 1: happen when I select all profile and hit on import.

Error 2: same as error 1

Error 3 & 4 at the same time when I want to close meGUI.

1 + 2) fixed (forgot to put the MessageBoxExLib.dll in the zip file...)
3 + 4) because of 1+2 the file handle could not be closed and therefore it can not be deleted/written during MeGUI closing ==> fixed

I will upload the new build soon.

[stax76]

why are the main developers of megui gone?

They didn't made a statement and only few things are known like sharktooth's health condition. Kurtnoise made a statement a while back saying something like like pausing computing generally but never made it true, maybe he made it now true but in this case he would have made another statement probably, I guess he isn't sure atm., he is still reading the forum.

Kurtnoise stopped after the last release which caused a lot problems for many users. I don't know exactly of what nature these problems were but it seemed the way some users reacted might have played a role, users with little support and understanding. If that's true it would be sad for supportive users like Inspector.Gadget. A way to deal with it could be to ignore unhelpful feedback and only support helpful feedback instead.

[Zathor]

Here is a small feature request. I always ouput MKV files, but MeGUI always defaults to MP4 on the main screen. It would be great if MeGUI would save the last selected format, or had an option to set the default.

It will now save the last used format.

The first problem that I instantly notice is that when I select "Automated 2pass" in the x264 setting, the checkbox for "Turbo" seems to be checked by default and can't be unchecked. :

Fixed.

New build has been uploaded:

- [MeGUISettings] removed the http://megui.org/auto/ update server
- [VideoEncodingComponent] + [MeGUISettings] added file format saving
- [x264ConfigurationPanel] Turbo mode can be changed in automated 2 or 3 pass

Because I did not receive any negative feedback regarding the development build I have deleted the "stable" build.

[Zathor]

I noticed how megui passes a parameter to neroencaac.exe that creates a fake chapters in the mp4/m4a container. If this could be fixed so it doesn't create fake chapters,it'd help muxing mp4 and uploading to youtube without using mp4box as a cli.

Can you please describe the problem in more detail? I do not use neroencaac.exe and a more detailed explanation (like the wrong parameter) should make it easier for me to fix the problem.

[prOnorama]

- [VideoEncodingComponent] + [MeGUISettings] added file format saving

Great, this works now it remembers your last setting for file format :)

Every setting I tried works from the main x264 configuration GUI except I'm still having a problem setting a value for rc-lookahead (doesn't show up in command line at all)

[rack04]

Can you update meGUI to support the new combined DGIndexNV? The way it is set up now you have to specify a path to DGAVCIndex, DGVC1Index, and DGMPGIndex. Now there is only DGIndexNV.

[nakTT]

New build has been uploaded

Because I did not receive any negative feedback regarding the development build I have deleted the "stable" build.
Anyone know what is the safest way to put the new build on top of my current build ("stable" build)?


:thanks:

[nakTT]

They didn't made a statement and only few things are known like sharktooth's health condition. Kurtnoise made a statement a while back saying something like like pausing computing generally but never made it true, maybe he made it now true but in this case he would have made another statement probably, I guess he isn't sure atm., he is still reading the forum.

Kurtnoise stopped after the last release which caused a lot problems for many users. I don't know exactly of what nature these problems were but it seemed the way some users reacted might have played a role, users with little support and understanding. If that's true it would be sad for supportive users like Inspector.Gadget. A way to deal with it could be to ignore unhelpful feedback and only support helpful feedback instead.
Oh! Sad to hear that. What about him? Anyway, I hope he will get better soon.


:thanks:

[Zathor]

Every setting I tried works from the main x264 configuration GUI except I'm still having a problem setting a value for rc-lookahead (doesn't show up in command line at all)
As soon as I change the value for "Nb. of Frames for Lockahead" the change is shown in the command line. Therefore I can not reproduce your problem. Can you explain the problem in more detail?

Can you update meGUI to support the new combined DGIndexNV? The way it is set up now you have to specify a path to DGAVCIndex, DGVC1Index, and DGMPGIndex. Now there is only DGIndexNV.
The main problem is that I do not have a license for the DGDecNV tool. If the commands have not changed between the old 3 tools version and now it should be possible. I cannot promise that I am able to change it.

Anyone know what is the safest way to put the new build on top of my current build ("stable" build)?
Create a backup of your MeGUI folder (in case something goes wrong) and copy the new files into the original directory.

[Triccotracco]

Can you please describe the problem in more detail? I do not use neroencaac.exe and a more detailed explanation (like the wrong parameter) should make it easier for me to fix the problem.

The same for me, not a big problem in my workflow. BTW when for example I load the .mp4 audio file in a gui like mkvmerge i see two, let me say, parts: the correct aac audio track & also this fake chapter. Not a big problem because with mkvmerge yuo can disable the fake chapter & then muxing mormally. For sure some mounths ago this strange stuff doesn't heppend.

Thankyou guys for all!

[quantum5uicid3]

i also confirm the --rc-lookahead issue still exists here on xp sp3 .net 3.5. what information do you need?



...reworking....

[Zathor]

i also confirm the --rc-lookahead issue still exists here on xp sp3 .net 3.5. what information do you need?
Which value do you would like to set and so on. At the moment I can confirm that a value of 40 will never be displayed regardless of the preset level. This is wrong and will be fixed. All other values should be shown in the command line (if it is not the default value of the preset). Please enter for example 41 and it should be visible.

[quantum5uicid3]

no it doesn't matter what it's set to, ive tried a wide variety of values

[Zathor]

no it doesn't matter what it's set to, ive tried a wide variety of values
Strange, can you send me please the profile with the problem?

[nakTT]

- [MeGUISettings] removed the http://megui.org/auto/ update server
- [VideoEncodingComponent] + [MeGUISettings] added file format saving
- [x264ConfigurationPanel] Turbo mode can be changed in automated 2 or 3 pass

Because I did not receive any negative feedback regarding the development build I have deleted the "stable" build.
Can you do this for audio file format as well?

:thanks:

[Zathor]

Can you do this for audio file format as well?

:thanks:
Give somebody an inch, and he will take a mile :p

[JoeH]

It will now save the last used format.

Thanks so much! :thanks::thanks::thanks:

[JoeH]

i made a couple more packages. to maybe make things easier. (full installer. creates shortcuts and uninstaller)
Lite (just megui, no tools) (http://www.constructd.com/megui/megui1057_zathorpatched_lite.exe)
Full (all tools updated beyond current update server) (http://www.constructd.com/megui/megui1057_zathorpatched.exe)


Thanks. It works great - I love the idea of having all the updated tools included.

When I installed it, the tools "oggenc2", "STX264", and "TXviD" all still asked to update. I updated oggenc2, but as I imagine the profiles you included are probably more updated than the ones included in STX264 and TXvid I downloaded them (to get rid of the "update" question) but did not install any of the profiles. I don't know if it is possible to avoid those tools not appeariing as updated, but I thought I'd mention it in case.

[kool]

Which one? The one from avisynth or megui\tools\avisynth_plugins?


Avisynth.


I will upload the new build soon.

Did you updated yet?

[nakTT]

Give somebody an inch, and he will take a mile :p
:D silly me.

[Zathor]

Avisynth.
With the newer builds the plugins will not be copied to the avisynth plugin dir. Instead they will be copied to tools\avisynth_plugins in order to use different versions without problems.

Did you updated yet?
Yes, it has been updated yesterday.

[hajj_3]

great work, hope you can add x264 v1369 soon, current version available in the updates list in megui is v1309.

Anyone know what happened to the megui developers? hope they didn't have a car crash or anything.

[prOnorama]

i also confirm the --rc-lookahead issue still exists here on xp sp3 .net 3.5. what information do you need?



i made a couple more packages. to maybe make things easier. (full installer. creates shortcuts and uninstaller)


Full (all tools updated beyond current update server) (http://www.constructd.com/megui/megui1057_zathorpatched.exe)

-it does not check if previous version is installed yet, so please uninstall any old version first.
-new uninstaller completely wipes megui directory, i think this was previous behavior.

- Uninstaller does not remove Start Menu and Quick start links.

- When installed no x264 *scratchpad* profile is loaded

- (I think this is a general flaw) the x264 Bluray_example profile "cheats" by having values in the Custom Command Line which should be set by the main patched GUI, just --nal-hrd --aud should be needed.

http://thumbnails23.imagebam.com/5925/1cc6f859241981.gif (http://www.imagebam.com/image/1cc6f859241981)

[quantum5uicid3]

- Uninstaller does not remove Start Menu and Quick start links.

what OS? I'm not great with NSIS, but I'll have more time to learn when finals are over. :)

anybody wanna help?

http://www.constructd.com/megui/megui_nsis.zip

[nakTT]

Hi Zathor,

I would be great if you could update MeGUI to accommodate this change of x264. Link below:

http://repo.or.cz/w/x264.git/commit/de5beaec2078967d08da8ae2483c9f982b0ab07e

:thanks:

[prOnorama]

what OS? I'm not great with NSIS, but I'll have more time to learn when finals are over. :)

anybody wanna help?

http://www.constructd.com/megui/megui_nsis.zip

WinXP SP3

[kool]

With the newer builds the plugins will not be copied to the avisynth plugin dir. Instead they will be copied to tools\avisynth_plugins in order to use different versions without problems.


Yes, it has been updated yesterday.

Thanks, it works now.

* If you upload a newer version in post 1, should we also replace our meGUI folder or we get every change by auto update?

* Do we need to change anything in existing x264 presets, or just leave it to default and encode? "I mean best quality"

[Triccotracco]

I see. I have just downloaded the unpatched one.

I'm interested to know about the "faster" bit for the patched 1057. Hope you can share your experience in a little bit detail.

:thanks:

Fine is for this megui patched build & faster is for these latest x264 releases compared old one. My experience is limited because i'm using now the presets with very very little adjustments such as crf value, my target is to watch movies on mediaplayer like for example WDTV and presets now, but also Sharktooth profiles in the past works 100% for me.:)

[quantum5uicid3]

Hi Zathor,

I would be great if you could update MeGUI to accommodate this change of x264. Link below:

http://repo.or.cz/w/x264.git/commit/de5beaec2078967d08da8ae2483c9f982b0ab07e

:thanks:

he didn't set it up to where they disable each other within the gui since x264 did it automatically. so its already supported, just copy new x264 in and change b-pyramid to normal.

[Zathor]

Uploaded a new build. Today there are only two very small changes - more to come in the next days.

- [MeGUISettings] changed the development server to http://www.constructd.com/megui
- [x264Encoder] changed the --rc-lookahead command line creation

The mirror is provided by quantum5uicid3. Thank you very much!

[Zathor]

Thanks, it works now.
* If you upload a newer version in post 1, should we also replace our meGUI folder or we get every change by auto update?
With the new mirror provided by quantum5uicid3 it will be possible to use once again auto update. Please change your development path to http://www.constructd.com/megui. Starting with the next build it will be uploaded there.

* Do we need to change anything in existing x264 presets, or just leave it to default and encode? "I mean best quality"
It depends on how old your profiles are, which settings you changed and on your target device. I can not answer this question in general.

(I think this is a general flaw) the x264 Bluray_example profile "cheats" by having values in the Custom Command Line which should be set by the main patched GUI, just --nal-hrd --aud should be needed.

As said earlier before. With this profile I want to start a discussion about how the profile management system should work. At the moment the only way to lock or force settings is to write it in the custom command line. With the preset slider you are then able to change the speed/quality without loosing your important parameters.

[kool]

It depends on how old your profiles are, which settings you changed and on your target device. I can not answer this question in general.


I don't have any profile, I just downloaded your build, do I need to make any profile?

[Zathor]

You need to know the limitations of your target device(s) and have to change the settings accordingly. If you have only one "rule set" you will need only one profile.

[kool]

The error still exists after trying both new versions and + new problem I don't get Xvid profiles and x264 by update.

http://i50.tinypic.com/2dazyb4.png

http://i48.tinypic.com/2mnopc6.png

For the screen shots 2, I think it happen with each profile in encoder settings.

I don't know why it happen :confused: , Or it is problem with Win 7.
Can't get megui to work :(

[Forteen88]

I don't know why it happen :confused: , Or it is problem with Win 7.
Can't get megui to work :(Try running MeGUI as administrator, by right-clicking on the icon and select "Run as administrator".

[kool]

Run as administrator solve the problem, but do I need to do this all the time? because after I select run as administrator things work fine, but when I load megui normally I get the error back.

* The simpleresize which come with megui update, why it doesn't work under avisynth 2.5.8? when I tried, got error simpleresize is not avisynth 2.5 plugin.

[wlee15]

Run as administrator solve the problem, but do I need to do this all the time? because after I select run as administrator things work fine, but when I load megui normally I get the error back.

* The simpleresize which come with megui update, why it doesn't work under avisynth 2.5.8? when I tried, got error simpleresize is not avisynth 2.5 plugin.

Right-click the megui shortcut, select properties, select the compatibility tab, check the box beside "Run this program as administrator".

[kool]

OK, the error issue as been solved by right click on "meGUI > Properties > Compatibility > Tick on Run meGUI as administrator" Hope this is the right solution.

But

* I don't get x264 profiles and Xvid by update
* simpleresize doesn't work under avisynth 2.5.8
* meGUI icon doesn't show up in Win 7 taskbar.

http://i48.tinypic.com/302yy5s.png

[Adub]

I have mirrored the current version on the first post here:
www.mirror.adubvideo.net/megui.zip

In addition, I can provide you with an ftp account on my server (unlimited bandwidth) if you would like. Just let me know if you are interested. It takes me two seconds to setup.

[quantum5uicid3]

you should be able to get xvid profiles now

there are no x264 profiles, someone needs to make them.

simpleresize was out of date, did a clean installation and updated. issue appears resolved

you're on your own with the taskbar

[nakTT]

he didn't set it up to where they disable each other within the gui since x264 did it automatically. so its already supported, just copy new x264 in and change b-pyramid to normal.
Thank you for the info. Glad to know that. Will give it a try ASAP.

:thanks:

Fine is for this megui patched build & faster is for these latest x264 releases compared old one. My experience is limited because i'm using now the presets with very very little adjustments such as crf value, my target is to watch movies on mediaplayer like for example WDTV and presets now, but also Sharktooth profiles in the past works 100% for me.:)
Thanks for sharing info.

:thanks:

[Aoshi101]

Problem: It keeps erroring out when I try to encode. It doesn't give any error message at all. In the worker it starts the encode but not even a second later, encode stops and worker status changes to say "error". Any way to find out the error or any solution on why this problem would occur?

How to duplicate this problem: Well there's no sure way to duplicate it unless if you're running default settings on everything. I just used the basic blu ray profile that came with this developmental build provided at the beginning of this thread. I changed nothing, tried encoding in mp4 x264.

Now I'm not encode savvy but I'm willing to learn. Could it be that blu-ray type settings cannot be encoded in an mp4 container? Any other info you guys need, just ask ill post as quickly as possible. I tried several things including changing the profile, trying a different container, tried changing resolution from 1080p down to 720p, etc etc. Can't figure it out for the life of me. Ideas?

System Specs:

Windows 7 64 bit
Quad Core 2 Q6600
4 gig 1066 ram

P.S. I lurk doom9 alot for encode information, first time i had any real errors with MeGUI that wasn't already solved. I appreciate your efforts Zathor!

[Zathor]

Do you have an entry in the log (in the file after closing megui or located at the log tab in MeGUI)? There should/could be a more specific error message.

[Zathor]

Run as administrator solve the problem, but do I need to do this all the time? because after I select run as administrator things work fine, but when I load megui normally I get the error back.

During startup of MeGUI it will be detected if you have write access in the MeGUI dir. If not the program will be restarted as administartor automatically. In your case it seems to be that you have write access to the MeGUI dir and no access to the allprofiles\x264 dir. Can you please check this (create a file in both directories without UAC and post the results)

* meGUI icon doesn't show up in Win 7 taskbar.
Sorry, I can see the icon in Win7. Do you get the megui.exe icon in the explorer?

[Aoshi101]

Do you have an entry in the log (in the file after closing megui or located at the log tab in MeGUI)? There should/could be a more specific error message.

--[NoImage] Standard error stream: C:\Program Files (x86)\megui\tools\x264\x264.exe: unrecognised option `--nal-hrd'

Thats the error then. Pulled it from the log, didn't even notice the log tab before (fyi me = not very observant ahaha).

[Zathor]

Thats the error then. Pulled it from the log, didn't even notice the log tab before (fyi me = not very observant ahaha).
You need to use a patched x264.exe which supports this feature.

[Aoshi101]

I thought the build you supplied was already patched for it? Everything I use currently is from the zip provided at the beginning of this thread, unless if I have to manually patch x264 exe?

[Zathor]

I thought the build you supplied was already patched for it? Everything I use currently is from the zip provided at the beginning of this thread, unless if I have to manually patch x264 exe?

The update server has recently changed. The new mirror is provided by quantum5uicid3 and I do not know at the moment if the x264 (build 1360 I think) is a patched one. I can check this not earlier than in ~12 hours. Which version of x264 and which mirror do you use?

[Aoshi101]

I use the constructd.com/megui/ address for patches and its currently set up to the 1369 techouse's vanilla build. I've seen the words "Jeebs patched" back in older versions of x264, so my guess is you can tell if its patched if it has the word "patched" in the name, or is that just for naming convention sakes.

Should I fall back to 1360?

[nakTT]

Uploaded a new build. Today there are only two very small changes - more to come in the next days.

- [MeGUISettings] changed the development server to http://www.constructd.com/megui
- [x264Encoder] changed the --rc-lookahead command line creation

The mirror is provided by quantum5uicid3. Thank you very much!
Glad to hear that we already have a new update server. Thanks to you and quantum5uicid3.


:thanks:

[Lugia25000]

http://www.constructd.com/megui

The new xvid encraw from alexins has many bugs. Can anyone change the encraw with the old encraw from -> http://megui.org/auto/stable/xvid_encraw-2009-05-30.zip ?
Old encraw needed aviwriter.dll.

Old xvidcore.dll and new xvidcore.dll work very fine with the old encraw.

@Zathor, big thx for the development.

My english is not so good, i hope everyone understand me.

[Zathor]

I use the constructd.com/megui/ address for patches and its currently set up to the 1369 techouse's vanilla build. I've seen the words "Jeebs patched" back in older versions of MeGUI, so my guess is you can tell if its patched if it has the word "patched" in the name, or is that just for naming convention sakes.

I have no access to the file at the moment but "vanilla" is most likely an unpatched version. And if you used this version and got the error it is clearly unpatched.

JEEBs builds can be found here: http://x264.fushizen.eu/
Direct link to Jeebs build with hrd:
http://x264.fushizen.eu/files/1369_hrd/x264.exe

More patches here: http://forum.doom9.org/showthread.php?t=130364

[Aoshi101]

Thanks so much for explaining it and helping me Zathor. I look foward to more possible updates to this build and hopefully if Sharktooth or Kurtnoise or any of the other MeGUI coders come back, they apply your fixes to their official build. Kudos to you bro.

[quantum5uicid3]

reverted back to old encraw as requested

updated to techhouse 1369 patched v2 for nal-hrd

EDIT: reverted back to unpatched 1369, im getting application errors with patched versions...

[kool]

You should be able to get Xvid profiles now

simpleresize was out of date, did a clean installation and updated. issue appears resolved


It works now thanks.

There are no x264 profiles, someone needs to make them.

Hope some one make them soon, because I don't know how to make them :p

During startup of MeGUI it will be detected if you have write access in the MeGUI dir. If not the program will be restarted as administartor automatically. In your case it seems to be that you have write access to the MeGUI dir and no access to the allprofiles\x264 dir. Can you please check this (create a file in both directories without UAC and post the results)


Hope I get you right by "with out UAC" I untick the option run meGUI as administrator in meGUI properties and tried to open meGUI and the result is as follow

http://i46.tinypic.com/35jxi8h.png

http://i48.tinypic.com/34t5qut.png

Sorry, I can see the icon in Win7. Do you get the megui.exe icon in the explorer?

Yes I do get the icon in explorer.

in 1th time when i install meGUI i do get both icon in explorer & taskbar, but after I restart megui I don't get meGUI icon in taskbar but in explorer it remain as normal.

[JoeH]

As said earlier before. With this profile I want to start a discussion about how the profile management system should work. At the moment the only way to lock or force settings is to write it in the custom command line. With the preset slider you are then able to change the speed/quality without loosing your important parameters.

After running loads (i.e. about 50) of tests quality / speed tests with the new X264, I wholly agree with you, Zathor. I think that the new profiles should NOT set the options which are set by the new "Speed" and "Tune" options in X264, and should only set options which are ignored by those but somehow necessary / helpful for a certain type of encode.

That way users can easily modify the settings based on how much time /quality they want / need, but also be assured of compatibility with the different devices or uses MeGUI offers.

[Zathor]

I have mirrored the current version on the first post here:
www.mirror.adubvideo.net/megui.zip

In addition, I can provide you with an ftp account on my server (unlimited bandwidth) if you would like. Just let me know if you are interested. It takes me two seconds to setup.

Thank you very much for your offer. Because quantum5uicid3 already provided a mirror we do not need an additional mirror at the moment. I will keep your offer in mind and would like to come back to you later if necessary.

[livetolove92]

No more x264 default setting =((
Hix, I may try to be adapt in using command line.

[JoeH]

After running loads (i.e. about 50) of tests quality / speed tests with the new X264, I wholly agree with you, Zathor. I think that the new profiles should NOT set the options which are set by the new "Speed" and "Tune" options in X264, and should only set options which are ignored by those but somehow necessary / helpful for a certain type of encode.

That way users can easily modify the settings based on how much time /quality they want / need, but also be assured of compatibility with the different devices or uses MeGUI offers.

I have thought this through a little more, and here is how I would propose the MeGUI "presets" work from here on out:
1. On the main screen, add a drop down menu for the "Speed" and the "Tune" options in X264. So, instead of just selecting the "preset", you would select the "preset", the "speed" and the "tune". In the case of "speed" and "tune", the first option in the dropdown would be to default to whatever is set in the "preset" you choose.
2. But, if you select, for example, "Animation" in the "Tune" dropdown, that would override whatever option is set in the preset for "Tune". The same for "Speed".
3. The included presets, then, would serve mainly to provide different "types" of encodings, such as for Blu-ray standalone, for IPod, DXVA compatible, etc.
4. There would NOT, however be duplicates for whether you want it to go fast or slow, high quality or low quality. All that can be decided at the time of encode using the two drop downs on the main menu.
5. The end result would be far fewer presets, easier to maintain, with much greater flexibility for the end user regarding speed/quality and tuning.

What do you think?

[Triccotracco]

Little vsfilter problem with autoupdate from:

http://www.constructd.com/megui

http://img709.imageshack.us/img709/8669/meguiupdateerror.jpg (http://img709.imageshack.us/i/meguiupdateerror.jpg/)

[Kagain]

A few profiles for those in need

Medium:
SD (DXVA-AVCHD)
HD (DXVA-AVCHD)
HD (DXVA-PS3)
HD (DXVA-Blu-ray)

Slower:
SD (DXVA-AVCHD)
HD (DXVA-AVCHD)
HD (DXVA-PS3)
HD (DXVA-Blu-ray)

Needs a x264 build patched with nal-hrd

http://www.mediafire.com/?znoqzwm2kdf

[Zathor]

No more x264 default setting =((
Hix, I may try to be adapt in using command line.
Sorry, I do not understand your posting. Maybe it's too late for me... Can you please explain?

Hope I get you right by "with out UAC" I untick the option run meGUI as administrator in meGUI properties and tried to open meGUI and the result is as follow


Sorry, I did not have made myself clear enough. Please copy a file with the windows explorer in the directory c:\program files\megui\allprofiles\x264 and a file in c:\program files\megui. I assume that the last one will work without prompt and the first one only if you confirm the administrative prompt. Is this correct?

I have thought this through a little more, and here is how I would propose the MeGUI "presets" work from here on out:
1. On the main screen, add a drop down menu for the "Speed" and the "Tune" options in X264. So, instead of just selecting the "preset", you would select the "preset", the "speed" and the "tune". In the case of "speed" and "tune", the first option in the dropdown would be to default to whatever is set in the "preset" you choose.
2. But, if you select, for example, "Animation" in the "Tune" dropdown, that would override whatever option is set in the preset for "Tune". The same for "Speed".
3. The included presets, then, would serve mainly to provide different "types" of encodings, such as for Blu-ray standalone, for IPod, DXVA compatible, etc.
4. There would NOT, however be duplicates for whether you want it to go fast or slow, high quality or low quality. All that can be decided at the time of encode using the two drop downs on the main menu.
5. The end result would be far fewer presets, easier to maintain, with much greater flexibility for the end user regarding speed/quality and tuning.

What do you think?
It seems to be not my day :) So I need to ask a few questions:
1) main screen = main configuration screen of the profile or the main screen?
speed = x264 preset and preset = profile?
3) so we have basic rulesets for the devices? great!

More or less this is the way I would want it to be, but everybody keep the feedback flowing!

[Aoshi101]

reverted back to old encraw as requested

updated to techhouse 1369 patched v2 for nal-hrd

EDIT: reverted back to unpatched 1369, im getting application errors with patched versions...

Well Zathor supplied me with Jeebs' 1369 patched and it works just fine so far. Test out Jeebs' version?

[Adub]

Thank you very much for your offer. Because quantum5uicid3 already provided a mirror we do not need an additional mirror at the moment. I will keep your offer in mind and would like to come back to you later if necessary.


You are certainly welcome. Just let me know if you need me.

[livetolove92]

Sorry, I do not understand your posting. Maybe it's too late for me... Can you please explain?



Sorry, I did not have made myself clear enough. Please copy a file with the windows explorer in the directory c:\program files\megui\allprofiles\x264 and a file in c:\program files\megui. I assume that the last one will work without prompt and the first one only if you confirm the administrative prompt. Is this correct?


It seems to be not my day :) So I need to ask a few questions:
1) main screen = main configuration screen of the profile or the main screen?
speed = x264 preset and preset = profile?
3) so we have basic rulesets for the devices? great!

More or less this is the way I would want it to be, but everybody keep the feedback flowing!

I mean the x264 profiles such as "1pass Extra Quality, 2pass Insane,...". Now it's only x264 Bluray :p.
And actually it get a problem when updating vsfilter like this http://img709.imageshack.us/img709/8669/meguiupdateerror.jpg

[quantum5uicid3]

i put kagain's profiles on the update server as long as there are no objections and updated to jeeb's r1369 patched for nal-hrd support. it seems stable

thank you Kagain

I made an installer, it includes the latest version of megui and the contents of the update server. the uninstaller removes everything except the allprofiles directory and there's no taskbar shortcut. there's no check for previous version, it should safely overwrite any previous version, but if you do have problems, uninstall old and then install new

Installer (http://www.mediafire.com/?q2hw1zza5jn)


vsfilter prob resolved

[livetolove92]

Well done, mate :D. Tks so much.

[kool]

Thank you Zathor & quantum5uicid3 you guys did a great work :logfile:

and Zathor my problem as been fixed with quantum5uicid3 new installer, hope things go smoothly after now on :p

[Triccotracco]

A few profiles for those in need

Medium:
SD (DXVA-AVCHD)
HD (DXVA-AVCHD)
HD (DXVA-PS3)
HD (DXVA-Blu-ray)

.....

.....

Needs a x264 build patched with nal-hrd


testing SD (DXVA-AVCHD) profile but:

[Information] Log
--[Information] [11/12/2009 06:39:07] Started handling job
--[Information] [11/12/2009 06:39:07] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui patched\tools\x264\x264.exe" --profile high --level 3.1 --preset slower --crf 20.0 --thread-input --keyint 48 --min-keyint 1 --b-pyramid strict --ref 6 --slices 4 --vbv-bufsize 15000 --vbv-maxrate 15000 --aud --nal-hrd --sar 64:45 --output "movie.264" "movie.avs"
--[Information] [11/12/2009 06:39:07] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream: C:\Program Files\megui patched\tools\x264\x264.exe: unrecognised option `--nal-hrd'
--[Information] [11/12/2009 06:39:07] Job completed


seems jeeb's 1369 patched not work properly. Without --nal-hrd works.

Tricco:)

[nakTT]

seems jeeb's 1369 patched not work properly. Without --nal-hrd works.

Tricco:)
Sorry for this noob question. What is --nal-hrd ?

:thanks:

[JoeH]

It seems to be not my day :) So I need to ask a few questions:
1) main screen = main configuration screen of the profile or the main screen?
speed = x264 preset and preset = profile?
3) so we have basic rulesets for the devices? great!

More or less this is the way I would want it to be, but everybody keep the feedback flowing!

Sorry for the term confusion. Yes, I was referring to
"Main screen" of MeGUI, NOT of the profile
speed = X264 preset
Preset = MeGUI profile

So, I think we are in agreement.

[Adub]

Seems to be a small bug when entering in values by hand into the x264 settings dialog window. It basically goes haywire and is very difficult to compensate for.


Also, when scrolling down from 1000 kbps, it jumps to 9999 and then starts to decrease.

[Zathor]

Seems to be a small bug when entering in values by hand into the x264 settings dialog window. It basically goes haywire and is very difficult to compensate for.


Also, when scrolling down from 1000 kbps, it jumps to 9999 and then starts to decrease.

Thanks for the problem report. I will have a look at it. Do you have the problem with all sliders?


Sorry for this noob question. What is --nal-hrd ?

http://mewiki.project357.com/wiki/X264_Settings#nal-hrd
Add NAL HRD parameters to the output stream; used for HD-DVD and Blu-ray compliancy. Depends on vbv-bufsize and vbv-maxrate to be set to be active.

[quantum5uicid3]

not sure if auto update wasn't working because version didn't change or what, but jeeb's 1373 patched is up now.

[nakTT]

not sure if auto update wasn't working because version didn't change or what, but jeeb's 1373 patched is up now.
Thank god. I have been waiting for it.

:thanks:

Edited: I get this error.
Finished parsing update file...
There is 1 file that can be updated.
Updating x264. File 1/1.
Update completed.
0 file was completed successfully
1 file had problem.

[nakTT]

http://mewiki.project357.com/wiki/X264_Settings#nal-hrd
Thanks for the info. No wonder I never encounter issue with 1369, because I did not use that particular feature.

:thanks:

[rack04]

In the new x264 profiles I is possible to break Blu-ray compliance using the tunes. For example, --tune animation increases bframes to 5 while blu-ray specifications say the limit is 3. If you know what settings you need for compliance I would add those to the custom command line so you're not relying on the defaults.

[Kagain]

In the new x264 profiles I is possible to break Blu-ray compliance

You're right about that.

Deleted the animation profiles.
Added reference frames and b frames to the command line so now the tune animation can be used instead.

http://www.mediafire.com/?znoqzwm2kdf

Thanks

[quantum5uicid3]

if i understand the presets and tuning correctly. specifying individual options in the command line does overwrite the tunings, but does not overwrite the presets. i didn't think about this before, so i think we're gonna need more gui changes. someone correct me if i'm wrong.

the update server should be good now, i think it was having trouble parsing the name of the patch for some reason. the hyphen maybe?

[nakTT]

the update server should be good now, i think it was having trouble parsing the name of the patch for some reason. the hyphen maybe?
After I keep on trying, it just succeeded in the end. I don't know what is the problem but it is okay now. Many thanks for providing us the update server.

:thanks:

[quantum5uicid3]

ive been messing with it for a while now, i verified it wasn't working here either. i was confused why, i'm pretty sure it was the hyphen in the patch name though :)

[quantum5uicid3]

so no confusion

[nakTT]

ive been messing with it for a while now, i verified it wasn't working here either. i was confused why, i'm pretty sure it was the hyphen in the patch name though :)
I don't know why and I can't really help as I'm not a programmer. But I'm very glad it is working now. Thanks again.

:thanks:

[quantum5uicid3]

Presets will be used as follows:

--preset name

and apply before all other options. In other words, they override the x264 defaults, which, with the default changes (http://forum.doom9.org/showthread.php?t=148148), will be:

--subme 7 --bframes 3 --weightb --8x8dct --ref 3 --mixed-refs --trellis 1 --crf 23 --threads auto

As such, all options that you set will act on top of the preset you choose, regardless of the option order.

ultrafast:

--ref 1 --scenecut 0 --nf --no-cabac --bframes 0 --partitions none --no-8x8dct --me dia --subme 0 --aq-mode 0

veryfast:

--partitions i8x8,i4x4 --subme 1 --me dia --ref 1 --trellis 0

fast:

--mixed-refs 0 --ref 2 --subme 5

medium:

<defaults>

slow:

--me umh --subme 8 --ref 5 --b-adapt 2 --direct auto

slower:

--me umh --subme 9 --ref 8 --b-adapt 2 --direct auto --partitions all --trellis 2

placebo:

--me tesa --subme 9 --merange 24 --ref 16 --b-adapt 2 --direct auto --partitions all --no-fast-pskip --trellis 2 --bframes 16

For all encodes, regardless of preset or not, using --pass 1 will automatically trigger "turbo" settings, which are as follows and override all commandline options:

--trellis 0 --no-8x8dct --partitions none --me dia --ref 1 --subme MIN(2, previous subme)

This can be disabled using --slow-firstpass.

For all encodes, if you don't set your own --ref option and instead use the default or a preset, x264 will automatically lower --ref if the --level you set conflicts with it. If you set --ref explicitly, it will not override what you set.

Profiles will be used as follows:

--profile name

The options will be baseline, main, and high, which do what you think they do. Note that these override all other options no matter what, with two exceptions.. Because interlaced and lossless coding are options with very explicit meanings, the encoder will terminate with an error if you attempt to use them with an incompatible profile.

Tunings will be used as follows:

--tune name

The options will be "film" and "animation", and will tweak AQ strength, psy-rd/trellis strength, deblock, refs, and so forth:

film:

--deblock -1:-1 --psy-rd 1.0:0.15

animation:

--ref (previousref==1?1:MIN(previousref*2,16)) --deblock 1:1 --psy-rd 0.4:0 --aq-strength 0.6 --bframes 5

All of this is subject to change before final release, and suggestions are welcome.

If you don't use any of the new presets, the only changes for you will be the new defaults, and the automatic fast first pass.

maybe someone can understnad this better, i just kept setting all my options manually, so never bothered to understand this. does "explicitly" setting options override the --tune and --preset or not?

[rack04]

maybe someone can understnad this better, i just kept setting all my options manually, so never bothered to understand this. does "explicitly" setting options override the --tune and --preset or not?

yes it will override both.

[quantum5uicid3]

ok cool thanks. im doing new ones now, it's so tedious :)

[foxace]

Hello and thank you for your excellent work.
Is it possible to make megui compatible with
the new version of "DG NV tools 2.0.0 "
The server "CUVIDServer .exe" does not launch properly, the function resize nvidia not working well.

:thanks:

[quantum5uicid3]

does anyone know? DXVA can now play anything as long as it's h264 compliant, right?

and AVCHD compliant is the same as bluray compliant?

i made some device presets with quality settings ranging from crf 18.5 to 23 in increments of 1.5 and a 2pass. you still need to set the tune option depending on the source and adjust the preset slider for speed adjustments.

[quantum5uicid3]

Hello and thank you for your excellent work.
Is it possible to make megui compatible with
the new version of "DG NV tools 2.0.0 "
The server "CUVIDServer .exe" does not launch properly, the function resize nvidia not working well.

:thanks:

someone buy zathor a gtx 295 and dgnv and i'm sure he'd be inclined :)

[foxace]

someone buy zathor a gtx 295 and dgnv and i'm sure he'd be inclined :)

ok. I send a letter to Father Christmas we'll see if he answers.:p

[Kagain]

you still need to set the tune option depending on the source and adjust the preset slider for speed adjustments.

The problem with making device profiles and still use the preset slider for speed adjustments is that the reference frames will not be adjuster accordingly.

i.e if --ref 4 is set in the commandline and you want a faster profile, the # of reference frames will not be decreased if you use the slider. But that might not matter too much.

[quantum5uicid3]

i know it's not absolutely perfect, but playing with it, ultra fast still goes pretty damn fast.

[quantum5uicid3]

zathor,

the following fields throw an error when trying to delete them to type in a new value, functionally everything is good, it's purely aesthetic.

Maximum GOP Size
Minimum GOP Size
Number of Reference Frames
VBV Buffer Size
VBV Maximum Bitrate

there's also problems deleting the crf and typing in a new value. if i delete it and want 23 for instance, i have to type 3-2.

[Zathor]

the following fields throw an error when trying to delete them to type in a new value, functionally everything is good, it's purely aesthetic. [...] there's also problems deleting the crf and typing in a new value. if i delete it and want 23 for instance, i have to type 3-2.

Thanks and fixed (as soon as I upload the next build)

I noticed how megui passes a parameter to neroencaac.exe that creates a fake chapters in the mp4/m4a container. If this could be fixed so it doesn't create fake chapters,it'd help muxing mp4 and uploading to youtube without using mp4box as a cli.

From the nero aac encoder help:
Note that multiple input files can be specified, they will be encoded together into a single output file with chapter marks indicating source file divisions.
So the problem seems to be a feature which works as designed. I assume a chapter will be created every time a stream is passed to neroaacencoder from stdin.

[nakTT]

zathor,

the following fields throw an error when trying to delete them to type in a new value, functionally everything is good, it's purely aesthetic.

Maximum GOP Size
Minimum GOP Size
Number of Reference Frames
VBV Buffer Size
VBV Maximum Bitrate

there's also problems deleting the crf and typing in a new value. if i delete it and want 23 for instance, i have to type 3-2.
The same issue happen when you want to type bitrate for "automated 2pass".

[Zathor]

The same issue happen when you want to type bitrate for "automated 2pass".

I have checked all input handler in the configuration window. All of them should be ok now.

Can you do this for audio file format as well?
This has been added, too. But the new build is still not available and because of other changes it may take one or two days before this build is available.

[nakTT]

Glad to hear that. Thanks man.

:thanks:

[Evil Ash]

Hi, this is my 1st post and I'm sorry its to report a bug. MeGUI is adding "--sar 1:1" at the end of the command line overriding any custom I add, its a PAL DVD so I'm adding "--sar 64:45" to the custom command line, everything looks fine in the profile, eg."program --crf 21.5 --thread-input --sar 64:45 --output "output" "input" ", I hit encode and heres an edited log so you can see what I mean.
--[NoImage] Job commandline: "x264.exe" --crf 21.5 --thread-input --sar 64:45 --sar 1:1 --output "E:\MKVs\vinny.mkv" "E:\MKVs\vinny.avs"
---[NoImage] avs [info]: 708x548 @ 25.00 fps (171658 frames)
---[NoImage] x264 [info]: using SAR=1/1I'm using the newest installer(thanks quantum5uicid3) fully updated and WinXp-SP3.

[Zathor]

Hi, this is my 1st post and I'm sorry its to report a bug. MeGUI is adding "--sar 1:1" at the end of the command line overriding any custom I add, its a PAL DVD so I'm adding "--sar 64:45" to the custom command line, everything looks fine in the profile, eg."program --crf 21.5 --thread-input --sar 64:45 --output "output" "input" ", I hit encode and heres an edited log so you can see what I mean.

Welcome to the forum!
And thanks for the problem report. I have fixed the error and a custom sar will overwrite the automatically generated one. But I can still not upload the build because of ongoing other changes.

[Zathor]

- [x264ConfigurationPanel] updated the input handling
- [AudioEncodingComponent] + [MeGUISettings] added audio format saving
- [MainForm] changed the unexptected error handler. The details will be only written to the log
- [ProfileConfigurationWindow] icon added
- [ProfileConfigurationWindow] every closing of the form will check if there has been something changed
- [x264ConfigurationPanel] added nal-hrd and aud checkbox (required for bluray; patched x264 is required for nal-hrd)
- [ContextHelp.xml] added and changed a few entries
- removed DGM and DGVC1 Indexer, removed CUVIDServer start
- added DGIndexNV and DGMultiSource support

This is an unstable build only for testing purposes because of the DGIndexer changes. I cannot test it myself (no license) so someone else needs to test it. As soon as the feedback is positive I will merge all three DGIndexer. At the moment all three indexer may not function properly. So do not use it in a productive environment!

If you want to test it, download the build, install as usual, edit the DGIndexNV path in the settings and copy the DGMultiDecodeNV.dll to the megui\tools\avisynth_plugin folder.

Unstable development build!
Link removed

[neuron2]

It crashes MEGUI when I enqueue a script using DGMultiDecodeNV.dll. It opens the preview fine but then crashes when I enqueue a job. This is the problem I have always had.

If you have an Nvidia card I'd be happy to give you a license so you can figure out why Megui crashes.

[foxace]

It crashes MEGUI when I enqueue a script using DGMultiDecodeNV.dll. It opens the preview fine but then crashes when I enqueue a job. This is the problem I have always had.

If you have an Nvidia card I'd be happy to give you a license so you can figure out why Megui crashes.

same for me when I click on queue megui crash and the nvidia resizer don't work the resolution becomes very small

[Zathor]

If you have an Nvidia card I'd be happy to give you a license so you can figure out why Megui crashes.

That would be so great! Thank you very much. Sent you a PM.

Hopefully I can reproduce the crashes, it's easy to solve and the CUVIDServer is not necessary anymore.

I have removed the link in my previous posting because of the existing problems.

[olex99]

I had a look at this a while ago when i was having the same problem. Worked out it was a timing issue between the different threads. When you click Enqueue it opens the script at least 3 times and i guess that on some occasions it wasn't able to dispose of the old one before opening it again.

I ended up putting a Thread.Sleep(50) inside the AVSReader class just after it opens the script and that fixed my problem. Bit of a hack i know, but since it was only for me i didn't care. You might be able to come up with a better solution.

[stax76]

There might as well be a bug on the native side since I have a report DGMultiSource with resize arguments crashing StaxRip which doesn't do anything special other than a few simple VFW calls. Such a bug might not cause issues in a native application but only in managed applications. Some people notice a script running in a native application and don't in a managed application and conclude there is a bug in the managed application but it might as well be a bug in the native component. Often the CLR detects when a native component tries to corrupt managed memory, sometimes the complete managed exception handling fails.

I ended up putting a Thread.Sleep(50) inside the AVSReader class just after it opens the script and that fixed my problem. Bit of a hack i know, but since it was only for me i didn't care. You might be able to come up with a better solution.

Maybe some simple thread synchronization.

[Zathor]

Thanks to neuron2 I have now a license and I am able to reproduce the problem.

I had a look at this a while ago when i was having the same problem. Worked out it was a timing issue between the different threads. When you click Enqueue it opens the script at least 3 times and i guess that on some occasions it wasn't able to dispose of the old one before opening it again.
You really do not want to know how many times the avs file is opened...

I ended up putting a Thread.Sleep(50) inside the AVSReader class just after it opens the script and that fixed my problem. Bit of a hack i know, but since it was only for me i didn't care. You might be able to come up with a better solution.
Tried this "hack", too, but I had no luck. Even with very high values and explicit dispose of the opened avs the program crashed without error handling in places where a error handling should catch it. Also I was not able to attach the CLR to the process. DGMultiSource errors out with cuCtxCreate() failed

It's too late now to check this further. Will have a look at it tomorrow.

[BuckMaster]

I want to thank you Zathor for all you do and time spend for Megui.I read this tread from the start, Megui is an app who worth more and you are one of the people who can prove that.
Cheers bro!:D

[medp7060]

Agreed. It seems that MeGUI is one of the best x264 GUI out there, but its develpment is not as avtive as before. Hope it is not another GKnot.

[JoeH]

Thanks to Kagain and Quantum for their work on v1 and v2 of the profiles. I have done some more work on the Bluray profiles, and am attaching the results.

NOTE: These profiles will ONLY work with the new version of MeGUI that Zathor has not yet released which has the checkboxes for the --aud and --nal-hrd options.

Here is a list of the changes I made and why:

1. Increased Bitrate on 2 pass to 8000 - Typical usage for a DVD9. The setting of 700 is not realistic for Bluray compatible devices.
2. Turned on Turbo on 2 pass - Default option, should always be used except in cases of extreme need.
3. --keyint 24 --min-keyint 2 - Required by Bluray specifications according the x264 Wiki
4. Moved everything I could off the "Custom command line" - It is not necessary to put everything that shouldn't change on the "Custom command line". It is enough that it appear in the command line. Anything that simply appears in the command line will take preference over the X264 "preset" and "tune" option. Because of this, the only thing I included was --bframe 3, as this is the default and thus does not naturally appear.
5. Selected the --nal-hrd and --aud checkboxes which Zathor added (Thanks Zathor!)
6. Slightly modified the CRF values - I changed "Very High Quality" to 15.0, which is what is recommended in the x264 official documentation as giving extremely high quality. I adjusted the values of Balanced and High Quality to step gradually up to the value of 23.0 in Standard.
7. Removed the difference between 1080p and 720p - X264 does nothing to resize the video. So, there is no need to have different profiles for 1080p and 720p. Therefore, I eliminated the redundancy and kept only 1 set of Bluray profiles, which should be used both for 1080p and 720p.

I think that's about it. If those changes seem good to you, please delete the v2 Bluray profiles and include these ones. Thanks!

Here is a link to download them: Bluray_profiles_v3.zip (http://www.mediafire.com/?zejiwmyeu0e)

P.S. - If you want to install these manually, just unzip them into the profiles directory. Just keep in mind you will need the update which Zathor posted but then took off.

[quantum5uicid3]

1. i assumed people would use the bitrate calculator
2. yeah, i agree, should probably be left on
3. oops :)
4. the slider and tune will change the commandline beyond just specifying the --tune and --preset is the problem. i think forcing the options in custom commandline is the better idea, because this makes maintaining compatibility for anyone completely dependent on the presets dummy proof(for lack of a better way to put it)
5. ok
6. i would imagine crf 15 would exceed the size of the original source in some cases. in other words, i think it's excessive. since this is a very subjective, i'd like to hear more opinions. maybe a "transparent" preset?
7. the difference is the maximum number of reference frames supported.

[Zathor]

Thank you very much, JoeH!

3. --keyint 24 --min-keyint 2 - Required by Bluray specifications according the x264 Wiki

I have read somewhere that --min-keyint 1 is recommended if targeting bluray. But I can't find the source now.

I'm in the process of bringing a new build online (without the DGindexer changes at the moment). I have changed the version to 1058 so that it can be updated with the new update server.

[nakTT]

Can't wait to give 1058 a try. Thanks Zathor.


:thanks:

[shon3i]

I have read somewhere that --min-keyint 1 is recommended if targeting bluray. But I can't find the source now.Both --min-keyint 1 and --min-keyint 2 are ok, --min-keyint 2 is preffered if stream after encoding goes to authoring application such as sonic scenarist. max --keyint depend of maximum bitrate and fps.

Removed the difference between 1080p and 720p - X264 does nothing to resize the video. So, there is no need to have different profiles for 1080p and 720p. Therefore, I eliminated the redundancy and kept only 1 set of Bluray profiles, which should be used both for 1080p and 720p.

7. the difference is the maximum number of reference frames supported. 6 vs 4 for 720p anyway will not incrase quality that much. I recomend to not use more than 4 ref's in any case.

[neuron2]

You really do not want to know how many times the avs file is opened...

DGMultiSource errors out with cuCtxCreate() failed It's crucial to know that, because the GPU card's memory limits the number of simultaneous script instantiations. So, please tell us exactly how many times the script is opened, when and if they are closed, how they are closed (are they "really" closed, i.e., DGMultiDecode's destructor is called, or some funniness is used such that they are not really closed until Megui exits), etc.

[quantum5uicid3]

Thanks to Kagain and Quantum for their work on v1 and v2 of the profiles. I have done some more work on the Bluray profiles, and am attaching the results.

NOTE: These profiles will ONLY work with the new version of MeGUI that Zathor has not yet released which has the checkboxes for the --aud and --nal-hrd options.

Here is a list of the changes I made and why:

1. Increased Bitrate on 2 pass to 8000 - Typical usage for a DVD9. The setting of 700 is not realistic for Bluray compatible devices.
2. Turned on Turbo on 2 pass - Default option, should always be used except in cases of extreme need.
3. --keyint 24 --min-keyint 2 - Required by Bluray specifications according the x264 Wiki
4. Moved everything I could off the "Custom command line" - It is not necessary to put everything that shouldn't change on the "Custom command line". It is enough that it appear in the command line. Anything that simply appears in the command line will take preference over the X264 "preset" and "tune" option. Because of this, the only thing I included was --bframe 3, as this is the default and thus does not naturally appear.
5. Selected the --nal-hrd and --aud checkboxes which Zathor added (Thanks Zathor!)
6. Slightly modified the CRF values - I changed "Very High Quality" to 15.0, which is what is recommended in the x264 official documentation as giving extremely high quality. I adjusted the values of Balanced and High Quality to step gradually up to the value of 23.0 in Standard.
7. Removed the difference between 1080p and 720p - X264 does nothing to resize the video. So, there is no need to have different profiles for 1080p and 720p. Therefore, I eliminated the redundancy and kept only 1 set of Bluray profiles, which should be used both for 1080p and 720p.

I think that's about it. If those changes seem good to you, please delete the v2 Bluray profiles and include these ones. Thanks!

Here is a link to download them: Bluray_profiles_v3.zip (http://www.mediafire.com/?zejiwmyeu0e)

P.S. - If you want to install these manually, just unzip them into the profiles directory. Just keep in mind you will need the update which Zathor posted but then took off.

ok thanks to JoeH, ive made the changes to presets according to suggested points 1,2,3,7.

zathor we need your thoughts on point 4

[neuron2]

OK, more data on the DG tools problem...

I found a missing close of the CUDA context in DGMultiDecode.dll. So please get the fixed one by redownloading 2.0.0 beta 6. It doesn't fix the Megui crashing but it may cure the cuCtxCreate() failure.

I traced my code and I see Megui doing this:

[open avs]
create DGMultiDecode instance (for preview)
[I close the preview]
destroy instance
[I enqueue the job]
create
destroy
create
destroy
create
destroy
CRASH!

So it should be working with my fix above but it is still crashing.

Also, it doesn't crash with the CUVID server, although I thought I saw that previously.

[Zathor]

- [x264ConfigurationPanel] updated the input handling
- [AudioEncodingComponent] + [MeGUISettings] added audio format saving
- [MainForm] changed the unexptected error handler. The details will be only written to the log
- [ProfileConfigurationWindow] icon added
- [ProfileConfigurationWindow] every closing of the form will check if there has been something changed
- [x264ConfigurationPanel] added nal-hrd and aud checkbox (required for bluray; patched x264 is required for nal-hrd)
- [ContextHelp.xml] added and changed a few entries
- update MediaInfo library and its wrapper to the latest release (0.7.25)

In order to have a stable release the build 1058 is now online. Point the update server to http://www.constructd.com/megui/ and the new version will be applied.

It's crucial to know that, because the GPU card's memory limits the number of simultaneous script instantiations. So, please tell us exactly how many times the script is opened, when and if they are closed, how they are closed (are they "really" closed, i.e., DGMultiDecode's destructor is called, or some funniness is used such that they are not really closed until Megui exits), etc.
After 1058 is out I will continue the work at this front. Sadly it's not easy to answer your question because of the structure the avs are opened/called. Give me a little bit time :rolleyes:

4. Moved everything I could off the "Custom command line" - It is not necessary to put everything that shouldn't change on the "Custom command line". It is enough that it appear in the command line. Anything that simply appears in the command line will take preference over the X264 "preset" and "tune" option. Because of this, the only thing I included was --bframe 3, as this is the default and thus does not naturally appear.

Changing the preset or tune slider will change things a user selected in other areas. That's the way it works now. So if a user wants to have higher speed/quality and moves the slider, some values which are required for device compatibility may be overwritten. For example the reference frames will increase up to 16 and many devices support only 3. I'm still unsure how to change the behavior. At the moment I recommend to put all device values into the custom command line. Device values = values which are required for device compatibility and which may change due to preset/tune changes.

[JoeH]

Changing the preset or tune slider will change things a user selected in other areas. That's the way it works now. So if a user wants to have higher speed/quality and moves the slider, some values which are required for device compatibility may be overwritten. For example the reference frames will increase up to 16 and many devices support only 3. I'm still unsure how to change the behavior. At the moment I recommend to put all device values into the custom command line. Device values = values which are required for device compatibility and which may change due to preset/tune changes.

Quantum and Zathor,

Thanks for clearing that up. I don't understand why it works that way - do you know if it is a bug in X264 or is this specific to MeGUI?

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.

[JoeH]

6. i would imagine crf 15 would exceed the size of the original source in some cases. in other words, i think it's excessive. since this is a very subjective, i'd like to hear more opinions. maybe a "transparent" preset?

At least for Bluray movies it still tends to be smaller than the original, at least in tests I've run. Obviously this wouldn't be for someone who wants to burn to a DVD9, but for those times you want to quickly export a video to actually burn on a Bluray-25 disk, it tends to give about the right size.

Of course, it's not big deal for me to just customize it - so either way is fine with me.

I think Sharktooth used the term "insane" in his profiles to refer to extremely high quality...:p

[Zathor]

Thanks for clearing that up. I don't understand why it works that way - do you know if it is a bug in X264 or is this specific to MeGUI?
It's a MeGUI related "problem". If you change an option it is not locked and it will be changed if the preset/tune changes.

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, more data on the DG tools problem...

I found a missing close of the CUDA context in DGMultiDecode.dll. So please get the fixed one by redownloading 2.0.0 beta 6. It doesn't fix the Megui crashing but it may cure the cuCtxCreate() failure.

I traced my code and I see Megui doing this:

[open avs]
create DGMultiDecode instance (for preview)
[I close the preview]
destroy instance
[I enqueue the job]
create
destroy
create
destroy
create
destroy
CRASH!

So it should be working with my fix above but it is still crashing.

Also, it doesn't crash with the CUVID server, although I thought I saw that previously.
Yes, the cuCtxCreate() is gone but it is still crashing... The good news is as soon as the job is in the queue it can be started without problems. But it's very hard to get it in the queue without crash.

[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.

[neuron2]

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).