.NET(1.1) based x264CLI GUI

[jeryll]

requirements:
MS .NET Framework 1.1 (probably don't work under MS .NET Framework 2.0 beta 1 (as reported by guada 2) - reason unknown)
latest x264CLI.exe - download it here (http://forum.doom9.org/showthread.php?p=610495#post610495) - (must be in same directory as GUI - must be named x264.exe)
Avisynth ...

BETA state ...
source available on demand
(just send me PM with email and I sent it to you - but I warn you - this code is uncommented (and badly written - so no learn from it :devil: ))

use it ONLY for testing purposes ...
It MAY or MAY NOT work for you
(at least for me it work with no problems so try it ... but do not complain too much ... (I may (or may not) have time to fix ... of course I post corrected (enhanced) version if I (or you) find bug ... or new important feature will be added to x264CLI.exe)

Don't expect too much from it ... it is simple as I want it ... no fancy preview windows ... etc ... only basic queuing ... if you interrupt encoding ... and start encoding again with same jobs - it start from begining ... after interupting it always start from begining ...

ehm ... I'm not very skilled in video encoding "things" ... so there may be missing options in setup ... if I miss something important ... just say it here and explain it ...

remember ... this is home made product for my own use ... so if you find it usefull for you ... be happy ... I'll be too ...

Pictures:

http://img263.echo.cx/img263/6417/x264gui17ec.png

ok ... thanks for comments ... I made some improvements ... here is new version

changelog: (all versions you can now download HERE >>> link <<< (http://mirror05.x264.nl/jeryll/) ) thank you, bob0r :D

todo:
------------------------
total rewrite (internal code structure) of whole gui - (10%)


v 0.1.9 beta
------------
FEATURE: added textbox (on "Zones + Other" tab), where you can enter your additional (future?) x264 commands
FEATURE: gui now can save log files (located in subdirectory logs) based on output to "x264 log" tab
1. log will be written always if all jobs in queue are done or after interrupting by user (based on status of checkbox "write x264.log" on "Zones + Other" tab)
2. each time you right click to "x264 log" tab and choose "Save log!" from context menu
CHANGE: changed internal structure for file with gui settings, it is incompatible with previous version - to avoid GUI crash you MUST DELETE OLD gui settings!

v 0.1.8 beta
------------
BUGFIX: when all partition options are unchecked (in "codec" tab and in "zones + other" tab) into commandline is generated only "--analyse " (thanks to LigH)
BUGFIX: partition analysing options switching profile problems (thanks to MatMaul)
CHANGE: if 8x8dct is deselected, i8x8 is "grayed ..." (thanks to Sharktooth)
CHANGE: removed "fast 1 pass" checkbox (little confusing for some users to have two 1st pass modes)
FEATURE: added 2 "new" enc. modes: "1F pass ABR" + "1F pass CQ" (because of removed "fast 1 pass" checkbox)
FEATURE: gui now show elapsed and estimated time to end of running job

v 0.1.71 beta
-------------
BUGFIX: removed extra b-frame controls (used in testing speedup feature for a2p, a3p - thanks to Sharktooth)

v 0.1.7 beta
------------
CHANGE: --qpmin --qpmax are no longer generated into commandline if no other values are used as x264.exe defaults
CHANGE: removed bitrate value from profiles (less trouble if you work a lot with profiles and you have saved various bitrate values in various profiles)
CHANGE: changed internal structure for profiles, they are incompatible with previous version - to avoid gui crash you MUST DELETE OLD profiles!
CHANGE: changed internal structure for file with gui settings, it is incompatible with previous version - to avoid GUI crash you MUST DELETE OLD gui settings!
CHANGE: little GUI rearrange ...
FEATURE: added -none and -all options into codec tab (usable in partition analysing - if used - only --analyse all or --analyse none is generated to commandline - thanks to Sharktooth, MatMaul)
FEATURE: added special controls for speedup in 1 pass for a2p, a3p automatic generated jobs (if used - they have always priority over your codec settings - but only in 1 pass for a2p or a3p ...) - so now you have chance assign your values and change them if you want - your settings here are saved on GUI exit - (see "Zones + Other" tab - thanks to Sharktooth)
BUGFIX: typo in commandline generation (generated " --bframe " instead of " --bframes")

v 0.1.6 beta
------------
CHANGE: little rearrange in GUI, little rename ...
CHANGE: encoding process now output job start and stop date + time to tab "x264log" + "Jobs"
FEATURE: codec profiles (see readme.txt in zip)
FEATURE: support for custom quant. matrices *.cfg (--cqmfile) and for x264.exe builtin matrices (flat, jvt)
BUGFIX: --fps was not generated into commandline (thanks to leowai)

v 0.1.5 beta
------------
CHANGE: improved usable range of --qp (you can now use --qp 0 (lossless))
CHANGE: encoding process now output job start and stop time to tab "x264log"
FEATURE: fast 1 pass - (this is applicable only for normal 1 pass ABR or 1 pass CQ (because of simple commandline generation routine (and I don't have time now to rewrite this)), but you can simple (as always) create your multi "x" - pass job manually - it is only few mouse clicks :) - thanks to cheburashka, JoeBG)
FEATURE: shutdown PC (FORCED) after all jobs finished - (works only in WIN XP with shutdown.exe in your system32 directory - thanks to Mc Onyx)
BUGFIX: i8x8 independent usage (before it can be used only with --8x8dct and can't be turned off while --8x8dct is in use) - (thanks to Sharktooth)

v 0.1.4 beta
------------
CHANGE: minor changes in some controls (improved usable range, increment, etc., thanks to LigH)
CHANGE: minor changes in command line generator (generation of defaults used in x264.exe (mostly) removed)
CHANGE: renamed "aut. 2 pass" to "a2p", "aut. 3 pass" to "a3p (1-3-3)"
FEATURE: added button in bitrate calculator, so you can now manually recalculate bitrate (before is based on mousemove event)
FEATURE: added --subme 6 (thanks to Sharktooth)
FEATURE: added automatic 3 pass job generation with sequence (1pass-3pass-2pass) - "a3p (1-3-2)" (thanks to LigH)
BUGFIX: fixed bug in automatic source time length calculating routine - if in your WIN locale enviroment is used other decimal separator as dot (thanks to LigH)

v 0.1.3 beta
------------
FEATURE: added source properties (x:y, fps,no. of frames, time length) recognition (based on feedback from x264.exe)
FEATURE: added automatic source time length loading into bitrate calculator (so you need not do this manually)
FEATURE: progressbar (based on feedback from x264.exe, so you must have --progress in your job commandline to have working progressbar)
BUGFIX: fixed bug in bitrate calculator (if you change "feed BR to" to x264 with no values you get error "Input string was not in a correct format" - thanks to lexor)

v 0.1.2 alpha
-------------
CHANGE: most of settings in GUI pre-set to the cli default (thanks sharktooth)
CHANGE: some tooltips here and there added ...
FEATURE: added experimental automatic 2 and 3 pass job(s) generation - with same settings for all (2 or 3) passes (thanks sharktooth)
BUGFIX: some bugfixes (p4x4 requires p8x8)

v 0.1.1 alpha
-------------
CHANGE: removed unused commands and controls (thanks akupenguin)
CHANGE: some tooltips here and there added ...
CHANGE: reorganized controls on setup, setup2 tab
FEATURE: --ipratio (thanks akupenguin)
FEATURE: --8x8dct option + i8x8 too (thanks sharktooth)
BUGFIX: some bugfixes (--qcomp not added on first pass)

jeryll

[bond]

yet another gui for x264cli, looks nice :)

[Sharktooth]

Yep. Really nice.
Adding the new 8x8 options would be great.

[lexor]

Yep. Really nice.
Adding the new 8x8 stuff and threads options would be great.
it does have a threads counter list in Setup2, so unless there is some other option by same name, threads are in :)

[dinolib2]

very nice!
I think it whold be better if cmd line is updated everytime you change something in setup (and not just when you move mouse pointer on the "Add Job" button...).

[Sharktooth]

it does have a threads counter list in Setup2, so unless there is some other option by same name, threads are in :)
Oops... tired eyes... :)

[akupenguin]

... so there may be missing options in setup ... if I miss something important ... just say it here and explain it ...
'RC buf' and 'RC sense' no longer exist.
I don't see a --ipratio (aka "keyframe boost")
'seek' and 'start frame' are the same.

[jeryll]

thanks to all for comments
new version released ... see first post

[Sharktooth]

another suggestion. When ALL partitions checkboxes are enabled, instead of "--analyse p4x4,p8x8,etc..." you can use "--analyse all".

[eqbal]

i can't download it... :(

[Sharktooth]

it needs an approval by a moderator

[yaz]

i can't download it... :(
be patient! it's waiting for approval (as written in the border ;) )

@jeryll
i love u :) my fingertips started wearing out as i edited again and again (and ...) my CLs.
thx a lot
y

[Sharktooth]

Ok, it has been approved:)

[peteag]

status-line could be great!

[Sharktooth]

Another great feature suggestion... it's for 2 pass encodings:
Auto-creation of pass 1 job when user selcts pass 2 only.
Just copy the same settings of pass 2 but with null output (-o NUL) and obviously --pass 1 ;)
Same thing for 3 passes. Auto-creation of pass 1 and 2 jobs.
Also, some settings are not the default ones (for example min q, q step, etc.) could you pre-set them to the cli default, please?

[guada 2]

Hello jeryll, :)

You says that:

" requirements:
MS .NET Framework 1.1 "

and for MS .NET Framework 2.0 bêta 1 ?

[MatMaul]

hello !
it's open source ?
if it is, can you post source please ?
thanks.

[jeryll]

Hello jeryll, :)

