x264gui

[bond]

algern0n has converted the x264vfw gui code to a standalone gui app, which can be used as gui for the x264 commandline encoder

with the gui you can encode from an .avs source directly to .mp4 or to raw avc
the gui offers the same options as the vfw one (of course) and also anamorphic signalling

algern0n will most likely not have time to continue working on the gui and therefore it would be great if someone else could take it over and add all the other funky options the commandline encoder offers

enjoy!

ps: ps its written in C and only 30kb big :D

[virus]

for those of you not familiar with IRC and the #x264 channel in particular, "algern0n" is actually me :D

a few quick notes:

x264gui is a normal Win32 application. It runs on all Windows platforms out there without the need to install extra stuff - however, x264.exe is required :)
x264gui doesn't use VfW at all. It's just an interface to the cmdline encoder.
the above package contains a binary executable and full source (everything GPL'ed, of course). No extra libs needed for building it. I've used MinGW and gcc 3.4.2. The exe is only 28 KB or so, since it only relies on standard libs shipped with the OS (I love compact executables :))
doesn't support raw YUV input. That would require extra dialogs to input width and height of the clip and is rarely used, so I didn't bother to add it.
being a normal Win32 app, you don't need to launch it from a dos or bash shell. However, it opens a (dos) console to show the output of x264 CLI if you choose to run the encoding pass on the fly. Alternatively, you can save your config to a batch file of your choice to run it later.
make sure to install it in the same directory as x264.exe or, even better, put x264.exe in one of your PATH directories.
saves the config in the Registry, but in a different place than x264vfw so the settings won't mix.
only one instance of x264gui can run at any given time. If you try to launch it twice, the 2nd instance won't start.
I've replaced the useless fourcc box with a PAR width/height widget (yes, SeeMoreDigital, that's for you :D)
not fully tested. use at your own risk.
I encourage people at taking over the development. It's not so hard. Also, other than pure C code, other things like a bit of documentation and an icon for the exe are lacking... anyone?


for all troubles you must address your complaints to bond, Project Manager, PR, and Lead Chatterer of the whole thing. It was bond pushing for such a solution - he believes that x264gui will kill the obsolete VfW interface... :rolleyes:
Personally, I've just stepped in using a free day for providing a working codebase people can improve on. Unfortunately I have no time to mantain it :(
So...

enjoy :)
virus aka algern0n

[Chainmax]

This is great. All we need now is for someone to start digging through all the threads and whip up a quick guide including generally recommended settings for us n00bs :).

[opsis81]

Many :thanks: to virus for his wonderful gui

[bob0r]

Many :thanks: to virus for his wonderful gui

Also thank Sharktooth, who writes the VFW GUI what this CLI GUI is based on!
And hopefully soon with pthread support, highly experimental! :D

:thanks: ALL!

P.S.
x264gui.exe added to x264cli.exe on my x264 website.

[virus]

I don't understand jeryll's post. This thread is about x264gui. Posting screenshots of another program here is highly confusing imho. Could a moderator please split that post to a different thread?


Sharktooth, who writes the VFW GUI what this CLI GUI is based on!
Well, no :)

x264gui is based on the current GUI present in SVN, not the new one Sharktooth is working on. Credits for the current VfW GUI go to a lot of people (it's basically XviD VfW readapted)... I'm not even sure how many devs contributed code to it. At least 6 or 7 for sure.

Anyway thanks for mirroring the package :)

[bob0r]

@virus

Ok Ok Ok :goodpost:

:scared:

[Blue_MiSfit]

this may be a bit OT, but I am wondering exactly what to do with the lovely raw .264 streams that the cli encoder can output. I did a quick encode of 2000 frames, and want to package the raw stream in MKV. MKVToolnix didnt know what to do with the file when I drag and dropped it. :confused:

help the raw stream n00b :)

-Misfit

[celtic_druid]

MKVmerge takes mp4 as input for native AVC muxing.

[berrinam]

