Quote:
Originally Posted by benwaggoner
x265's default tuning is generally just fine. Using --preset slower is where the best features of HEVC generally kick in, but it'll still be a lot slower than x264 veryslow.
The Main profile of HEVC is equivalent to High in x265. Main10 would be used for 10-bit instead of High10. x265 is generally able to use more threads than x264 at a given frame size. If you are doing 1080p, you probably don't need to be running in parallel with only 12 physical cores, and can just leave it at default. Using more than you have logical cores is pointless, and probably would cause encoding to become slower overall at some point due to the extra overhead of parallelization.
By Level, do you mean Tier? A typical 1080p encode for distribution/playback would be Main Profile Level 4.0 Main Tier. High Tier is more for creating high-bitrate mezzanine files. High Tier is basically all the same constraints of Profile & Level, except allowing much higher bitrates than Main Tier. But, for the same reason, not as compatible for device decoding.
For 1080p24, 12 Mbps peak is generally quite ample with x265. 1080p50 would use a higher profile with a higher max bitrate.
|
So its worth using slower over slow? Not worth going much slower than that?
I heard that x265 was LESS parralelizable than x264? Would it not still make sense to use only 12 threads out 24 anyway? I can play games while encoding, and when im not playing, i can run a second encode. Does fewer threads not mean higher compression efficiency like with x264? If only marginal?
Yes thats what i thought, high is just another set of restraints. It wont impact quality unless i max out the main teir of whatever level im on. At first i thought it was like x264, where high is actually more efficient than main.
So leaving level unrestricted is best?