

SSIM/PSNR etc are only half good as it's very difficult to make metric which reliably represent visual perceived video quality. For web those bitrates are still problematic (to high).
/01.jpg)
Blu-ray bitrates- they allow to get very decent end user quality. In terms of final quality I'm more happy with e.g. We want to use something lower here as we doing intermediate step master. Those quoted CRF values are "chosen" by x264/5 developers, but they are for " final encode/quality". x264 and Resolve h264 encoder separately as they are not as efficient. By doing so you can find at what source bitrate you start being so close with final youtube quality against uncompressed upload that there is no point raising upload bitrate any further. You don't want to analyse bitrate in 2nd graph (youtube uses fixed profiles as far as I understand), but quality.