.264 files can be put into the mp4 container through mp4box or mpeg4ip. See YAMB (http://forum.doom9.org/showthread.php?t=93927) for a gui for mp4box

EDIT: avc2avi should also put these streams into the avi container, but I have never used it.

[JoeBG]

Thanks for this wonderfull gui

[hpn]

Is there a way to do an unattended 2-pass encoding with this beauty? The gui looks so sexy and simple so I may decide to trash VirtualDub completely for my future x264 encodes.

[Doom9]

well, for automated twopass, audio encoding, dgindex project creation, avisynth script creation, overhead calculations, profiles, etc. you may want to turn to megui: http://forum.doom9.org/showthread.php?t=87567

It currently requires mencoder for x264 encoding but x264.exe support is on the todolist and shouldn't be too hard (and of course all the other features that are already in there will also be available in x264.exe mode). I had a volunteer who was going to make a much more userfriendly gui and not wanting to make his work more difficult I put development of any features that touch the GUI on hold for a while but now I haven't heard from him in a bit so I might resume and just do the GUI myself.

[Krismen]

What happend to x264cli gui post?

[JoeBG]

...so I might resume and just do the GUI myself.

I miss some features:
- zones
- abr first pass (--bitrate xxx --ratetol 2.0 --pass 1)
- b-pyramid
- weightb
- me "umh"

Most of this is possible in MeGUI. I think a standalone x264GUI should have all this.

[virus]

I miss some features:
- zones
- abr first pass (--bitrate xxx --ratetol 2.0 --pass 1)
- b-pyramid
- weightb
- me "umh"

I think a standalone x264GUI should have all this.
I think that x264gui already has b-pyramid, weightb and ABR first pass :)
(at least, if I understand correctly, CBR has been nuked so a bitrate-based single pass *is* ABR by default).
Also, the first pass of Nth pass is already bitrate-based in x264gui (no longer qp-based).

[SeeMoreDigital]

Thanks Virus,

Cool... I like my anamorphic signalling. Nice to know somebodies thinking about me...

:D

And... How difficult would it be to add .d2v source file support?

[bob0r]

@bond
@virus

Since x264 build 260, VFW now has threads/ratio/8x8dct
Is it possible to update the x264gui.exe?

[Doom9]

@bob0r: I think Unfortunately I have no time to mantain itkinda tells it all. I guess it's time to take out the W32 API skills ;)

[bob0r]

@Doom9

Thats why i directed it to bond also ;)

And VFW is kinda up-to-date now, it wasn't when that gui was made, so 1 update per month should be doable.

At least it takes less time then teaching me :p

[virus]

Since x264 build 260, VFW now has threads/ratio/8x8dct
Is it possible to update the x264gui.exe?
Yes.

Already added an icon (courtesy Sharktooth and... you :)) and some support for 8x8-ready commandlines and other minor improvements, but I'm waiting for Celtic Druid to release the source of his new enlarged VfW GUI with all the options (8x8, ME type, ME range, B-bias and so on).

I think I can find some time to merge CD's GUI into x264gui this monday... but I need the sources. I've downloaded his latest test versions (binaries only) and I'll probably want to edit the GUI a bit (adding a box to input a zones string, for example - this doesn't apply to VfW but can be done in x264gui). I'd just need widgets that work... so CD please share the code even if it's incomplete asap, or I won't have the possibility to fully update x264gui at all :(

EDIT: now I see that some of the changes have been submitted to SVN. But where is the full-featured test GUI posted today on the "x264 development" thread?

[bob0r]

@virus

Maybe you mean http://forum.doom9.org/showthread.php?p=667103#post667103 ?

And about my sweet logo, that's as far as my graphics skills go :D

(and yes i meant svn source)

Also:
When i use the current x264gui.exe, i click OK > Run the encoding pass, nothing happens. Don't know if that's a feature or bug...

[virus]

@virus

Maybe you mean http://forum.doom9.org/showthread.php?p=667103#post667103 ?

Yes. That one. Featuring everything :)
I plan to hack it and add it to x264gui.


When i use the current x264gui.exe, i click OK > Run the encoding pass, nothing happens. Don't know if that's a feature or bug...
maybe a bug in the user? :D

(do you have x264.exe in your PATH? what happens if you open a dos shell and type "x264"? does the cli actually start? x264gui.exe should also work - according to the Win32 API reference, anyway - if you place it in x264.exe's directory - but I haven't tested it)

[bob0r]

@virus

Hack it? you mean just use c_d's source?

And, i have:
C:\Program Files\x264\x264.exe
C:\Program Files\x264\x264gui.exe

And no its not in my DOS Path (i just thought both files had to be in the same dir) (also both files in I:\cap\_x264 does not work, so its not a "space" thing)

If we require a DOS PATH can you tell me how to add it, and maybe even tell me how to add it to: x264\vfw\installer\x264-conf.nsi NSIS script.

I have edited the x264-conf.nsi file myself to add x264.exe and x264gui.exe to the installer


Kinda off topic, but is there a command line tool to add x264vfw.ico to x264.exe?


Edit:
Btw if i was you i would wait when all "possible" bugs are fixed, and c_d gives his GO, reading that thread i see some guy reported a "bug".
Its up to the expert to see if its true :o

[virus]

@virus

Hack it? you mean just use c_d's source?
Can't use that sources as they are. Some mods are needed. Still, using CD's code would save me a lot of time.



And no its not in my DOS Path (i just thought both files had to be in the same dir) (also both files in I:\cap\_x264 does not work, so its not a "space" thing)
That explains why x264gui cannot start the encode... how is it supposed to locate the copies of x264.exe that you have scattered all over your drives? :D