You says that:

" requirements:
MS .NET Framework 1.1 "

and for MS .NET Framework 2.0 bêta 1 ?

I think it may run without problem under MS .NET Framework 2.0 beta 1 ... if you have 2.0 beta 1 installed ... just try it ... and you see if it run or not ... ;)

[guada 2]

huuuummm!!!! :)

jeryll
I tested it, the result is negative.
What is the reason of this dysfunction? ;)

:thanks:

[Sharktooth]

the "beta"ness of the .net framework 2.0....

[jeryll]

thanks to all for comments
new version released ... see first post

v 0.1.2 alpha
- added experimental automatic 2 and 3 pass job(s) generation - with same settings for all (2 or 3) passes (thanks sharktooth)
- most of settings in GUI pre-set to the cli default (thanks sharktooth)
- some tooltips here and there added ...
- some bugfixes (p4x4 requires p8x8)
- alternative download added

[yaz]

I tested it, the result is negative.hmmm ... 0.1.2a is running fine here. maybe, i got another 2.0b1 :confused: ... or do i do sg wrong? :D
thx
y

[Sharktooth]

great!
im testing the new additions :)

EDIT: auto 2 and 3 pass seems to work correctly.
well... ill continue to suggest things then :D

[JoeBG]

great!
im testing the new additions :)

EDIT: auto 2 and 3 pass seems to work correctly.
well... ill continue to suggest things then :D
- Load/Save options feature and Reset to defaults.
- Load/Save queue (if i understood correctly how it works it should be similar to the Load/Save options...)
- AVS Edit button - launches the default text editor or notepad and loads the avs file.
- AVS Preview button - launches the avs file in the default media player or windows media player 6.4 (mplayer2.exe).

-creation and loading of custom profiles
- muxing with mp4box

[Sharktooth]

Oh... you use a persistent queue (didnt notice it), sorry for my previous suggestions. Here are new ones:

- Load/Save options feature (basically profiles) and Reset to defaults.
- AVS Edit button - launches the default text editor or notepad and loads the avs file.
- AVS Preview button - launches the avs file in the default media player or windows media player 6.4 (mplayer2.exe).
- Clean codec stats file button.
- Calculator addition: reserve space for AAC audio stream (just checks the diskspace occupation of an .AAC file + "overhead" and subtract that space from the final filesize recalculating the bitrate).

Regarding overhead in MP4, Doom9 has some experience with it. Maybe he can add some words of wisdom :)

@JoeBG: Muxing with mp4box is a bit more tricky (for overhead calculations etc). Lets get a working and precise bitrate calculator first (like the one on MeGUI).

[lexor]

first bug report here:

