Just 2 ffmpeg's x264 presets in git?

Linux howto's, compile information, information on whatever we learned on working with linux, MACOs and - of course - Products of the big evil....
Post Reply
User avatar
^rooker
Site Admin
Posts: 1483
Joined: Fri Aug 29, 2003 8:39 pm

Just 2 ffmpeg's x264 presets in git?

Post by ^rooker »

[PROBLEM]
I wanted to encode files in h264, but all the tutorials I found referenced to ffmpeg presets which, for some yet unknown reason, I didn't seem to have:

Code: Select all

[libx264 @ 0x2b463a0] Error setting preset/tune baseline/(null).
...
Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
The ffmpeg version I was using was pulled from git and compiled manually. Since I only compiled it, but hadn't installed it, I suspected path issues to be a problem.


[SOLUTION]
If only I had read ffmpeg's output more thoroughly. It already told me about which x264-presets it could offer. Right after the above shown error message were the following lines:

Code: Select all

[libx264 @ 0x2b463a0] Possible presets: ultrafast superfast veryfast faster fast medium slow slower veryslow placebo
[libx264 @ 0x2b463a0] Possible tunes: film animation grain stillimage psnr ssim fastdecode zerolatency
I was a bit puzzled, because I couldn't find the corresponding preset-files anywhere on my system. As user "LordNeckbeard" explained in an answer on stackoverflow.com, the reason for that is that is that...
FFmpeg now accesses the x264 internal presets instead of using text files to emulate them. This is easier to maintain and use.
That's it.
Just use one of the presets that ffmpeg is offering you and it works :)

PS: I'm still not quite sure if ffmpeg would actually find its preset-files on my system if I wanted to use file-based presets :?
Jumping out of an airplane is not a basic instinct. Neither is breathing underwater. But put the two together and you're traveling through space!
Post Reply