full fledged x264.exe GUI [Archive]

Doom9

30th July 2005, 20:13

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

30th July 2005, 20:28

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

jellysandwich

31st July 2005, 02:59

I assume NET framework is required?

js

Doom9

31st July 2005, 11:01

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

Blue_MiSfit

1st August 2005, 01:55

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

1st August 2005, 02:06

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

1st August 2005, 06:55

Blue_MiSfit

1st August 2005, 09:30

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

1st August 2005, 10:04

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

1st August 2005, 10:22

Doom9

1st August 2005, 10:54

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

1st August 2005, 17:17

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

1st August 2005, 17:37

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

1st August 2005, 19:11

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

1st August 2005, 19:40

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

1st August 2005, 19:46

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

4th August 2005, 19:42

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

14th August 2005, 14:12

is 2.1.9 going to be released?

Doom9

14th August 2005, 14:18

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

14th August 2005, 14:23

ok :)

Koti

14th August 2005, 19:35

the new release resizes properly even with granny fonts.

Nice :D

darkside40

17th August 2005, 18:53

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

18th August 2005, 21:23

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

18th August 2005, 22:51

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

19th August 2005, 09:45

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

19th August 2005, 09:57

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

19th August 2005, 10:24

/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

19th August 2005, 10:25

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

19th August 2005, 11:01

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

19th August 2005, 11:24

How is frame rate set in the GUI?

Doom9

19th August 2005, 11:27

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

19th August 2005, 12:09

@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

19th August 2005, 12:52

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

19th August 2005, 12:58

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

19th August 2005, 18:35

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

19th August 2005, 23:16

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

Doom9

21st August 2005, 20:39

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

bob0r

22nd August 2005, 00:10

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

24th August 2005, 10:56

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

24th August 2005, 11:21

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

25th August 2005, 03:50

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

25th August 2005, 09:18

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

28th August 2005, 21:56

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

vidhead

29th August 2005, 11:34

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

29th August 2005, 12:08

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.