if you open the gui and go to Bitrate Calc and then change "feed BR to" to x264 you get "Input string was not in a correct format" probably because the other fields aren't set up yet (i.e. blank), but still would be nice if it didn't crash like that.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ParseDecimal(String s, NumberStyles style, NumberFormatInfo info)
at System.Decimal.Parse(String s, NumberStyles style, IFormatProvider provider)
at System.Decimal.Parse(String s)
at System.Convert.ToDecimal(String value)
at x264CLIgui.MainForm.Feedbitrate(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
x264CLIgui
Assembly Version: 0.0.1987.14995
Win32 Version: 0.0.1987.14995
CodeBase: file:///C:/Documents%20and%20Settings/Alex/Desktop/x264CLIgui.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

[Doom9]

@sharktooth: aren't you suggesting all the features that are already in megui (which is even open source so you can add whatever you like)?

you, and joebg make me want to spend my time doing something else than continue development of megui. next time perhaps I let somebody else sweat on stuff that you can't implement that easily and then swoop in once things get easy to reap the benefits :(

[bond]

i also have to say that megui really rocks

[jeryll]

o.k. - I must clarify something ... this piece of software is not aimed against megui (and is newer planned be so complex as megui is - so no muxing or audio encoding is planned here) ...

I post it here because people in forums here complain about not existing GUI for x264CLI.exe ... and because I made one for my own use ... I post it here ... so they have chance and possibility to test newly implemented features in x264 without waiting for latest mencoder ...
that is all ... and I have written in my first post this:

use it ONLY for testing purposes ... (this is for what I made it - I using it only for testing new features in x264)
Don't expect too much from it ... it is simple as I want it ... no fancy preview windows ... etc

I implement some of Sharkstooth suggestion, because they are usefull (not only for me I think) ...

- so in this GUI newer will be audio+video muxing

- only thing planned in bitrate calculator is bugfixing and automatic source time lenght loading (for correct bitrate calculator function)

- maybe I implement Load/Save options feature (basically profiles) and Reset to defaults because this seems usefull for testing purposes...

if anybody want to do some serious DVD backup - I recommend - use megui - it is a wonderfull piece of software, on which doom9 hardly worked long time ...

[jeryll]

first bug report here:

if you open the gui and go to Bitrate Calc and then change "feed BR to" to x264 you get "Input string was not in a correct format" probably because the other fields aren't set up yet (i.e. blank), but still would be nice if it didn't crash like that.


thank you ... fixed

[Leo 69]

Your piece of software is not less wonderful, jeryll. Many of us can not download mencoder versions every day to get the latest x264 because of the slow connection,
but it is MUCH easier to get the latest X264 CLI and your beautiful GUI to enjoy the encoding. Thanks a lot for this stuff.

[Sharktooth]

@sharktooth: aren't you suggesting all the features that are already in megui (which is even open source so you can add whatever you like)?

you, and joebg make me want to spend my time doing something else than continue development of megui. next time perhaps I let somebody else sweat on stuff that you can't implement that easily and then swoop in once things get easy to reap the benefits :(
Sorry Doom9. I didnt intend to suggest features that are already in MeGUI (but since it's made in C# i have some problems with its code), criticize or offend you in any way.
However the point is: since there are already other encoding apps supporting x264 (GK, AutoAC, ARCalculator - to name a few...) why still bothering developing MeGUI?
The answer is easy: coz it's a great tool and you deserve all my gratitude and respect for your great work.
Every day i load my VFW gui project for x264 and i close it after few seconds coz there is ppl asking for it but there is ppl saying "drop it, it's useless coz vfw is for n00bs/vfw is dead/vfw is crap" as well...
That's frustrating since i started to make something i thought it could be usefull and ppl criticize it even before it's finished...
However the point is x264 needs its own gui and someone (jeryll) developed a GUI that seems to meet everything ppl wants from x264. A perfect candidate for being THE x264 gui.
So, i think there's no reason on putting limits on that project.
MeGUI has its own place since it supports x264 but other codecs too, thru mencoder.
It is a generic mencoder frontend, but it will never be THE x264 GUI.
No offense but thats my vision (i still use MeGUI though, as well as many other ppl).

[hpn]

MeGUI has its own place since it supports x264 but other codecs too, thru mencoder.
As of yesterday version 0.1915 supports x264.exe as alternative x264 encoder, so I guess Doom9 now could easily make a "lite" version of MeGUI only for x264 encoding for those quys who don't use XviD and ASP (plus of course keep working on the normal, full-featured verson as well)

[JoeBG]

you, and joebg make me want to spend my time doing something else than continue development of megui. next time perhaps I let somebody else sweat on stuff that you can't implement that easily and then swoop in once things get easy to reap the benefits :(

@ doom9

First of all many thanks for MeGUI :thanks: . It really rocks like band said. It has its own place in mpeg4 encoding and it´s the biggest place because it supports everything we all wish to have. I´ll make a german html-manual for it to support it for the great public and it´s the tool I use for my own encodings.

What we are talking about here is a x264 gui. It´s great, thanks jeryll, but it´s really something different from MeGUI. MeGUI is much more than a gui. :)

[Doom9]

I do have to ask though.. since .NET languages are interoperable.. why not help with MeGUI instead? Except for the commandline generation for x264.exe, everything is has already been there before the first line of this GUI was written.

hpn: all codec configuration will be handled in dialogs in the future.. so basically all that remains is a codec selector.. and of course I could simply deliver a config file that defaults to x264 as codec and x264.exe as encoder and you have your light version. I don't think a split makes sense.. it just increases the workload.

[Koti]

Thanks for your gui - was just what I was looking for. :)

I hope the evolution of this discussion doesnt discourage your work or releasing any updates

[jeryll]

I hope the evolution of this discussion doesnt discourage your work or releasing any updates
here is a little update ... see first post

v 0.1.3 beta
- added source properties (x:y, fps,no. of frames, time length) recognition (based on feedback from x264.exe)
- added automatic source time length loading into bitrate calculator (so you need not do this manually)
- progressbar (based on feedback from x264.exe, so you must have --progress in your job commandline to have working progressbar)
- fixed bug in bitrate calculator (if you change "feed BR to" to x264 with no values you get error "Input string was not in a correct format" - thanks to lexor)

[LigH]

For such small uploads (31 KB), you shall not need a RapidShare account; just attach your file here in this board, a moderator will approve it at most after a few hours.

[bob0r]

@LigH
Already ahead( :devil: ) of you :sly:

@jeryll
Update your first post so LigH knows what the hell i am talking about :D

[jeryll]

@LigH
Already ahead( :devil: ) of you :sly:

@jeryll
Update your first post so LigH knows what the hell i am talking about :D
done ;)

[LigH]

Aah - nice. (But the filename column is too small, ellipses '...' were used.)

[bob0r]

Aah - nice. (But the filename column is too small, ellipses '...' were used.)

Yeah default apache has the same problem, only a longer file names can be used.
I might alter the index.php file later, but best way is to add the direct links
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_1a.zip
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_2a.zip
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_3b.zip

Thats the best way anyway :)

[Koti]

thank you :)

If you hover the mouse over the files on the link it shows the version. ( at least in firefox)

[LigH]

Is it intentional that the "min keyfr int" on the register "Setup" is changeable only by 10 instead of by 1?

The bitrate calculator does not work yet? How bad that I only can enter a target bitrate (not a target size - but that is a limitation of x264 CLI), therefore it is quite essential.

Shouldn't an auto-generated 3-pass use a pass-type sequence of "1, 3, 2" instead of "1, 3, 3" (because the last pass shall not change the stats file anymore, to be able to re-run only the last pass with different settings)?

[jeryll]

Is it intentional that the "min keyfr int" on the register "Setup" is changeable only by 10 instead of by 1?

