Log in

View Full Version : Newbie needs help with x264 string


ronny85
19th September 2013, 13:12
I am trying

x264 fast_pskip 0 --ref 5 --merange 24 --threads 8 --lookahead-threads 2 --keyint 240 --rc-lookahead 60 --bitrate 1997 --qpmin 0 --qpmax 69 --cabac 1 --deblock -1:-1 --ipratio 1.40 --aq-mode 1 --aq-strength 1.00 --partitions 0x3:0x133 --me umh --subme 9 --psy 1 --psy-rd 1.00:0.15 --mixed-ref 1 --no-chroma-me 1 --trellis 2 --8x8dct 1 --cqm 0 -–deadzone-inter 21 -–deadzone-intr 11 --chroma-qp-offset -3 --sliced-threads 0 --nr 0 --no-dct-decimate 1 --interlaced 0 --constrained-intra 0 --bframes 3 --b-pyramid 2 --b-adapt 2 --b-bias 0 --direct 3 --weightb 1 --open-gop 0 --weightp 2 --min-keyint 23 --scenecut 40 --intra-refresh 0 --rc 2pass --mbtree 1 --ratetol 1.0 --qcomp 0.60 --qpstep 4 --cplxblur 20.0 --qblur 0.5 -o video.mkv video.h264


But it answer
x264: invalid option -- ?

What is wrong?

Guest
19th September 2013, 13:28
Can't you read the error message(s) and fix things based on that? You'll have to learn all this at some point, it's not difficult.

For example, your first option is fast_pskip. The error message points you to that, then you look at the help and see it should be --fast-pskip.

There are other errors, see if you can find and fix them using the error output together with the help, fixing one thing at a time. You can view the help with

x264 --fullhelp

raffriff42
19th September 2013, 13:31
> -–deadzone-inter 21 -–deadzone-intr 11
Don't use a word processor to write command lines ;)

Guest
19th September 2013, 13:35
Well, if we are going to spoonfeed him... :)

--lookahead-threads 2

...appears bogus.

raffriff42
19th September 2013, 14:02
Of course I agree w/ your advice to fix one thing at a time, but those flaws jumped out at me :)

ronny85
19th September 2013, 14:32
Sorry I am posting with my smartphone

Corrected
x264 --fast-pskip 0 --ref 5 --merange 4 --threads 8 --keynt 24 --rc-lookahead 60 --bitrate 1997 --qpmin 0 --qpmax 69 --cabac 1 --deblock -1:-1 --ipratio 1.40 --aq-mode 1 --aq-strength 1.00 --partitions 0x3:0x133 --me umh --subme 9 --psy 1 --psy-rd 1.00:0.15 --mixed-ref 1 --no-chroma-me 1 --trellis 2 --8x8dct 1 --cqm 0 --deadzone-inter 21 --deadzone-intr 11 --chroma-qp-offset -3 --sliced-threads 0 --nr 0 --no-dct-decimate 1 --interlaced 0 --constrained-intra 0 --bframes 3 --b-pyramid 2 --b-adapt 2 --b-bias 0 --direct 3 --weightb 1 --open-gop 0 --weightp 2 --min-keyint 23 --scenecut 40 --intra-refresh 0 --rc 2pass --mbtree 1 --ratetol 1.0 --qcomp 0.60 --qpstep 4 --cplxblur 20.0 --qblur 0.5 -o video.mkv video.h264

But still --? Error :/

poisondeathray
19th September 2013, 14:40
keynt should be keyint
deadzone-intr should be deadzone-intra

Groucho2004
19th September 2013, 14:47
"--fast-pskip" shouldn't have a value.
"--mbtree 1" - WTF?
"--direct 3" - more WTF.

This is getting ridiculous. Stop posting this nonsense and RTFM.

ronny85
19th September 2013, 15:12
That string is from internet and is not easy to get the sense of "direct" from --help.

So forums should be a good way to ask for some help instead of a scolding.

Chill out.

Groucho2004
19th September 2013, 15:27
That string is from internet
No idea what that means.

is not easy to get the sense of "direct" from --help.
"--fullhelp" gives you all available command line options. You don't need a "sense", you need to understand what they do.

You're just throwing crap at the wall hoping something will stick.

Guest
19th September 2013, 15:41
Just use presets and defaults until you understand what you are doing. Hacking at options like this without knowing what they do is highly likely to give you worse results than simply using the defaults.

And this:

"But still --? Error :/"

What was the error, specifically?

detmek
19th September 2013, 19:50
No idea what that means.



That means somebody somewhere posted that command line and he blindly tries to copy-paste it.

@ronny85 Do as neuron2 said. Start with --preset slow --tune film

mandarinka
19th September 2013, 20:16
Yes, don't use that commandline at all. First, it probably uses questionable values. Second, it is full of errors.

For example: -o video.mkv video.h264
If your input is video.mkv, output has to be video.h264 (I don't think x264 will read raw files). If that is the case, the order should be video.mkv -o video.264. The -o parameter is there to tell the program which of the two filenames is output. Take care, because if the file exists, x264 will immediately overwrite it.

--direct 3 is incorrect, that is the internal value or something which doesn't work as a parameter, use --direct auto
--no-dct-decimate 1 also doesn't use arguments... remove that thing from your commandline (--no-dct-decimate actually disables the thing IIRC)
--interlaced 0 - just remove that compeltely if you don't want to use interlacing. (BTW, that goes for most options you use heheh).
--rc 2pass Totally wrong. The syntax is --pass 1 and --pass 2

Did you use a commandline from ffmpeg or what?


Etc etc... just abandon that stuff and start with a sane base, the above posters are right with that advice. If you plan to fiddle with the options apart from presets, I would say you should start with a gui that generates them for you. Six years ago, megui was a good program for generating command lines, IIRC it is still actively maintained?

the_weirdo
19th September 2013, 20:21
There're a lot of nonexistent parameters in that command line, like "fast_pskip 0", "--cabac 1", "--partitions 0x3:0x133", "--mixed-ref 1", "--no-chroma-me 1", "--8x8dct 1", "--no-dct-decimate 1", "--sliced-threads 0"...
Looks like someone has tried converting "Encoding settings" from MediaInfo to x264 command line.

ronny85
20th September 2013, 09:47
Well I figured out how to solve my problem and converted almost all of my crappy from mediainfo.

Thank you!