They are explained in the H.264 guide.įfmpeg -i input -c:v libx265 -crf 26 -preset fast -c:a aac -b:a 128k output.mp4 x265 supports the following -tune options: psnr, ssim, grain, zerolatency, fastdecode. By default, this is disabled, and it is generally not required to set a tune option. Ignore placebo as it provides insignificant returns for a significant increase in encoding time. Use the slowest preset you have patience for. Valid presets are ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow, and placebo. The preset determines compression efficiency and therefore affects encoding speed. CRF works just like in x264, so choose the highest value that provides an acceptable quality. The default is 28, and it should visually correspond to libx264 video at CRF 23, but result in about half the file size. The mode works exactly the same as in x264, except that maximum value is always 51, even with 10-bit support, so please read the H.264 guide for more info.Īs with x264, you need to make several choices: Use this mode if you want to retain good visual quality and don't care about the exact bitrate or filesize of the encoded file. In this guide we are going to focus on CRF and Two-Pass encoding, as 1-pass target bitrate encoding is not recommended.
The Compilation Guides show you how to do that. See HWAccelIntro for information on supported hardware H.265/HEVC encoders.įfmpeg needs to be built with the -enable-gpl -enable-libx265 configuration flags and requires x265 to be installed on your system. These gains will be most pronounced at resolutions of 1080p and higher. This guide focuses on the encoder libx265 which can offer around 25–50% bitrate savings compared to H.264 video encoded with libx264, while retaining the same visual quality. Final Cut and Apple stuff compatibility.xeon would be easier to handle and purchase without having to pull together pieces here and there but does NOT come with iGPU or hardware codec support, but having 28 threads would definitely allow me to splice the job in multiple parallel executions. I didn't want to spend more than $1000 total (including chassis/ram etc) in this case that's why the older generations, but I'm stuck because. I'm currently trying to buy a server machine that could handle more load and I'm stuck between i7-i9 with higher cores or xeon, in particular E5-2697 v3 because of the higher core.
I mostly do encoding from higher resolutions of movies/series for myself to either small 360p for cartoons/slow moving TV series or 1080p maybe 2700/3300kbps for higher resolution movies, all in h264 for maximum compatibility.
0 kommentar(er)