probably bug while copying from another control (you can enter your value manually) ... and of course I fix this in next release ...


The bitrate calculator does not work yet? How bad that I only can enter a target bitrate (not a target size - but that is a limitation of x264 CLI), therefore it is quite essential.


In latest version (v1.0.3b) calculator works automatically, gui reads source script, then launch for very short time x264.exe with it, get what x264.exe says about source script, then calculate source length from known properties, then load source length into calculator and run bitrate calculation routine ... in my test everything works fine ... ???


Shouldn't an auto-generated 3-pass use a pass-type sequence of "1, 3, 2" instead of "1, 3, 3" (because the last pass shall not change the stats file anymore, to be able to re-run only the last pass with different settings)?

this is from mencoder manpage for x264 (about passes)
Here is how it works, and how to use it:
The first pass (pass=1) collects statistics on the video and writes them to a file. You might want to deactivate some CPU-hungry options, apart from the ones that are on by default.
In two pass mode, the second pass (pass=2) reads the stats file and bases ratecontrol decisions on it.
In three pass mode, the second pass (pass=3, that is not a typo) does both: It first reads the stats, then overwrites them. You can use all encoding op- tions, except very CPU-hungry options.
The third pass (pass=3) is the same as the second pass, except that it has the second pass' stats to work from. You can use all encoding options, in- cluding CPU-hungry ones.

[LigH]

In my test, the playing time was not read into the calculator. And when I manually enter the duration and change the settings, nothing is recalculated.

And for 3-pass: I already know that "pass=3" is a "second" pass, but changes the stats file so that a 3rd pass will use these updated statistics. But the 3rd pass does not need to change the stats file anymore, if no 4th pass follows - and furthermore, I'd prefer to be able to run several 3rd-pass runs on the same stats from a 2nd-pass, but with slightly different settings, therefore the stats file must not be updated again and again on a 3rd-pass.

[cheburashka]

It would be nice to have automaticaly "reduced" options for the first pass in your autogenerated 2- and 3- pass modes as it's done in MeGUI ("turbo" mode) or x264 VFW r.261 ("fast" first pass).

:thanks:

[jeryll]

In my test, the playing time was not read into the calculator. And when I manually enter the duration and change the settings, nothing is recalculated.
Could you please run your "problematic" avs script x264.exe in dos command prompt with this commandline (used in gui for script recognition):
x264.exe --pass 1 --seek 10 --frames 1 -o NUL: your_script.avs
then check x264.exe output if there is line looks like:

example - avis [info]: 704x416 @ 25.00 fps (4001 frames)

x264CLIgui needs this line for recognition of script parameters
(but it seems sometimes is 1 frame check not enough (x264.exe maybe finish sooner than gui is fully started (or output checking threads maybe are slow - if gui is already running), so it's maybe simply miss this avis [info]) ... so I increase it in next version)

and please post your script here (if possible)


And for 3-pass: I already know that "pass=3" is a "second" pass, but changes the stats file so that a 3rd pass will use these updated statistics. But the 3rd pass does not need to change the stats file anymore, if no 4th pass follows - and furthermore, I'd prefer to be able to run several 3rd-pass runs on the same stats from a 2nd-pass, but with slightly different settings, therefore the stats file must not be updated again and again on a 3rd-pass.
if you think it's usable for testing - I add "aut. 3 pass (1-3-2)" in next version and rename old "aut. 3 pass" to "aut. 3 pass (1-3-3)"

[jeryll]

It would be nice to have automaticaly "reduced" options for the first pass in your autogenerated 2- and 3- pass modes as it's done in MeGUI ("turbo" mode) or x264 VFW r.261 ("fast" first pass).

:thanks:
you mean this? - http://forum.doom9.org/showthread.php?p=595200#post595200

if yes - then maybe in next version ...

[LigH]

Script:ImageSource("HDTV%04d.bmp",1,400,25,true)
ConvertToYV12()
Result:avis [info]: 1280x720 @ 25.00 fps (400 frames)
x264 [info]: using cpu capabilities MMX MMXEXT 3DNow!
x264 [info]: slice I:1 Avg QP:23.00 Avg size: 26519 PSNR Mean Y:43.91 U:50.04 V:51.67 Avg:45.25 Global:45.25
x264 [info]: slice I Avg I4x4:12.3% I8x8:0.0% I16x16:87.7%
x264 [info]: PSNR Mean Y:43.91 U:50.04 V:51.67 Avg:45.25 Global:45.25 kb/s:5303.8

encoded 1 frames, 1.33 fps, 5335.20 kb/s
Register "Jobs":
x=1280; y=720; fps=25.00; frames=400; h:m:s=0:0:0

Register "Bitrate calc":
hours=0; mins=0; secs=0; mins T=0; ... bitrate=

[Mc Onyx]

I'd like to thank to Jeryll, for a great and very handy GUI, thank you :)
And i'd like to make a suggestion, for the GUI, maybe you could make an option to shutdown the computer, after completing the last job, if it's not too much trouble or work.Maybe you could use the command: shutdown -s -f -t 0
in the commandline or something, i personally would find it quite usefull. Thanks in advance Jeryll.

[Ishan]

I can't get that thing to work, maybe I'm missing something. I got x264 cli wich works really great alone but with the GUI when I hit encode the programm just do nothing. It shows me the Log tab and that's it, It doesn't even run x264.
Anyone got a clue?

edit: never mind, got it working, it was my dgmpgdec ^_^;

[cheburashka]

you mean this? - http://forum.doom9.org/showthread.php?p=595200#post595200

if yes - then maybe in next version ...

Yes, you're right. I did not see that post. But that is exactly what I asked for.
"disables partitions P-sub8x8 and B-sub16x16" means remove analisys options p4x4 and b8x8, if they selected for full pass.
:thanks:

[jeryll]

In my test, the playing time was not read into the calculator. And when I manually enter the duration and change the settings, nothing is recalculated.

Ok, problem solved ... (this had nothing with calculation routine as I think, but with "Regional and Language Options" used in WIN (I think you are used German(German) settings) ... if you switch to English (for test) ... gui may work correctly ...) - now it is working regardless "Regional and Language Options" settings - and bitrate calculator is recalculating if you move mouse off from controls you are changed (but I add calculate button so now it is easy for everyone)

[LigH]

I love it when I guess well! :D

[Sharktooth]

New value for --subme --> 6

[jeryll]

thanks to all for comments
new version released ... see first post for changelog or download it
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_4b.zip

[Mc Onyx]

Hi! A new option is now available in X264, the Lossless mode. It's enabled, when you set quant to 0(zero), so you can enable it in the GUI, because now it's not possible, it always resets to 1.
Thanks for the great GUI! :)

[JoeBG]

thanks to all for comments
new version released ... see first post for changelog or download it
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_4b.zip
Looks great :) Very good job ;)
But I miss a some features:
- fast first pass (its on the to do list)
- the possibility to define profiles
- an explanation how to calculate the bitrate. My brain is really to small for that. Can I only define one language (=audiostream) by kbps? No extra space?
- lossless mode

