Log in

View Full Version : .NET(1.1) based x264CLI GUI

Pages : [1] 2 3
jeryll
4th June 2005, 22:42
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
8th June 2005, 17:59
yet another gui for x264cli, looks nice :)
Sharktooth
8th June 2005, 18:06
Yep. Really nice.
Adding the new 8x8 options would be great.
lexor
8th June 2005, 18:33
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
8th June 2005, 18:39
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
8th June 2005, 18:41
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
8th June 2005, 18:48
... 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
9th June 2005, 06:28
thanks to all for comments
new version released ... see first post
Sharktooth
9th June 2005, 09:15
another suggestion. When ALL partitions checkboxes are enabled, instead of "--analyse p4x4,p8x8,etc..." you can use "--analyse all".
eqbal
9th June 2005, 09:42
i can't download it... :(
Sharktooth
9th June 2005, 09:44
it needs an approval by a moderator
yaz
9th June 2005, 09:47
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
9th June 2005, 20:12
Ok, it has been approved:)
peteag
9th June 2005, 20:51
status-line could be great!
Sharktooth
9th June 2005, 20:57
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
9th June 2005, 21:07
Hello jeryll, :)

You says that:

" requirements:
MS .NET Framework 1.1 "

and for MS .NET Framework 2.0 bęta 1 ?
MatMaul
9th June 2005, 21:21
hello !
it's open source ?
if it is, can you post source please ?
thanks.
jeryll
9th June 2005, 21:30
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
9th June 2005, 22:08
huuuummm!!!! :)

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

:thanks:
Sharktooth
9th June 2005, 22:31
the "beta"ness of the .net framework 2.0....
jeryll
10th June 2005, 09:10
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
10th June 2005, 09:15
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
10th June 2005, 12:44
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
10th June 2005, 13:02
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
10th June 2005, 13:08
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
10th June 2005, 14:06
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
10th June 2005, 22:29
@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
10th June 2005, 23:21
i also have to say that megui really rocks
jeryll
10th June 2005, 23:42
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
11th June 2005, 00:00
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
11th June 2005, 00:03
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
11th June 2005, 03:55
@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
11th June 2005, 05:55
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
11th June 2005, 09:20
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
11th June 2005, 13:07
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
11th June 2005, 16:33
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
12th June 2005, 21:49
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
12th June 2005, 22:41
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
12th June 2005, 22:55
@LigH
Already ahead( :devil: ) of you :sly:

@jeryll
Update your first post so LigH knows what the hell i am talking about :D
jeryll
12th June 2005, 23:41
@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
12th June 2005, 23:50
Aah - nice. (But the filename column is too small, ellipses '...' were used.)
bob0r
13th June 2005, 00:29
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
13th June 2005, 00:36
thank you :)

If you hover the mouse over the files on the link it shows the version. ( at least in firefox)
LigH
13th June 2005, 08:06
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
13th June 2005, 11:09
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
13th June 2005, 11:29
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
14th June 2005, 02:04
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
14th June 2005, 10:01
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
14th June 2005, 10:04
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
14th June 2005, 13:52
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=