As for adding a directory to your PATH, I have no idea how things are done in WinXP. Under Win9x, I do it the old way (editing c:\autoexec.bat... and then I think a reboot is needed, too - can't remember right now)

For compiling Sharktooth's NSIS scripts, you need "makensis" (cmdline utility which comes with NSIS itself)... and it must be in your PATH, too. Note that MSYS uses the same PATH that you specify for the dos shell, so setting it once for both shells is sufficient.


Kinda off topic, but is there a command line tool to add x264vfw.ico to x264.exe?Adding an icon requires OS-specific code. I doubt x264cli will ever have an icon, though it's doable (lots of #ifdef's required). Besides, afaik you cannot add an icon after the exe has been compiled without it. The only thing you can do is to make a link to x264.exe in your Desktop and tell Windows to associate the icon you want to it :)
(but I bet this is not what you want)


EDIT: Jarod, don't worry, the bug reported by Tommy has already been fixed by Celtic Druid ;)

[bob0r]

@virus

Cool, i am sure celtic_druid is happy to give you his sources, if he didn't already, else a few bears and we are all set.

I meant adding the PATH part TO the .nsi script (not how to use it, hence new install on x264.nl is nsis)


I added the PATH:
<right mouse> My Computer > Properties > Advanced > Environment Variables > System Variables > Path > Edit > added: C:\PROGRA~1\x264

Now when i start x264gui.exe via Startmenu, it does not encode.
When i first open start/run/CMD then x264gui.exe it does encode
But so it does without the added: C:\PROGRA~1\x264 variable.

So uhm, guess we have to start it with cmd :)
A bit more help needed it seems :o


No icon... ok
Bug fixed... ok

:thanks:

[celtic_druid]

PM sent. I'll release a proper diff, after I change some more stuff and do one vs 260, since that already takes into account some of my changes.

[virus]

I added the PATH:
<right mouse> My Computer > Properties > Advanced > Environment Variables > System Variables > Path > Edit > added: C:\PROGRA~1\x264

Now when i start x264gui.exe via Startmenu, it does not encode.
When i first open start/run/CMD then x264gui.exe it does encode
But so it does without the added: C:\PROGRA~1\x264 variable.
Not sure since I don't use WinXP, but my guess is that you're modifing settings which only apply to dos shells but are not, so to speak, "system-wide". So when you launch x264gui from your Desktop, your modified PATH is not used. When you open cmd, though, the new PATH is loaded and x264.exe is found and started correctly.

Unfortunately, I have no idea how to solve this thing under XP. Under Win9x, editing \autoexec.bat in your main Windows drive is sufficient to modify the PATH variable in a way that affects either shells and normal usage (= a link in the Desktop, or in the shell menus). I'll leave the solution to ppl who use WinXP :D

(but you can try copying x264.exe to a directory that normally is automatically inserted in the PATH of every system right after you've installed Windows, like c:\windows. That may work but then you'll have to make sure to update that copy each time you compile a new exe)

[Sharktooth]

It should work but check the "working directory" under the x264gui start menu' link properties.

[bob0r]

It should work but check the "working directory" under the x264gui start menu' link properties.

Start in: "C:\Program Files\x264"

But thats not the problem.
It only works when i start it from start/run/cmd, thats how i always work.
When i double click x264gui.exe (what normal people do :p) it does not encode.

[bob0r]

..

(but you can try copying x264.exe to a directory that normally is automatically inserted in the PATH of every system right after you've installed Windows, like c:\windows. That may work but then you'll have to make sure to update that copy each time you compile a new exe)

That also does not work.

[virus]

Apparently, the problems come from a mismatch between the TEMP/TMP environment variables, which I use (through a standard API function btw) for creating the temporary batch which is launched on the fly, and the directory where WinXP puts the temp stuff for the current user.

I'm currently updating x264gui so I'll include a solution for that issue - and I'll made sure people with WinXP tests it before releasing the update ;)

[leiming2006]

This GUI is out of date.
I think you need to update it.
This GUI seems to be the VFW that is long long ago.

[bob0r]

Would you like to cuddle?

[Sharktooth]

no need to resurrect this thread.
there are plenty of GUIs now and x264 even has it's own one.

[bond]

no need to resurrect this thread.
there are plenty of GUIs now and x264 even has it's own one.it makes as much sense as resurrecting the avc2avi gui :p

[SeeMoreDigital]

it makes as much sense as resurrecting the avc2avi gui :pNice one...

Indeed a GUI where the fps could be set/adjusted would be very useful ;)


Cheers

[SeeMoreDigital]

Does anybody know what the very last x264 VfW build is and where it can be obtained?

[Sirber]

:search:

http://forum.doom9.org/showthread.php?t=116653

[SeeMoreDigital]

Jeez... I was beaten to the punch by less than a day!

Thanks for the link Sirber ;)