Thanks in advance :)

[jeryll]

But I miss a some features:
- fast first pass (its on the to do list)
- the possibility to define profiles
- lossless mode

just look on first post ... feature with (done) statement ... is implemented and will be in next release ... otherwise I'm working on it ...
Can I only define one language (=audiostream) by kbps? No extra space?
In this time - yes ... for basic testing calculations it is enough I think ... BTW I made bitrate calculator used here in gui as standalone application, and because I'm lazy to run two programs at once, I just copy its code to gui code so here is it as I need it ... not much more can be expected (not so hard to include some extra space calculations ... maybe sometimes later)
- an explanation how to calculate the bitrate.
... because my technical english is not so good ... I just look on web and found some (simple I think) explanations (thanks to people which written this)

The bit rate is the average number of bits that one second of video or audio data will consume. You will usually find that better video or audio quality is obtained from files with a higher bit rate which will be bigger in size, while files with lower bit rates tend to have a worse video or audio quality (and smaller size).

If you are looking to take your video footage and edit/fit it onto a DVD or CD you will need to calculate the bit rate to ensure that the best quality/per available space is achieved.

HOW TO - Manually calculate the bitrate
The basic bitrate formula is (this one found on - http://www.videohelp.com/calc.htm)

(Size - (Audio x Length )) / Length = Video bitrate

L = Lenght of the whole movie in seconds
S = Size you like to use in KB (note 700 MB x 1024° = 716 800 KB)
A = Audio bitrate in KB/s (note 224 kbit/s = 224 / 8° = 28 KB/s)
V = Video bitrate in KB/s, to get kbit/s multiply with 8°.

°8 bit = 1 byte.
°1024 = 1 kilo in the computer world.

Example
90 minutes video, L = 90 x 60 = 5 400 seconds
700 MB CD but be sure that if fits use a bit lower like 695 MB, S = 695 x 1024 = 711 680 KB
Audio bitrate, A = 224 kbit/s / 8 = 28 KB/s

(711 680 - (5400 x 28) ) / 5400 = 104 KB/s x 8° = 830 kbit/s.

[Sharktooth]

- lossless mode
Quant 0 encoding automatically enables it. No need for an option.

@Jeryll: Bug in setup tab: when selecting 8x8dct it automatically enables/disables i8x8, also it cant be deselected once enabled by 8x8dct.

[jeryll]

@Jeryll: Bug in setup tab: when selecting 8x8dct it automatically enables/disables i8x8, also it cant be deselected once enabled by 8x8dct.
ah ... this is from x264.exe output

i8x8 requires --8x8dct. (so I made it dependent on --8x8dct)

from actual mencoder x264 manpage:
(no)i8x8
Use additional macroblock type i8x8 (default: en- abled). This option has no effect unless 8x8dct is enabled.

if this is bug, I made i8x8 option independent again in next version

EDIT: (ah ... probably you mean we can use --8x8dct without -i8x8) :rolleyes:
ok - fixed

[jeryll]

thanks to all for comments
new version released ... see first post for changelog or download it
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_5b.zip

[LigH]

Nice day today - one birthday present after another! :D

Nice work. And in case I forgot to tell it clearly: Bitrate calculator worked well in 0.1.4.

[Doom9]

Sorry Doom9. I didnt intend to suggest features that are already in MeGUI (but since it's made in C# i have some problems with its code), criticize or offend you in any way.
However the point is: since there are already other encoding apps supporting x264 (GK, AutoAC, ARCalculator - to name a few...) why still bothering developing MeGUI?

Because it's the best MPEG-4 solution so far. First of all, all those tools came later.. MeGUI was the start.. when I made it there was no x264.exe with avisynth input and mp4 output so x264.exe was basically unusable, and there was no VfW either.

Since then, it does AAC, it does MP4 muxing.. basically anything you need if you are aiming for MP4. None of the other programs you mentioned does all of that. AutoAC is even VfW dependant (as it used avs2avi). GKnot only does AVI, ArCalculator doesn't seem to do MP4 either.

So, i think there's no reason on putting limits on that project.
MeGUI has its own place since it supports x264 but other codecs too, thru mencoder.
It is a generic mencoder frontend, but it will never be THE x264 GUI.
No offense but thats my vision (i still use MeGUI though, as well as many other ppl).By now, the default x264 encoder is x264.exe. But people using x264.exe will want to encode audio as well, and perhaps mux subs. So with MeGUI they have everything in one self-contained place. Why is there a need for anything else? Especially if it's closed source, can use MeGUI a template on how to do things since it's open source, and comes later and doesn't really improve upon things.

I feel no different about this than about all the Doom9 site copycats. So far I have survived them all because I seem to have the longest breath, but it is still very frustrating. And in a way, unethical as well to redo something that has already been done (and given away for as free as free can be). I wouldn't add full fledged audio encoding just to make an alternative to BeLight if I didn't bring something significantly better to the table.. I wouldn't even think to try and compete with GKnot because it does way more than I'd ever wanna do.. the only reason I'm even considering AVI is because I might need it for the next codec comparison.. it isn't yet sure which container is going to be used for the various mp4 codecs. Or looking at muxing, we don't need a second YAMB so MeGUI will always be more limited in that way, it just does what makes sense in an integrated tool.

[Koti]

remember ... this is home made product for my own use ... so if you find it usefull for you ... be happy ... I'll be too ...

jeryll

happy here :thanks:

[LigH]

Hi jeryll,

would you like to add a new register for custom quantization matrices? ;)

There are presets "flat" (default) and "jvt" in rev. 266, and custom comma separated strings as well (for 4x4 and 8x8 transforms, intra and inter, and for 4x4 even single matrices for luma and chroma).

[leowai]

@jeryll,

I didn't see the framerate (--fps <float:rational> Specify framerate) in setup2 works for me. The option was not shown in the command line at the bottom of this GUI.

Does it works for you guys?

regards,
leowai

[Sharktooth]

custom quant matrices added to x264cli

[jeryll]

@jeryll,

I didn't see the framerate (--fps <float:rational> Specify framerate) in setup2 works for me. The option was not shown in the command line at the bottom of this GUI.
Thank you for reporting this. Fixed

[Doom9]

I'm wondering though.. what is specifying the framerate going to do? I mean, if your output is mp4 then the output framerate will match the input and if you're going for raw, since raw has no framerate you can specify what you want but will still have to specify the framerate again in your mp4 muxer.

[akupenguin]

Raw does store a framerate.

[bond]

Raw does store a framerate.
does it handle vfr too?

[jeryll]

thanks to all for comments
new version released ... see first post for changelog or download it
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_6b.zip

[MatMaul]

any ideas :
if all analyse options are tick, "--analyse all" and if none option are tick, "--analyse none"
no copy to command line "--qpmin 10" and "--qpmax 51" because are defaults values

sorry if you don't know what I write, I have problem with english.
thanks!

PS:profiles is very good idea,I use them a lot!

[Sharktooth]

@jeryll: fast 1st pass for automated 2 and 3 passes:
for 1st pass replace user settings with: -r 1, -A none, --me dia, -m 1 and no 8x8dct + the other settings
nth pass with user settings.

(thanks to superdump)

[jeryll]

thanks to all for comments
new version released ... see first post for changelog or download it
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_71b.zip

internal structure of profiles and gui settings is modified, so please delete your old profiles and gui settings (*.xml files in gui directory), otherwise GUI probably crash on startup...

[Sharktooth]

uhm... is it safe to use different b-frames value (or even disable them) between 1st and nth pass?

[jeryll]

uhm... is it safe to use different b-frames value (or even disable them) between 1st and nth pass?
damn! ... sorry ... I mistakenly leave this b-frame option (used to testing this feature) in release version ...

I'm working on this ...
done! v.0.1.71b
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_71b.zip

[Sharktooth]

:)
I just had an idea for improvment... is it possible to "incorporate" the countquant.pl script in the gui? It is quite usefull to analyze the stat files.
Also, a "output to avi" option using avc2avi (encode to raw -> avc2avi -> avi) would be great (i can already hear bond swearing....) :D
Another suggestion... per job process priority :)

