supported pixel formats

[bmegli]

Kaby Lake, H264

[AVHWDeviceContext @ 0x55c82d8b37e0] Opened VA display via DRM device /dev/dri/renderD128.
[AVHWDeviceContext @ 0x55c82d8b37e0] libva: VA-API version 1.1.0
[AVHWDeviceContext @ 0x55c82d8b37e0] libva: va_getDriverName() returns 0
[AVHWDeviceContext @ 0x55c82d8b37e0] libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
[AVHWDeviceContext @ 0x55c82d8b37e0] libva: Found init function __vaDriverInit_1_1
[AVHWDeviceContext @ 0x55c82d8b37e0] libva: va_openDriver() returns 0
[AVHWDeviceContext @ 0x55c82d8b37e0] Initialised VAAPI connection: version 1.1
[AVHWDeviceContext @ 0x55c82d8b37e0] Matched "Intel i965 driver for Intel(R) Kaby Lake - 2.1.0" as known driver "Intel i965 (Quick Sync)".
25 : nv12
0 : yuv420p
1 : yuyv422
17 : uyvy422
4 : yuv422p
296 : rgb0
298 : bgr0
335 : p010le

[bmegli]

The interesting one is p010le:

FFmpeg notes:

AV_PIX_FMT_P010LE	like NV12, with 10bpp per component, data in the high bits, zeros in the low bits, little-endian

Microsoft notes:

• fixed point representation
• stored in 16 bit LE WORDs, 6 lowest bits set to 0
• P010LE is FOURCC code (planar, 4:2:0, 10-bit, little endian):
  • P for planar
  • 0 for 4:2:0
  • 10 for 10 bits per channel
  • LE for little endian

So this should be like NV12:

• Y plane, 16 bit words with 10 bit data, height H and stride S
• followed by interleaved UV plane, height H/2, stride S

Intel forum notes (to check):

• claims that there is no 6 bit shift in software and is in hardware
• claims interleaved/non interleaved U/V problem