full fledged x264.exe GUI

[Doom9]

Here's the first productive release of my x264.exe GUI. It's meant for those who prefer a GUI for just x264 without the additional bells and whistles that MeGUI (http://forum.doom9.org/showthread.php?t=96032) offers. And if you should decide that audio encoding, muxing, and support of other codecs would be nice, there's an easy upgrade path (profiles, settings and even queued jobs are compatible).

You'll need the following additional software installed to use it:

.NET Framework 1.1 (http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&displaylang=en) Version 2.0 final may work as well. Please report your findings.

Avisynth 2.55 (http://www.doom9.org/Soft21/SupportUtils/AviSynth_255.exe) for video frameserving. Beta versions are NOT!!! supported

A YV12 VfW codec. If you have a recent XviD version installed, that will suffice. If you don't get any preview when opening an AviSynth script, install the Helix YV12 codec (http://forum.doom9.org/showthread.php?s=&threadid=56972)

x264 CLI (http://forum.doom9.org/showthread.php?t=89979)

For changelogs, keep an eye on this post: http://forum.doom9.org/showthread.php?p=674495#post674495

[Sharktooth]

thanks doom9... that's what i needed :)

[jellysandwich]

I assume NET framework is required?

js

[Doom9]

I assume NET framework is required?Yes. It is based on MeGUI code which is C#.

[Blue_MiSfit]

Noticed a bug - when you switch from the main tab to the queue tab, the window gets resized and cuts off some of the UI buttons in the queue tab - particularly the "clear" button. Also, the window does not resize when you click back to the main tab - cutting off other UI elements.

Just thought you should know doom9 :)

-Misfit

[Pirks]

Here's another bug: I load AVS script, select MKV in "File Type", press "..." button to the right of "Video Output", the "Enter name of output" file dialog pops up and... hey, where is MKV in "Save as type" menu at the bottom? There's only MP4 available.

[berrinam]

Noticed a bug - when you switch from the main tab to the queue tab, the window gets resized and cuts off some of the UI buttons in the queue tab - particularly the "clear" button. Also, the window does not resize when you click back to the main tab - cutting off other UI elements.
Resizing works fine for me.

[Blue_MiSfit]

Resizing works fine for me.

Hmm.. could have something to do with my .net framworks. I had (at some point) the 2.0 beta installed along with most of visual studio 2005. It is now gone, but since then anything .net related has been a little sketchy... It's really time for me to reformat.

Anyone else having this bug?

-MiSfit

[stax76]

Hmm.. could have something to do with my .net framworks. I had (at some point) the 2.0 beta installed along with most of visual studio 2005. It is now gone, but since then anything .net related has been a little sketchy... It's really time for me to reformat.

Anyone else having this bug?


If you've deinstaled 2.0 I don't see a problem, I run 1.1 and 2.0 side by side without problems, after all it's build to work side by side. If more than one version is installed the version should be executed against it was compiled. I would expect that it's a OS problem in particular how your OS does GUI's (themes etc.). Something could be screwd of course, I've even heard some virus scanner could break .NET GUI code so format could help but this should always be the last thing to do. Note that .NET don't make very deeply changes to the system. Did you try to reinstall 1.1, I would always use the english version in case something crashes to have english error messages for posting bug reports.

[Koti]

Noticed a bug - when you switch from the main tab to the queue tab, the window gets resized and cuts off some of the UI buttons in the queue tab - particularly the "clear" button. Also, the window does not resize when you click back to the main tab - cutting off other UI elements.

Anyone else having this bug?

yep , same problem , never had .net 2.0 either

Display res @ 1600x1200 , large fonts (120dpi) , ATI AIW 9600

[Doom9]

Anyone else having this bug?I cannot reproduce this either. I know the problem but I fixed that previous to the release. However, seeing that you're using granny fonts (sorry, I make jokes about this even at work, large fonts cause a lot of problems and basically destroy any advantage of a big resolution.. your 1600x1200 turns into crappy 1024x equivalent by using large fonts so you should've never bought a screen that can handle that reslution).. I could imagine that the fonts are the culprit. Can you post screenshots of how the GUI looks?

Here's another bug: I load AVS script, select MKV in "File Type", press "..." button to the right of "Video Output", the "Enter name of output" file dialog pops up and... hey, where is MKV in "Save as type" menu at the bottom? There's only MP4 available.I can confirm that. It's an omission in the conditional code and works as it should in the full MeGUI. I'll fix this in the next release. It's no issue for an intermediate fix release since even though you can only chose mp4 files in the opening dialoge, the extension doesn't matter anyway.. it will automatically be switched to mkv as soon as you press the OK button in the opening dialog. Adn the same problem also comes up when you set the output type to raw.

[Koti]

Can you post screenshots of how the GUI looks?

1st opened
http://img215.imageshack.us/img215/8748/1stopen8lu.th.jpg (http://img215.imageshack.us/my.php?image=1stopen8lu.jpg)
Q window
http://img95.imageshack.us/img95/941/queuewindow7se.th.jpg (http://img95.imageshack.us/my.php?image=queuewindow7se.jpg)
back to input after q window
http://img215.imageshack.us/img215/3369/afterqueue9nk.th.jpg (http://img215.imageshack.us/my.php?image=afterqueue9nk.jpg)

Just a thought , kurtnoise fixed this in Yamb by making a resizable window, here (http://forum.doom9.org/showthread.php?p=656486#post656486)

Thx from the blind guys at the old folks home ;)

[Doom9]

How does MeGUI behave in this situation? The problem clearly is your DPI settings, and I don't want the window to be resizeable (it's not as simple as setting a flag, you have to make sure it does resize and doesn't look ugly because you're only using parts of the screen).

