intel quick sync for jpeg encode acceleration

[Antoine Martin]

​Intel Quick Sync Video supports JPEG encode acceleration on Braswell and later. (2016)

JPEG is critical to the performance, especially for the HTML5 client. Let's see if this beats ​libjpeg-turbo.

Chrome uses it: ​Chrome Working On JPEG Encode Accelerator With VA-API/V4L2 Support, so that's likely to be a win.

[Antoine Martin]

Re-scheduling as per ticket:451#comment:10.

[Antoine Martin]

​https://trac.ffmpeg.org/wiki/Hardware/QuickSync

Not many examples around:

• ​How to reduce the latency of FFmpeg h264_qsv encoder?
• ​qsvdec.c
• ​qsvenc.c

[Antoine Martin]

qsv via ffmpeg - no workee :(

[Antoine Martin]

Even trying the ffmpeg qsv command line examples fails.

Probably requires that I unplug or turn off the nvidia card and switch back to the intel iGPU. (Intel® HD Graphics 530 found in the ​i6700k)

libva (#451) might be a better option: it is more generic, supports amd and nvidia too, and this does look like it might work without touching the hardware:

$ vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_1_5
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.7.1)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG4Simple            :	VAEntrypointVLD
      VAProfileMPEG4AdvancedSimple    :	VAEntrypointVLD
      <unknown profile>               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD

[Antoine Martin]

It is nonfree and doesn't work, whereas vaapi does: #451.

[migration script]

this ticket has been moved to: ​https://github.com/Xpra-org/xpra/issues/1666