[Doom9]

I may sound like a broken record, but MeGUI has the AVI output option. Why would you need anything else. Point me to a feature MeGUI cannot do versus this non open source derivation of my work, and I'll make sure the next release won't have that missing feature. If it isn't about features then I have to take it personally.

[Sharktooth]

Doom9 im really sorry. there's nothing personal. :(

[cheburashka]

@Jeryll
Isn't it a good idea to add 1st pass speedup options to saved profile ?

[MatMaul]

thanks for the changes!!!

[MatMaul]

when I tick "all" in analyse all other analyse's options are grey.
but when I load a profile with "all" ticked, all other analyse's options aren't grey.
I have no problem with none case.

[LigH]

Bug in 0.1.71 b:

- Select "use speedups for 1st pass in a2p, a3p". (Please write numerations!)
- Do not check any macroblock partitions, neither check "all" or "none".

=> The generated 1st pass command line contains "... --analyse --...". This makes x264 exit immediately.

[Ishan]

@Doom9
I don't want to sound agressive or anything, just stating my point. Can't you just leave the poor guy alone? His program is good, and I like MeGUI too, their purpose is NOT the same !
x264gui is really helpfull to do a quick encode to try out settings and generate a video only mp4. MeGUI is mainly aimed for backup purpose.
Just look @ how many divx/xvid encoding tools there are or one click dvd backup?
Diversity is good, let the people choose what they want to use.

[Doom9]

Can't you just leave the poor guy alone?No I cannot. Let me spell it out for you: this gui brings nothing new to the plate to warrant a separate project.. and on the other end he just has to look at my source code to implement features. If it were in the commercial world.. fine, everybody brings the price to the table. But in the free world, I consider it common courtesy to not compete just for competition's sake but only if you can bring something significantly new or other. this gui is just picking cherries out of megui (x264 is the most used mode) and I find that intolerable, in fact I find any "me too" product intolerable, especially if you can just basically write off from someplace else (note that I'm not saying copying.. that would be a GPL violation and I have no reason to suspect that). I would never have started MeGUI if there already was another tool for the task. It reminds me of a few years ago when everybody wanted to have ripping site, and they basically picked out the cherries from my guides.. suddenly everybody had a Nandub guide.. guess where they get the info about all the options from?

[Koti]

I consider it common courtesy to not compete just for competition's sake but only if you can bring something significantly new or other
I think he has brought something different - a stripped down x264 only gui - I doubt or I dont feel he is competing with you but offering the world a choice.

If we take the idea like you put it no one else should develop open source codec or application for any tool that exists allready.

All he has done was release a tool that some of us like and you have done your best to discourage him time and time again yet you and this forum talk of wanting more programmers ? :confused: :confused: :confused:

How does this approach help others that would wish to post or develop a new tool ? :confused: :confused: :confused:

@doom9 I understand you have worked long and hard on me-gui and its a nice application :) , but freedom is about choices isnt it ???

[niamh]

this gui is just picking cherries out of megui (x264 is the most used mode) and I find that intolerable, in fact I find any "me too" product intolerable, especially if you can just basically write off from someplace else
That's close to slander, unless you've proved this is what is happening, in which case I will stand corrected. I don't find it very fair either that you take this in public instead of taking it privately with jeryll, who's only being helpful and generous of his time, no matter what you seem to think of him.

