[Bug 258976] multimedia/intel-media-sdk: QSV doesn't work since 21.3.1

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 07 Oct 2021 05:41:57 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258976

            Bug ID: 258976
           Summary: multimedia/intel-media-sdk: QSV doesn't work since
                    21.3.1
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: jbeich@FreeBSD.org
          Reporter: naito.yuichiro@gmail.com
          Assignee: jbeich@FreeBSD.org
             Flags: maintainer-feedback?(jbeich@FreeBSD.org)

When I use hevec_qsv encoding, ffmpeg always fails as follows.
And also multimedia/handbrake doesn't show QSV encodings on the Video encoder
menu.

```
$ ffmpeg -i /zpool/video/test.avi -vcodec hevc_qsv hevec_qsv_test.mp4

(snip)

Input #0, avi, from '/zpool/video/test.avi':
  Metadata:
    software        : Lavf58.29.100
  Duration: 00:03:45.28, start: 0.000000, bitrate: 412 kb/s
  Stream #0:0: Video: mpeg4 (Simple Profile) (FMP4 / 0x34504D46), yuv420p,
312x232 [SAR 1:1 DAR 39:29], 208 kb/s, 29.97 fps, 29.97 tbr, 29.97 tbn, 30k tbc
  Stream #0:1: Audio: ac3 ([0] [0][0] / 0x2000), 44100 Hz, stereo, fltp, 192
kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (mpeg4 (native) -> hevc (hevc_qsv))
  Stream #0:1 -> #0:1 (ac3 (native) -> aac (native))
Press [q] to stop, [?] for help
[hevc_qsv @ 0x806a75e00] Error initializing an internal MFX session:
unsupported (-3)
Error initializing output stream 0:0 -- Error while opening encoder for output
stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or
height
[aac @ 0x806a76d00] Qavg: 2305.336
[aac @ 0x806a76d00] 2 frames left in the queue on closing
Conversion failed!
```

If I downgrade intel-media-sdk to 21.3.0, it works as I expected.

It seems that hardware detection method has been changed since 21.3.1.
Setting environment variable as `INTEL_MEDIA_RUNTIME=MSDK` works for me as a
workaround.

-- 
You are receiving this mail because:
You are the assignee for the bug.