This turns out to be a bug in the Intel driver when running on Apollo Lake hardware. You can follow the issue thread here; we’ll update the driver in PMS once it’s fixed: https://github.com/intel/intel-vaapi-driver/issues/398
This turns out to be a bug in the Intel driver when running on Apollo Lake hardware. You can follow the issue thread here; we’ll update the driver in PMS once it’s fixed: https://github.com/intel/intel-vaapi-driver/issues/398