<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
After finishing the three hevc_qsv presets for _8b420, _10b420 and
_10b422 mp4<br>
<a class="moz-txt-link-freetext" href="https://lists.cinelerra-gg.org/pipermail/cin/2024-November/009039.html">https://lists.cinelerra-gg.org/pipermail/cin/2024-November/009039.html</a><br>
<br>
I thought to do the corresponding for hevc_vaapi<br>
<br>
However I am struggling to get 10bit 422 output rendered from Cingg,
which so far falls back to 10bit 420 chroma subsampling<br>
<br>
<font face="Courier New, Courier, monospace">fprobe -hide_banner
hd01_hevc_vaapi_10b422.mp4<br>
Duration: 00:01:11.20, start: 0.000000, bitrate: 11082 kb/s<br>
Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 /
0x31766568), yuv420p10le(tv, bt709/unknown/unknown, top coded
first (swapped)), 1920x1080 [SAR 1:1 DAR 16:9], 11080 kb/s, 25
fps, 25 tbr, 12800 tbn (default)<br>
<br>
<br>
In a previous thread I proved that ffmpeg hevc_vaapi encoding has
this 10bit-422 capability<br>
3) 10-bit yuv422p10le hevc_vaapi encoding using -vf
'format=y210,hwupload'<br>
<a class="moz-txt-link-freetext" href="https://lists.cinelerra-gg.org/pipermail/cin/2024-November/008982.html">https://lists.cinelerra-gg.org/pipermail/cin/2024-November/008982.html</a><br>
<br>
<br>
And yes, there was also issues before hevc_qsv_10b422.mp4
combinations Pixel format/profile finally succeeded.<br>
But here are some differences, yet. While hevc_qsv provided a
Pixels drop down menu with pixel formats,<br>
hevc_vaapi just has a single "vaapi" pixel format.<br>
<br>
Any idea why, and what can fulfill the vaapi 10bit 422 encoding
here?<br>
<br>
<br>
<br>
<br>
</font>
</body>
</html>