Error at x264.exe

[Eastermeyer]

Hi !

What's wrong here ?

.\x264.exe --keyint 240 --min-keyint 24 --bframes 4 --b-pyramid --ref 6 --deblock -2:-2 --bitrate 12598 --qpmax 42 --pass 1 --partitions "all" --direct auto --weightb --subme 7 --merange 32 --b-rdo --mixed-refs --bime --8x8dct --trellis 1 --no-fast-pskip --no-dct-decimate --cqmfile ".\prestige.cfg" --sar 6:4 -videoformat ntsc --fullrange "on" --fps 24000/1001 --threads auto --non-deterministic --thread-input --no-psnr --no-ssim --progress --output NUL E:\capture\wedding.avs

x264 [error]: invalid argument: min-keyint = deoformat

[Sharktooth]

what x264 revision? was it built straigth from the SVN or patched source?
also what program generated that commandline? it's full of useless stuff... and some options where maxed out in a nonsense way...

[Eastermeyer]

x264 core:57 svn-712 from x264.nl

That commandline was created by Brain 1.0 ;) according to Selurs man.

[akupenguin]

Your commandline is wrong. I won't say exactly how, except that x264 supports option abbreviation and bundling like any good unix app.

[Guest]

-videoformat -> --videoformat

[Sharktooth]

ushhh dont tell him...:p

[Eastermeyer]

Thank you, neuron2.

What's wrong ?

This material is important for me, and because of that i would like to use the maxed out settings for maxed out quality.

So, what's wrong with the options ? Is there one, which doesn't fit to the others ?

[Dark Shikari]

Thank you, neuron2.

What's wrong ?

This material is important for me, and because of that i would like to use the maxed out settings for maxed out quality.

So, what's wrong with the options ? Is there one, which doesn't fit to the others ?First pass doesn't need strong settings... only second pass does, for one.

[Sharktooth]

still confusion about quality and compression...
maxed out settings = max compression and often maximized measured quality.
the measured quality is different from perceived quality though. so i wont say maxed out settings = maxed out quality. there is always a sweet spot between compression and desired quality and it usually is subjective.
for example i dont like subme 6 and 7, brdo and few other settings coz they tend to "flatten" the picture, while i like grain, film defects, rough details, etc...so i use lower subme values

[Dark Shikari]

the measured quality is different from perceived quality though. so i wont say maxed out settings = maxed out quality. there is always a sweet spot between compression and desired quality and it usually is subjective.
for example i dont like subme 6 and 7, brdo and few other settings coz they tend to "flatten" the picture, while i like grain, film defects, rough details, etc...so i use lower subme valuesNote however that Sharktooth seems to be the only one who encounters this issue, since I have never measured much of any significant case in which higher compression settings "decrease visual quality" with the exception of --trellis 2.

(Note that this statement will fail with some extreme CQMs though)

[Sharktooth]

try encoding GrindHouse (one of the two movies, deathproof or planet terror) with subme 6 or higher...
after encoding, compare it with the source pictures and look at the grain and defects. most of them are "gone" even if you rise the bitrate (or use a very low quantizer) and lower the deadzones