[Koti]

How does MeGUI behave in this situation?
Errr.... actually never installed/used it :rolleyes:
(guess I should give it a go ;) )
it's not as simple as setting a flag
I bet its is a lot of work , unfortunatly I am clueless on programing :( - was just mentioning how kurt fixed issue.

Ah well my dpi is staying as is ;) , :thanks:

edit - MeGUI behaves very well - can swap back and forth and all parts remain visible.
http://img20.imageshack.us/img20/7661/megui9ij.th.jpg (http://img20.imageshack.us/my.php?image=megui9ij.jpg)

[Doom9]

In MeGUI there's no GUI resizing code (well, almost none, I figure the preview window will give you grief as well, but it might just work out because there are only few GUI elements). Since the app seems to be resized automatically to adapt to the DPI settings, the MeGUI main window should work just fine for you.

[Koti]

MeGUI does fine in all parts - preview window included
would it be possible to make x264.exe GUI behave like this or would it be alot of work ? If not , I understand. :)

[Doom9]

would it be possible to make x264.exe GUI behave like this or would it be alot of workTurns out it was a couple lines of code. I did not write the window resizing code and it wasn't done the way I'd have made it. I have no idea if it's using Form.Size rather than Form.ClientSize or me saving the size of the form after initialization and use that size instead of hardcoded sizes, but the new release resizes properly even with granny fonts.

[Sharktooth]

is 2.1.9 going to be released?

[Doom9]

yup, but as I said in the main thread, I want to wait for the first bugreport (or a lack thereof), as I've made considerable internal changes that affect every mode. You can compile your own as the source code is out, you just need to define X264_ONLY in VS.NET (I'm afraid commandline compilation at this point doesn't work because of the bitmap I'm compiling into the app.. but if you find a way to get around that feel free to share). Please do not post your own builds though.

[Sharktooth]

ok :)

[Koti]

the new release resizes properly even with granny fonts.

Nice :D

[darkside40]

I have tried the MEGui x264 an it works really fine for me.

The only thing that doesent work perfect is the Bitrate Calculator.
When i try to calculate the Bitrate by using the MKV format it crashes when i try to select the aac audio Track.

When i use the MP4 format i can select the aac audio track, but i doesent get recognized in the calculation.
Means, before i select the audio track the calculatet bitrate says 1000k/bits for the Video, and after i selected the audio the Video has the same bitrate.

When i use the Bitrate Calculator of the "normal" MeGui everything works fine.

[Doom9]

alright, I found the culprit. It was a remainder of the simplified calculator berrinam wrote a while back. I must've missed that part when I went over the code and made it more functional.

[Doom9]

the new version is out. Most notably it contains a hopefully fully working bitrate calculator and of course all the changes mentioned in the megui thread.

[darkside40]

THX for the new Version.
The Bitrate Calculator just works fine now, no more crashes.

The only thing i miss in this Gui is the Avisynth Script Creator, this tool is very usefull in the "normal" MeGui an it would be cool to have it in this Version too.

[berrinam]

I really don't see why people use MeGUI x264 edition when they want features from the full edition. In fact, I don't see why people want a x264-only edition except if the full version becomes too daunting. Maybe there is some other reason that I have missed?

[Doom9]

/me fully agrees with berrinam. The only reason for the existence of this version is that some people seem to be happy with a gui for just the x264 executable. the regular megui defaults to x264.exe so unless you change the container dropdown, you can just ignore the audio groupbox and it's pretty much the same then, but you have all the nifty features.

[darkside40]

In the full edition there are too many thing i dont need.
I dont need the AVC Quant Matrix Editor, Chaptor Creator, on click encoder, d2v creator or a muxxer (this thing i do with other progs).