As we're well aware, this is your site, so why not close the damn thread for good then, and be done with it? You will win in the end anyway. Obviously this GUI is what a lot of people have been looking for (see number of views). Do the guys of Gordian Knot try to stop the development of bitrate calculators? Because they were there first? Bah. I'm sure your points are valid, but why do you manage to only sound jealous? You apparently haven't convinced anybody on this thread of anything at all yet, except that you're most definitely The Boss, and that, of course, is the most powerful of arguments :(

[Sharktooth]

Ok guys, let's calm down.
Doom9 has valid reasons to complain, but as many ppl say a x264 exclusive gui, not based on mencoder, is quite usefull (compiling mencoder with the lastest libs and x264 is quite annoying and not everyone is able to compile the sources without knowing how to do it...) expecially coz you only need the cli and the gui.
Well, MeGUI is a "all in one solution" and it's quite powerfull, it's definatly the "ultimate" backup tool with full x264 support, but the users looking for a simple x264 CLI gui will use the jeryll proggy coz it has its own place and it's made for doing 1 thing only: being a x264 cli gui.

[Doom9]

How does this approach help others that would wish to post or develop a new tool ?Simple as that: you got something really new that goes beyond existing stuff.. you release it.. if not.. you keep it to yourself until that point where it does surpass existing offers. Or, even better, you help out the existing project.. especially when it's not only free but open source. The day somebody starts a .NET based Recode alternative (built around x264 and XviD) I'll be happy to join in. I've never cared much about just being there.. this forum isn't here to just be another forum to discuss digital video.. it's all about going beyond that. It is a valid learning experience to redo what others have done, but when it comes to make it public, you gotta ask yourself if your time wouldn't be better spent helping an existing project if it's written in a language you understand. And in case you haven't realized it yet: This gui and MeGUI are written in the same language, and I have repeatedly asked him to join me into creating an even better software.

I don't expect you to understand if you've never even been close to the same position I'm in.. but I know it for a fact that I'm not the only one writing software on this board (and it's not some minor application either.. ) feels the same way about yet another application. I'm just the one not sitting on my mouth this time.

If we take the idea like you put it no one else should develop open source codec or application for any tool that exists allready.You obviously haven't understood a word I said.. try reading again, especially the parts about brining stuff to the table.

Or let me put it another way.. is XviD just another MPEG-4 ASP codec? Is x264 just another AVC codec? Obviously not.. they're leaders in their domain and that's what it's really about. Would you rather have seen 10 codecs that are less than mediocre or one that beats them all? You got the latter because everybody pulled on the same rope. There are tons of other examples in the software world where this applies. Linux is a major collaborative effort, we have Firefox, OpenOffice, etc. And if we leave the software world you have this forum being what it is because thousands upon thousands of people pull together and help each other to make this a better place.. if each ran his own forum, we'd never see anything like it.

[leowai]

.... Or, even better, you help out the existing project.. especially when it's not only free but open source.
... It is a valid learning experience to redo what others have done, but when it comes to make it public, you gotta ask yourself if your time wouldn't be better spent helping an existing project if it's written in a language you understand. And in case you haven't realized it yet: This gui and MeGUI are written in the same language, and I have repeatedly asked him to join me into creating an even better software.
I believe Doom9's intention is more on trying to joint the force into the development of the MeGUI rather than asking the author stop developing a similar GUI program. Since both program are written in the same language, it's rather "waste" of time on this GUI with no extra features compared to MeGUI.

May be the author himself feel to be too new to the programing and dare not to join Doom9's MeGUI development?

[Koti]

doom9 : I see/understand your point. Yes it would be nice if he helped , but everyone has thier own visions and some prefer to pursue them alone or in a different direction. I just dont feel anyone should be discouraged or forced to work on something else because of this :)

I still feel that this application did bring something to the table that was quite different than any other ( my opinion )

Thx doom9 for your forum :)
Thx jeryll for your gui :)

Thx Newcastle for your beer :D :D

[stax76]

maybe I'm missing something but I don't see how doing something that has already been done should be a problem. Doom9 said however several times that MeGUI or MeGUI souce code was useful for the development of jeryll's application and jeryll didn't even made a attempt to deny this. I don't know if it's true since I'm not involved in x264 yet but I feel sorry for people writing closed source and cannot do without taking benefit by open source applications. It happend to me regarding my applications several times and it sucks pretty much.

[Sharktooth]

sources are available on demand... (read the first post)

[jeryll]

ok I'm back from my 1 week long work/vacation trip in Austria ...
so for now I start bugfixing ...

thanks to all who post here infos about bugs in gui ...
thanks to all who support me and like this gui ...
thanks to all who write here their feelings about gui (bad or good) ...

(probably) everyone here (or at least I) like possibility be in a position to choose ...

choice A) if you don't like (in any way) this gui - please DON'T USE IT!
choice B) otherwise - do whatever you want to do (OF COURSE YOU MAY USE THIS GUI as long as you want to)!

maybe I'm bad guy for someone, but I don't worry much about this...

