Ilya87

@waterflag0614 Send please the yuv file (ore the original one) to the mega.nz service.

@waterflag0614 Seems to me your sample isn't valid. 1 - It looks damaged (see encoded file in the link below) 2 - Your sample is semi-planar NV12 https://wiki.videolan.org/YUV#NV12, NOT yuv420p...

@waterflag0614 mobile-8bit-yuv420p-720p.yuv is yuv420p If you are not shure, use yuvplayer (https://sourceforge.net/projects/raw-yuvplayer/), please. It allows you to select colorspace, resolution, etc. Now your example looks good to me. 288 frames...

@waterflag0614 the solution is found - change the lad parameter as it is recommended in User Guide "When RateControlMode is set to 1 it's best to set this parameter to...

@waterflag0614 Yes, it is normal if developers implemented such prediction model for bitrate.

@waterflag0614 Quatation from the x265 cli: The longer the lookahead buffer the more accurate scenecut decisions will be, and the more effective cuTree will be at improving adaptive quant. Having...

«when the same command line is executed, the value of real bit rate is different each time.» 1 – When run on the same yuv file? If yes, it' s...

@1480c1 ? is a typo (corrected in post), comma should be used. And not, when you'll see screenshots fullscreen using 24" monitor artifacts are clearly seen, moreover this screenshots are...

@tianjunwork, yes, I'm sorry - at this bitrate x264 also provides comparable banding artifacts, BUT at comparable bitrate x264 is better x264 veryslow_qp15_bitrate_3549 https://yadi.sk/i/uBj5eDI_m7-Pcw SVT-HEVC -q12 result bitrate is 3108...

Almost doubled bitrate - same artifacts.