The only things i need is the calculator and the script creator, so i dont have to start Gknot only to generate the avs script.

[vidhead]

i like the x264-only edition, it's clean, clear and crispy. MeGUI full edition is ok too once you realise it has 2 methods of creating jobs.

there was a little problem with MeGUI 0.2.2.0 this morning, the One Click Encoder window would not close (it wasn't 'always on top', more like a 'dialogbox that must be click ok or cancel?) the 1-pass did not start. i think i switched of autorun.

after running DGIndex.exe (1.4.0) - DGIndex has closed - the One Click Encoder would only die with 'end task'. this was repeated several times. dunno why. now it doesn't happen. now it does.

also, i get this error when the above problem did not occur:
avis [error]: unsupported input format (DIB )
could not open input file 'J:\source\VTS_01_1.avs'

"E:\tools\x264\x264.exe" --pass 1 --bitrate 587195 --stats "2pass.log" --filter 6,0 --analyse p8x8,b8x8,i4x4 --qpstep 1 --progress --no-psnr --output NUL "J:\source\VTS_01_1.avs"

i believe the d2v it created is corrupted because all i see is a thin black strip instead of the expected.

btw, avsedit 1.1 is a great avisynth script creator with preview.

cheers

[Peter1234]

How is frame rate set in the GUI?

[Doom9]

i believe the d2v it created is corrupted because all i see is a thin black strip instead of the expected. Not necessarily but there's an error in your AviSynth script for sure. Open the script in a media player and have a look at the error message, that should tell you what it is. I figure either a script error or a missing plugin are likely causes.

now it doesn't happen. now it does.I cannot reproduce that so you need to figure out a reliable method to reproduce this (meaning it happens every time if you that, that and that)

In the full edition there are too many thing i dont need.How about just not using them? It's not like you even have to look at the menu, every menu option has a shortcut (e.g. Control-S for the settings, Control-Q for the quantizer matrix editor, Control-A for the AviSynth creator - basically it's control and the underlined letter).. I never use the menu.

[bob0r]

@doom9

You mind if i include your MeGUI-x264.exe to my x264-xxx-install.exe installer on x264.nl ?

It looks great :sly:

[Doom9]

You mind if i include your MeGUI-x264.exe to my x264-xxx-install.exe installer on x264.nl ?Not at all, I'd be honored. Please just make sure you check this thread when you put out a new build to see if there's a new version.
It looks great Thanks. I hope it works just as great as it looks :)

How is frame rate set in the GUI?Why would you need to set the framerate? The output framerate will match the input framerate. And if you mux a raw stream, even though RAW can apparently contain a framerate, mp4box will need that you specify a framerate or it'll use 25fps and if I'm not mistaken so does mp4creator, so setting a framerate is kinda moot. Just in case avc2avi can use the framerate in a raw stream, you can put "--fps 23.976" in the custom commandline field in the codec configuration. But that would be the only scenario where I see the fps command making any sense. In any other scenario than this big if avc2avi scenario, there's simply no need to do that, hence there's no GUI control for assigning the framerate either. Having every option is nice and all, but if something is of no use, I see no point in adding it.. it just confuses the unsuspecting users.

[Peter1234]

Sorry about the frame rate question. I see that there is no input parameter for frame rate required, the encoder gets it from the input video file.

[bob0r]

Not at all, I'd be honored. Please just make sure you check this thread when you put out a new build to see if there's a new version.

Yup, will check it manually, i added it on x264.nl with a .net link and a link to this thread.

Okay!

[Doom9]

and the first new release is already out. Changes, as usual, can be found in the MeGUI thread.

[Doom9]

a new build is out. It contains improvements and fixes in the bitrate calculator.

[bob0r]

a new build is out. It contains improvements and fixes in the bitrate calculator.

Cool added it, to x264 build 287.


It would be nice if the first post in this thread would show Last Edited, so we don't have to go to the last page just to see if there is a new version ( yes i don't trust version numbers :scared: )

[vidhead]

it's happening again...One Click Encoder is stuck.

ok here is exactly the sequence i've taken:
1. start MeGUI (0.2.2.0)
2. select One Click Encoder (window appears)
3. click ... for video input then select a vob
4. check do not encode audio
5. < did not change suggested output resolution, 640 (vob is 720)
6. Extra Setup - codec - AVC [greyed out] - select a previously configured profile
7. Storage medium = custom, specified a filesize in MB, container is MKV
8. click encode button

the DGIndex prog runs in minimized for a little while then "closes" and the One Click Encoder window is "stuck". the "x" does not work. when i click the Encode button again a dialogbox pops up with "You must select a video file or project name to continue". ->end task.

i opened the d2v file with DGIndex and this time it is ok.

