Doom9's Forum - View Single Post - What is current status for hardware H.265 encoding.

Yups · 10th April 2021, 15:35

Blender Open Movie from here: https://forum.doom9.org/showpost.php...&postcount=423

Code:

    
HERO - Blender Open Movie            VMAF      speed       bitrate

Quicksync H265 (27.20.100.9316)
Iris Xe CQP FF best                  86.56     550 fps     199 kbit
Iris Xe CQP FF balanced              85.66     850 fps     201 Kbit
Iris Xe CQP FF speed                 76.25     1550 fps    200 Kbit

Iris Xe CQP best                     88.59     167 fps     200 kbit
Iris Xe CQP balanced                 87.18     280 fps     201 Kbit
Iris Xe CQP speed                    86.22     520 fps     200 Kbit


NVENC H265 (470.14)
GTX 1660S CQP best                   84.52     430 fps     200 Kbit
GTX 1660S CQP default                83.55     990 fps     201 Kbit
GTX 1660S CQP performance            79.22     1130 fps    200 Kbit


x265 (Staxrip 2.1.9.0)
i7-1165G7 CRF slower                 90.25     8 fps       200 Kbit
i7-1165G7 CRF slow                   88.18     34 fps      200 kbit
i7-1165G7 CRF medium                 85.72     56 fps      200 Kbit
i7-1165G7 CRF very fast              83.36     73 fps      200 Kbit


x264 (Staxrip 2.1.9.0)
i7-1165G7 CRF slower                 75.37     81 fps      200 Kbit

Disabled b-adapt is better for this video. Turing CQP cannot reach Iris Xe CQP quality, subjective and objective the difference is large.

Turing has two downsides, only 5 bframes versus 16 bframes on Iris Xe and there is no GPU equivalent mode which is more flexible than a fully fixed function solution, however even the FF mode from Iris Xe looks better. It might look different with CBR vs CBR which I haven't tried. That said, the H265 CQP results from Turing are really good for a hardware encoder, something like x265 fast-faster with extremely fast encoding times, the CQP quality from Iris Xe is just insane.

10th April 2021, 15:35	#451 \| Link
Yups Registered User Join Date: Sep 2011 Posts: 362	Blender Open Movie from here: https://forum.doom9.org/showpost.php...&postcount=423 Code: HERO - Blender Open Movie VMAF speed bitrate Quicksync H265 (27.20.100.9316) Iris Xe CQP FF best 86.56 550 fps 199 kbit Iris Xe CQP FF balanced 85.66 850 fps 201 Kbit Iris Xe CQP FF speed 76.25 1550 fps 200 Kbit Iris Xe CQP best 88.59 167 fps 200 kbit Iris Xe CQP balanced 87.18 280 fps 201 Kbit Iris Xe CQP speed 86.22 520 fps 200 Kbit NVENC H265 (470.14) GTX 1660S CQP best 84.52 430 fps 200 Kbit GTX 1660S CQP default 83.55 990 fps 201 Kbit GTX 1660S CQP performance 79.22 1130 fps 200 Kbit x265 (Staxrip 2.1.9.0) i7-1165G7 CRF slower 90.25 8 fps 200 Kbit i7-1165G7 CRF slow 88.18 34 fps 200 kbit i7-1165G7 CRF medium 85.72 56 fps 200 Kbit i7-1165G7 CRF very fast 83.36 73 fps 200 Kbit x264 (Staxrip 2.1.9.0) i7-1165G7 CRF slower 75.37 81 fps 200 Kbit Disabled b-adapt is better for this video. Turing CQP cannot reach Iris Xe CQP quality, subjective and objective the difference is large. Turing has two downsides, only 5 bframes versus 16 bframes on Iris Xe and there is no GPU equivalent mode which is more flexible than a fully fixed function solution, however even the FF mode from Iris Xe looks better. It might look different with CBR vs CBR which I haven't tried. That said, the H265 CQP results from Turing are really good for a hardware encoder, something like x265 fast-faster with extremely fast encoding times, the CQP quality from Iris Xe is just insane. Last edited by Yups; 10th April 2021 at 15:47.