1. I'm not original enough with developing this gui?
(maybe - who knows (definition of originality is very complicated thing - so please don't post here your point of view at it - milion people = milion views, thoughts) - I find for myself this gui very usefull, so I use it)

2. I'm bad because I give this gui to community here to use?
(I'm not forcing anyone to "you must use this gui ... otherwise ... bububu ... something")

3. I'm bad because I don't want to contribute in MEGUI development and I'm .NET programmer?
(this is my choice/decision, so please respect it (I'm home programmer-beginner (self-educated), and I don't have enoughs skills/time for this type of project))

If you three time answered "YES" on questions 1,2,3 above - have a nice day and don't use this gui ... that is all ...

I still want develop this gui (I have time for this now), but please ask here for features that are primary aimed for testing purposes of x264...

Sorry if I don't reply to every single post in this threads ... I dont have time for this ...

For everyone ... english is not my native language ... so be merciful to me ... thank you ...

[MatMaul]

I think a possibility of a generation of a .bat file is good, like in the other gui of x264 (x264gui.exe). It's for persons who want add another command line(for besweet for example) for a night encoding for example.(I like use a bat for launch all my encode programs for encode a film).
Do you have seen my last post?(bug when you charged a profile with "all" ticked)

PS : thinks for the sources :D

[Doom9]

I think a possibility of a generation of a .bat file is good, like in the other gui of x264 (x264gui.exe). It's for persons who want add another command line(for besweet for example) for a night encoding for example.(I like use a bat for launch all my encode programs for encode a film).MeGUI does both video and audio encoding (using beSweet) ;) Or you can copy commandlines out from a codec configuration screen if you prefer that.. or edit commandlines in job files, etc.

[Sharktooth]

again on the 8x8dct thing... when deselecting 8x8dct the i8x8 option should be "grayed" and when selecting 8x8dct the i8x8 option should be "ungrayed". Not vice versa. 8x8dct does not imply the use of i8x8... so once "ungrayed" i8x8 should be de/selectable.
Also the fast 1st pass thing is confusing... you already have the options for speeding up the first pass in "Zones + Other" in a3p and a2p. Could you manage to re-use them even for manual modes?

[JoeBG]

I think a possibility of a generation of a .bat file is good, like in the other gui of x264 (x264gui.exe). It's for persons who want add another command line(for besweet for example) for a night encoding for example.(I like use a bat for launch all my encode programs for encode a film).
Do you have seen my last post?(bug when you charged a profile with "all" ticked)

PS : thinks for the sources :D

Don´t makes sense for a x264gui. If you want jeryll to go to a complete conversion programm, the work is still done with MeGUI.

Features to make things different from MeGUI makes sense. So why not?

[MatMaul]

ok.at least, I can copy the generated command line in a bat file, I loss just 3 seconds... :D

[Doom9]

by the way.. what other jobs are you running besides x264? I'm wondering because I think MeGUI covers MP4 creation pretty well. You have audio creation and muxing as well, as well as support for subs and the likes.

[jeryll]

again on the 8x8dct thing... when deselecting 8x8dct the i8x8 option should be "grayed" and when selecting 8x8dct the i8x8 option should be "ungrayed". Not vice versa. 8x8dct does not imply the use of i8x8... so once "ungrayed" i8x8 should be de/selectable.
Done.
Also the fast 1st pass thing is confusing... you already have the options for speeding up the first pass in "Zones + Other" in a3p and a2p. Could you manage to re-use them even for manual modes?
cheburashka will have added fast 1st pass to profile (for me is this thing usefull sometimes too) ... there is a little difference between
fast 1st pass
(here is for speedup in first pass used automated reduction routine as suggested by akupenguin here (http://forum.doom9.org/showthread.php?p=595200#post595200) )
and between
fast 1st pass settings for a2p,a3p modes
(here you must adjust wanted speedup settings for 1st pass in a2p,a3p modes manually)

I'm looking for solution for this (I probably add something like "1F pass ABR" into encoding modes and remove "fast 1 pass" checkbox, so it will be not so confusing, I think ;) )

[jeryll]

when I tick "all" in analyse all other analyse's options are grey.
but when I load a profile with "all" ticked, all other analyse's options aren't grey.
I have no problem with none case.
I'm currently looking what's wrong ... fixed

[MatMaul]

thanks ! for doom9: I prefer the mkv container (because support default track : I think it's a good feature (for forced subtitles for example) and the mp4 container doesn't support default tracks at this time( or I don't see this...)).for MeGUI the subtitle's support is a good think.

[Doom9]

I prefer the mkv containerI see. I might support MKV in the future.. North101 designed the GUI for that output type.. I replaced MKV with AVI for now because I can do that with the tools I already support. My biggest issue is that mkvmerge wants an mp4 or avi with avc.

[jeryll]

Bug in 0.1.71 b:

- Select "use speedups for 1st pass in a2p, a3p". (Please write numerations!)
- Do not check any macroblock partitions, neither check "all" or "none".

=> The generated 1st pass command line contains "... --analyse --...". This makes x264 exit immediately.
fixed

[MatMaul]

I see. I might support MKV in the future.. North101 designed the GUI for that output type.. I replaced MKV with AVI for now because I can do that with the tools I already support. My biggest issue is that mkvmerge wants an mp4 or avi with avc.

Great!

[Mosu]

My biggest issue is that mkvmerge wants an mp4 or avi with avc.

What exactly would you prefer? Elementary stream support?

[Doom9]

What exactly would you prefer?The option to use a raw stream. Using AVI isn't such a great idea to begin with, and most tools don't have native output.. so you end up needing a tool that handles the avi hacks and imports the whole thing (I suppose mkvmerge does this just as mp4box does it), or you do it raw, then mux to mp4, and if you want mkv output, mux it again, which is quite a tedious process.

And P.S. I do not find MP4 containing video listed as allowable input on the mkmerge man page..

[Mosu]

The option to use a raw stream.

The problem is always writing a ES parser... Because e.g. mpeg4ip is licensed under the Mozilla Public License which is incompatible with the GPL mkvmerge is licensed under, so I cannot even use their code to start with. And ffmpeg's code is not exactly an example of easy-to-reuse code.

Which does not mean that I won't do it.

Using AVI isn't such a great idea to begin with, and most tools don't have native output.

Just FYI: mkvmerge does not support reading AVC from AVIs. Only from MP4 files at the moment.

so you end up needing a tool that handles the avi hacks and imports the whole thing (I suppose mkvmerge does this just as mp4box does it), or you do it raw, then mux to mp4, and if you want mkv output, mux it again, which is quite a tedious process.

True, no doubt.

And P.S. I do not find MP4 containing video listed as allowable input on the mkmerge man page..

Yes, it's outdated ;)

[Doom9]

Just FYI: mkvmerge does not support reading AVC from AVIs. Only from MP4 files at the moment.hmm.. I thought there was this VfW compatibility mode. But I must admit I'm really not following Matroska's progress, and I've merely started using MP4 because AVI does have some issues when it comes to using the full featureset AVC video offers.

[Mosu]

hmm.. I thought there was this VfW compatibility mode. But I must admit I'm really not following Matroska's progress, and I've merely started using MP4 because AVI does have some issues when it comes to using the full featureset AVC video offers.

That is true, and I've heard that it does indeed work, but I don't support this officially, and neither can mkvmerge convert such a file into what we call "native storage".

[jeryll]

thanks to all for comments
new version released ... see first post for changelog or download it
http://mirror05.x264.nl/jeryll/x264CLIgui_0_1_8b.zip

[Sharktooth]

suggestions:
save log button in Log window (export in xml format indexed by job or in regular txt).
add custom command line textbox (to be able to use future and maybe still unsupported options) so if "--foo xyz" is manually added in that box the commandline will look like "x264.exe current options and flags set by the GUI --foo xyz".
If you prefer you can made the command line manually editable instead and dont care of the previous suggestion.

[dimzon]

I have found a bug running such GUI on Russian Regional Settings (this locale use 'comma' instead of 'dot' for floating point formatting). I made some reverse-enginering for latest binary and perform such modifications:
public static void Main(string[] args)
{
Application.CurrentCulture = CultureInfo.InvariantCulture;
Application.Run(new MainForm());
}


Enjoy!

[Doom9]

actually, as an MCP, you should've noted that using the invariant culture is not a good culture to use for anything that is not kept internally and never sees a GUI. I suppose this GUI has decimal numericupdown elements since certain parameters are floats, so using the invariant culture causes UI mismatches with the locale of your PC.
My own app, MeGUI, correctly handles this for all locales (after some initial problems I must admit, but having learned the hard way it's unlikely I'll forget again).

[dimzon]

actually, as an MCP, you should've noted that using the invariant culture is not a good culture to use for anything that is not kept internally and never sees a GUI. I suppose this GUI has decimal numericupdown elements since certain parameters are floats, so using the invariant culture causes UI mismatches with the locale of your PC.
My own app, MeGUI, correctly handles this for all locales (after some initial problems I must admit, but having learned the hard way it's unlikely I'll forget again).
Of couse right way is to change Float.ToString() to Float.ToString(IFormatProvider) calls in command line creation subrotune. Unfortunally I am not this GUI developer and I have not enought time to lean and debug decompiled undocumented source code. So this quick patch (hack) is temporal (but working) solution :)

[Doom9]

So this quick patch (hack) is temporal (but working) solution
there's also an other option of course: http://forum.doom9.org/showthread.php?t=98032
that one is open source so you won't have to bother to decompile ;)

[Sharktooth]

...
BETA state ...
source available on demand
(just send me PM with email and I sent it to you - but I warn you - this code is uncommented (and badly written - so no learn from it :devil: ))...
well...

[dimzon]

there's also an other option of course: http://forum.doom9.org/showthread.php?t=98032
that one is open source so you won't have to bother to decompile ;)
Unfortunally
Avisynth 2.55 for video frameserving. Beta versions are NOT!!! supported
:mad:
Using fresh beta is my religion :)