9. i restart MeGUI and there are 3 tasks in the queue, pass-1, pass2 and mux. under status it shows 'error' for pass-1, waiting for the remainder. i re-run pass-1 and the log show the commandline,etc. and then

avis [error]: unsupported input format (DIB )

Not necessarily but there's an error in your AviSynth script for sure. Open the script in a media player and have a look at the error message, that should tell you what it is. I figure either a script error or a missing plugin are likely causes.


ok...with mpc it shows :
Script Error : there is no function named "mpeg2source" etc.

the avs itself contains this only:
mpeg2source("J:\source\VTS_01_1.d2v")
crop(8,0,-0,-2)
LanczosResize(640,480)

bingo. this explains why : MeGUI (?) did not write in/load the plugins dlls. hmmm, does MeGUI know where aviSynthPlugins is?

(for comparison - gordian knot has a place to specify where aviSynthPlugins folder is.)


How about just not using them? ...
that's the other guy not me ;)

[Doom9]

MeGUI (?) did not write in/load the plugins dlls. hmmm, does MeGUI know where aviSynthPlugins is?No, but your System knows. Thus, if you copy dgdecode.dll where it says in the manual (that would be the megui thread, first post, and the readme file in megui) you won't have that problem.

As for the other thing.. I need 100% reproducability. Can you reproduce this every time using exactly the steps you outlined above? Also, you mention 0.2.2.0 and matroska.. 0.2.2.2 contains a crucial bugfix for matroska output in the one click encoder, please try again using the latest version.

And P.S., you should post that in the main MeGUI thread.. this thread is only for the limited version that doesn't have a one click encoder. Thank you.

[vidhead]

jumped from http://forum.doom9.org/showthread.php?p=703072#post703072 (as advised)

ok, i'm on MeGUI 0.2.2.2 full now.
copied DGDecode.dll in MeGUI.exe folder.

did the exact same steps mentioned before. One Click Encoder now closes (not stuck) after DGIndex closes. jobs don't run. same error with the avs script because it does not include the necessary plugins.

when i edit the avs script directly, provide the path and load the avs edited script to Input (tabbed main window) it works.

you could make path to aviSynthPlugins folder user configurable?

[Doom9]

same error with the avs script because it does not include the necessary plugins.Once again this is a user error. I require the avisynth plugins to be in the plugin directory. If that doesn't work for you, then you have to work your way around MeGUI cos I'm not gonna change that, I find the plugin path concept extremely useful and it spares me work.

[Doom9]

a new build is up. As usual, the changelog can be found here: http://forum.doom9.org/showthread.php?p=674495#post674495

[vidhead]

...I find the plugin path concept extremely useful and it spares me work.

where do you find this information from? the registry? an ini file? is in HKLM\Software\Avisynth\PluginDir2.5?

ok, i've avisynth 2.5 and 2.55 installed in 2 different locations. when i install AviSynth 2.55 it "picks" the Gordian Knot AviSynthFolder during installation which i accepted. (shrugs) so all along i assumed my system has it registered there? avisynth.dll in c:\windows\system32 is v.2.55

i dunno about other people doing testings with many different utilities and different builds, but i tend to have several versions installed, if possible, in various drives/locations for the purpose of testing different builds. i think it would be really helpful where paths can be explicitly stated so one may switch them easily without installing and uninstalling and rebooting. in this way we know exactly which programs or dlls are being used each time. only a suggestion.

anyhow, after i copied all the plugins into the place MeGUI was looking for them (i used RegMon - a registry monitering utility do discover where it looks) into c:\Program Files\AviSynth\plugins folder, i'm sorry to say it still doesn't work - the same error happens.

i have worked around this manually.

[Doom9]

MeGUI doesn't look anywhere.. AviSynth does. I'm sorry but having two AviSynth versions installed (why on earth would you do that, it's not like there's any reason to have 2.5 alongside with 2.55, is there?) is an extremely rare case and I'm not catering to the 0.1% audience with special setups.
You can always put a loadplugin("path-to-dgdecode.dll") into any AviSynth script MeGUI writes.

[Doom9]

the 0.2.2.3a build contains nothing new, but it's compiled using csc so it's smaller. I'll leave the VS.NET build up for a few days to see if there are no problems with this new build.

[Sharktooth]

I would like to include the stripped x264 MeGUI with my binaries as bobor did. Can i do it?

[Doom9]

Can i do it?Absolutely. The same comments apply here (ship an up-to-date version), and one thing I forgot: give a link to the MeGUI thread for further info and the sources (since it's GPL and all).

[Sharktooth]

up-to-date is my second name.... :)
however http://forum.doom9.org/showthread.php?t=89979
test the installer and read the License agreement... i added it "on the fly" but i will include a decent one ASAP.

[Doom9]

looks nice :) I couldn't download the lite version but the full one worked out just fine. will you still keep a non installer version (just the exe) someplace?
One thing: having an uninstall link in a start menu is a big nono in Microsoft's guidelines.. you can accidentally start uninstalling

[Sharktooth]

lite version fixed (damn CAPS!!!)...
The lite version is a non istaller version :) it contains the EXE and the DLL only.
The uninstall link is safe, unless the user is blind and click the UNINSTALL button a second time... :D

[bob0r]

I think i have found some bug, it could be a visual bug only:

When i open megui-x264.exe in dir only with x264.exe (so first time), also 2nd and 3rd..... etc time.

When you go to config > Show commandline, it shows:
"x264.exe" --bitrate 700 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "" ""

When you select Baseline Profile it shows:
"x264.exe" --bitrate 700 --no-cabac --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "" ""

When you go back to Main Profile it still shows:
"x264.exe" --bitrate 700 --no-cabac --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "" ""

When you go to High profile, it remains:
"x264.exe" --bitrate 700 --no-cabac --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "" ""

So the --no-cabac stays there, is this only a visual bug, or will this affect your encode?


Also, when you go to High Profile directly, Show commandline does not change...

[Doom9]

well, by default CABAC is turned on.. then if you select the baseline profile, it is turned off (unchecked). Main profile doesn't require CABAC, and neither does high profile require lossless, or 8x8dct / i8x8 MBs.. hence if you up the profile, more GUI options become available but they are not automatically selected, and thus the commandline stays the same. If you select a lesser profile, the commandline can change because certain options have to be disabled as they are not compatible with the selected profile.

[bob0r]

I understand, and you are correct.

Its just rather confusing, that you have to recheck all options that were enabled by default.

But i guess when you start megui-x264, you have to right away save your own profile!

[Doom9]

Its just rather confusing, that you have to recheck all options that were enabled by default.Imagine coding a multi level history for that, that would be beyond reasonable. Incidentally, no program I know of, offers anything similar, and with profiles, there's really no need for it.

[akupenguin]

One solution that doesn't need a history: The profile selction could by applied during commandline generation instead of modifying the options selected.

[Doom9]

One solution that doesn't need a history: The profile selction could by applied during commandline generation instead of modifying the options selected.and then people would ask me "why is the commandline not showing this option even though it's selected in the GUI?" ;)

new release is out, enjoy.

[bob0r]

Ok, if thats the problem i agree with you.

We still love it! 0.2.2.5 added to x264.nl installer.

:thanks:

[stephanV]

and then people would ask me "why is the commandline not showing this option even though it's selected in the GUI?" ;)
A greyed out option is generally assumed not to be used. This is how it's done in virtually every other program or GUI. (e.g. x264 VFW)

It's you choice of course.

[Doom9]

the CodecSettings property is painfully oblivious to greyed out ;) Lowering the profile, then increasing it again is rather pointless to begin with.. those who know what they're doing will not have the slightest problem with this behavior. And those that don't fit this criteria can always learn.. at times this is to be prefered over the dumb solution <evil grin of an arrogant developer>

[Selur]

would be nice if you could support mp4(aac) as audio input and mux it with the created mp4(x264) file :)

[berrinam]

For non-x264 features, use MeGUI full version.

[bob0r]

would be nice if you could support mp4(aac) as audio input and mux it with the created mp4(x264) file :)

For now its best to use MeGUI-FULL anyway, as .mp4 output of x264 is not quite there yet.
( http://forum.doom9.org/showthread.php?t=99909 )

I just use MeGUI-x264 for raw output (.264) and just mux the video with the latest MP4BOX.

Simply mux:
MP4Box -add video.264 x264.mp4
MP4Box -sbr -add audio.aac x264.mp4 (-sbr only for HE-AAC/AAC+/AAC+SBR(+PS))

... assuming MeGUI-FULL muxes the .264 video file with mp4box.

[Doom9]

as .mp4 output of x264 is not quite there yet.well, shit in shit out. Clearly something is wrong with AVIs that have those outrageous dwScale and dwRate values.. it's probably another Microsoft "feature", but it's not like a file having the proper values would cause any problems.

[stephanV]

Nothing is wrong with those AVIs, it is nowhere defined dwRate and dwScale are not allowed to have those values. A video file should be allowed to have any arbitrary framerate, not just 23976/1000, 25/1 and 2997/100. Note that the mp4 output of x264cli is so far the only thing that exhibits those problems. It would be more logical to seek the problem there. (for MKV it is fixed already)

[bob0r]

Is there a way to add http://x264.nl/x264.ico to the megui.exe shortcut in Start/Programs/x264 just like VFW configuration?
( rundll32.exe x264vfw.dll,Configure x264.ico but then for megui-x264.exe)

The reason i ask here is, if its not possible, is there a way to alter megui-x264.exe with some tool to change the icon, if thats a yes, is it allowed by doom9 to alter your file?

[Sharktooth]

Yes, it can be done the in same way as for x264 VFW configuration icon.

[Doom9]

you can assign any icon to a shortcut you want. If you want to design a nice MeGUI icon, you're of course also welcome ;)

[bob0r]

you can assign any icon to a shortcut you want. If you want to design a nice MeGUI icon, you're of course also welcome ;)

Well you can use our sweet x264.ico for megui-x264 :)
As for megui-full, i would not dare to design an icon for it :scared:

:script: (i just like the smilie of this one)

[bob0r]

Yes, it can be done the in same way as for x264 VFW configuration icon.

CreateShortcut "$SMPROGRAMS\x264\x264 command line interface encoder.lnk" $INSTDIR\megui-x264.exe $SYSDIR\x264.ico possible?

Please explain to me how its done.

Windows wont update my icons in the start menu
CreateShortcut "$SMPROGRAMS\x264\uninstall x264.lnk" $INSTDIR\x264-uninstall.exe still shows the original NSIS icon, while C:\Program Files\x264\x264-uninstall.exe uses the new icon.

Any way to reset how windows reads the icons?

[Sharktooth]

1 - RTFM :
4.9.3.4 CreateShortCut

link.lnk target.file [parameters [icon.file [icon_index_number [start_options [keyboard_shortcut [description]]]]]]

Creates a shortcut 'link.lnk' that links to 'target.file', with optional parameters 'parameters'. The icon used for the shortcut is 'icon.file,icon_index_number'; for default icon settings use empty strings for both icon.file and icon_index_number. start_options should be one of: SW_SHOWNORMAL, SW_SHOWMAXIMIZED, SW_SHOWMINIMIZED, or an empty string. keyboard_shortcut should be in the form of 'flag|c' where flag can be a combination (using |) of: ALT, CONTROL, EXT, or SHIFT. c is the character to use (a-z, A-Z, 0-9, F1-F24, etc). Note that no spaces are allowed in this string. A good example is "ALT|CONTROL|F8". $OUTDIR is used for the working directory. You can change it by using SetOutPath before creating the Shortcut. description should be the description of the shortcut, or comment as it is called under XP. The error flag is set if the shortcut cannot be created (i.e. either of the paths (link or target) does not exist, or some other error).
2 - to reset the icons completely uninstall the previous version (remove the uninstall and the icon if they're still there), reboot and reinstall the new version. If the icon is still not refreshed, start in fail safe mode with command prompt and delete the windows icon cache file.

[bob0r]

1: i tried
CreateShortcut "$SMPROGRAMS\x264\x264 command line interface encoder.lnk" $INSTDIR\megui-x264.exe x264.ico
and
CreateShortcut "$SMPROGRAMS\x264\x264 command line interface encoder.lnk" $INSTDIR\megui-x264.exe $SYSDIR\x264.ico

i did read RTFM, i even tried search with google, but without samples i am completely clueless here. Too bad i am not as smart as i look :cool:

2: ok seems a reboot is needed (sjees i hate that)

Edit:
Ok i got it fixed now, from the same FM:

CreateDirectory "$SMPROGRAMS\My Company"
CreateShortCut "$SMPROGRAMS\My Company\My Program.lnk" "$INSTDIR\My Program.exe" \
"some command line parameters" "$INSTDIR\My Program.exe" 2 SW_SHOWNORMAL \
ALT|CTRL|SHIFT|F5 "a description"

When you add rundll32.exe, x264vfw.dll,Configure is the "some command line parameters", so for megui-x264.exe, i had to add "" ( $INSTDIR\megui-x264.exe "" $INSTDIR\x264.ico ) Bleh, no wonder i didn't get it!

Anyways enough OFF Topic, doom9 feel free to remove all useless posts in this thread.

[Doom9]

new build is up. enjoy!!

[bob0r]

new build is up. enjoy!!

Attachments Pending Approval
MeGUI-x264.0.2.2.6.zip

:D

[bob0r]

@Sharktooth
(r327B) Updated MeGUI-x264 to version 0.2.2.6a (support for Adaptive Quantization and Mixed Refs).

Where can this be found?
Or was it a private build, just to test your builds and patches, because AQ was not submitted to SVN yet?

[kurt]

http://forum.doom9.org/showthread.php?t=89979
-.-> the "x264 Full package" contains r327B, isn't it?

[Sharktooth]

it's in the megui development thread, and yes, it's for testing.
Bugfixes:
-The OneClickWindow doesn't crash when trying to use 'Don't Encode Audio'
-DGIndex doesn't crash when aborting jobs
-MeGUI won't let you try to open the Process Window when running DGIndex, which would lead to a crash.
-root directory bug discussed with haubrija in main MeGUI thread

Cosmetics:
-MeGUI will give a message if there are jobs queued, but not waiting (eg done or postponed, etc)
-Better managing of 'Don't Encode Audio' with the container format dropdown

New features:
-load simple DGIndex jobs
-add '--mixed-refs' option for x264
-add AQ options for x264

[mezzanine]

Can i have a link to the latest source code?

thanx

[Sharktooth]

It's in the MeGUI Development thread.

[Doom9]

a new release is out. enjoy

[Doom9]

a new build is up. This marks the first x264 gui to support the new --crf switch.

[Sharktooth]

doom9, look at the MeGUI main thread plz.

[Doom9]

done.. hope the a build works for your distro.

[bob0r]

It could be wise to make a Megui-x264-SVN and a Megui-x264-Sharktooth build, as for example SVN revison 334 does not support AQ and --subme 7 yet.

[Doom9]

well.. autoaq is off by default and I suppose many people won't even bother looking for it.
I have enough revisions to take care of as it is and another one is simply out of the question. Whoever uses options that their build doesn't support only has himself to blame.. it's like using a unicode build on w98. And the software requirements do point to Sharktooth's custom builds ;)

P.S. Just so that you don't get the wrong impression, I know where you're coming from, but the effort to add another conditional compilation switch compared to the use (these patches are going to be committed in the forseeable future and thus I would have to remove that switch again), just telling people or having them fail (if you use an unsupported option x264 will tell you so you'll only commit that error once) is imho preferable in this case.

[Sharktooth]

for the next builds, i will separate SVN builds from the Experimental builds so MeGUI x264 will have no problems with x264 builds other than mine.
im just waiting AQ gets committed.

[Doom9]

well.. it's not so much a problem, rather you just can't use every switch. It is not completely unlike x264 with mencoder.. you can configure everything but half the things don't make it into the commandline because mencoder doesn't support them.

[Doom9]

a new build is up. As usual you can find the changelog in the main megui thread.

[Doom9]

a new build is out
The changelog of the full MeGUI fully applies to the x264 edition as well this time.

[Sharktooth]

updated x264-Full with 0.2.3.0.
updated custom profiles for version 0.2.3.0.

[Doom9]

A new build is out. Enjoy avc levels and support for b-frame RDO.

Now I can say it's your turn to update ;)

[Doom9]

@bob0r: since you're also shipping MeGUI with your compiles perhaps we can reach a compromise regarding the non SVC patches. Would it be enough if the options that cannot be used in your build simply were to not be in the GUI? If people were to edit the XML file manually, they could still make use of them, and if they load a profile with them activated, they'd be in the commandline. Plus, a profile with subme7 would just lead to a crash. But hiding the options in question would not be much of a burden (as compared to properly hide everything - even in the config files). You'd just need to make your own compiles with my compile script and warn people that not all of Sharktooth's profiles will work with your build.

[bob0r]

@doom9

I still think we, you/me, should focus on the SVN.

Builds for sharktooth can be called beta (also be tested like beta).
Once a patch is updated to the x264 SVN, you could also update megui-x264 to match the SVN options. (With update i mean release a "stable matching x264 svn release")

Or indeed add something like: Enable none-SVN options, for sharktooth or other custom builds.

I dont know how hard it is to generally disable an option for all profiles/settings, until "Enable none-SVN options" is selected, but that would be the best way.


Extra motivation :D:
If i would "demand" a megui-x264 version for my custom builds, then ofcourse you should not change your ways. But i am just working of SVN, thats my standard, everything i do i try to do as basic and generally as possible (Meaning reach the most CPUs with encoding and decoding files)

I think sharktooth's builds are very important and i think megui-x264 should match his updates.
For x264 SVN megui-x264 files, i think my visitors can wait a few days/week before they can test new options. (by then possible more documentation is made anyway)

[Sharktooth]

my builds are easy to identify... the CLI stdout contains:
x264 core:40 svn-362M (built by Sharktooth)in the first line.
An easy check for "Sharktooth" will identify if it's my build or not.

[Doom9]

well x264 is alpha anyway. I won't stop adding support for non supported patches.. MeGUI is basically the only option people have for these patches unless they use the commandline. What you suggest with another checkbox is actually even more work than both ways I've outlined above.
What I suggested above is two lines so it's virtually no effort. But I don't have time to reorganize the GUI and update 4 different files every time a patch gets commited. Furthermore, as it stands now, unless somebody uses subme 7, profiles would be fully compatible which isn't the case if I start modding the settings class for different compiler flags.

[bob0r]

Well then, what ever you find best, its fine with me :)

[DryFire]

With MeGui 2.3.1, the Quene tab remains teh same size as teh jobs tab and does not show the start, stop, pause buttons etc...

It also does not allow me to resize the window.

[Doom9]

damn you visual studio.. stupid GUI designer got rid of the event that should trigger the resize. One thing's for sure: Visual studio's GUI designer is not made for having multiple GUI looks depending on compilation option and has huge trouble coping with that scenario.

[Doom9]

alright, I have uploaded the source code supporting the SVN options only and updated the compile script as well. syntax: compile x264-svn.. you have to compile it on your own though. The a build attached here supports all the patches as usual and fixes the GUI resizing issue.

[bob0r]

Attachments Pending Approval

(just delete this message when done)

[Doom9]

it should be available now.. but you actually need to compile it on your own and the source code is in the development thread, not here.

[bob0r]

Thanks, its working, great feature.

Please change www.x264.nl to http://x264.nl on the me-gui development thread (man i hate the SUBdomain www. :D)

Thanks!

[orandennison]

Turns out it was a couple lines of code. I did not write the window resizing code and it wasn't done the way I'd have made it. I have no idea if it's using Form.Size rather than Form.ClientSize or me saving the size of the form after initialization and use that size instead of hardcoded sizes, but the new release resizes properly even with granny fonts.

I'm still having the resize problem, and I have never used "granny fonts". I run at 1280x1024 on a 19" lcd, on a nvidia geforce 6600gt, xp pro, .net 1.1. Latest drivers for everything. The full-fledged version of megui doesn't have the problem, but as I change tabs in the x264 version of megui it resizes and stays small, which winds up cutting off part of the screen on other tabs. Sorry if this has been mentioned before, I read through the first 4 pages and didn't see any further mention of this problem. I'll just use the full version, but I thought you should know about this.

Thanks for all your work on this doom9. :D

ps. don't be so hard on people who aren't blessed with good vision. Large fonts were made available for a reason, and as a fellow programmer we shouldn't ignore or make fun of handicapped people just because they make our lives more inconvenient.

[Doom9]

@orandennison: and which build are you using? I managed to break that darned resizing thing in the 0.2.3.1 series so you need I think the 0.2.3.1a release that contains the fix.

[orandennison]

It was the 0.2.3.1a release, here's a picture of how it looks when it resizes. Let me know if there's something else you want me to check on.

http://i2.photobucket.com/albums/y8/quint21/meguiclipping.gif

[Doom9]

that's granny fonts.. 120dpi.. I can even smell it. Regardless, I haven't changed the resizing code at all so for all I know something goes wrong on your PC. I temporarily changed my resolution to 120dpi, endured the pain but the resizing works out here. The thing is, the only problem there ever was didn't look at all like your screenshot.. the horizontal resolution is never changed, only the vertical one is.

[Sharktooth]

found a lot of bugs in command line creation... bugreport in the main megui thread.

[orandennison]

that's granny fonts.. 120dpi.. I can even smell it. Regardless, I haven't changed the resizing code at all so for all I know something goes wrong on your PC. I temporarily changed my resolution to 120dpi, endured the pain but the resizing works out here. The thing is, the only problem there ever was didn't look at all like your screenshot.. the horizontal resolution is never changed, only the vertical one is.

Well, you were right- I was looking in the wrong place. I thought you set large fonts on the "appearance" tab of display properties, but large fonts was actually set on the "settings" tab under "advanced". I disabled large fonts under "settings>advanced", and then tried setting it to both Large and Extra Large under "appearance" and the problem went away. The fonts in the application didn't actually resize though when I changed font size under the "appearance" tab (they stayed normal), so maybe that's why some people thought the problem was fixed? Either way, the problem persists and I'd like to continue to help debug this, so let me know if there's anything else I can try.

[ziw0d0]

Please, add "psnr enabled checkbox" in the new build. Sometimes it happens it is useful.

[Doom9]

Please, add "psnr enabled checkbox" in the new build. Sometimes it happens it is useful.Like when?

[burgerpardis]

nm....answered my own question. thanks for the utility. :)

[lycium]

since the 7th jan updates it now _crashes_ :( before it only failed to install the last few items on the update list.

xp64, athlon x2
.net 2.0, msvc2005 runtimes etc

[Sharktooth]

MeGUI x264 is discontinued. Use the full MeGUI.

[Benus_MinO]

http://www.mininova.org/tor/1236294

anyone can upload it to another tracker or server?

[Sharktooth]

what the f...??!??!?!? they didnt even ask for permission to do that... they also dont redistribute the source code... GPL violation? FORUM RULE 6
also you resurrected a 3 years old thread that's even talking about a different thing for such a stupid request... please...