topic Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above in Intel® Arc™ Discrete Graphics

QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

nanashi — Thu, 20 Feb 2025 07:29:23 GMT

QSV hardware encoding does not show up as a list of encoders on OBS and cannot be used with driver version 32.0.101.6557 and above. As a workaround, I am now using version 32.0.101.6460, but I am no longer able to increase the driver version.

# HW/SW info

- GPU

- Intel Arc A750

- OS

- Windows 11 24H2 (OS Build 26100.3194)

- Graghics Driver

- 32.0.101.6557, 32.0.101.6559(WHQL)

- Application

- OBS Studio 31.0.1 (64 bit) (2025/1/18 release, current latest)

# How to Reproduce

- install intel GPU driver version 32.0.101.6557 and above

- run OBS and with menu bar open 'file' > 'settings' > 'output' and check 'video encoder' list

- Quicksync AV1/H.264/HEVC do not appear in the list

- In OBS log file recorded 'Seems the QSV test subprocess crashed. Better there than here I guess. Let's just skip loading QSV then I suppose.'

# Additional Info

Similarly, ffmpeg is giving the error 'Failed to init HECI driver' with GPU driver version 32.0.101.6557 and above. It was also reported below.
https://community.intel.com/t5/Graphics/Failed-to-init-HECI-driver/td-p/1662203

I am assuming that this is a problem with the intel GPU driver and not OBS.

Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

JedG_Intel — Fri, 21 Feb 2025 07:03:27 GMT

Hello nanashi,

I understand that you're having issues with the newer drivers as QSV encoding is not showing as an option on OBS. Have you tried using other recording software to further isolate the issue? I'm asking this so we can narrow down the investigation that we'll be conducting. Please also send a screenshot of the options available on your end.

I hope to hear from you soon.

Best regards,

Jed G.

Intel Customer Support Technician

Re: QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

nanashi — Fri, 21 Feb 2025 11:40:37 GMT

Attached are logs of QSV hardware encoding in ffmpeg command line, as I wrote in the 'Additional Info' section of my first post.

The following commands are used to output in QSV AV1 format with hardware encoding (approximately around line 65 of each log file).

> ffmpeg -hwaccel_output_format qsv -f lavfi -i mandelbrot=size=1920x1080 -t 5 -c:v av1_qsv output.mp4

When executed with driver versions 32.0.101.6460 and 32.0.101.6559, respectively, the output file itself is done successfully in both cases, but the latter produces the following error.

> IGSC: (D:\qb\workspace\31779\source\igsc-master\lib\igsc_lib.c:gsc_driver_init():218) Error in HECI init (3)
> IGSC: (D:\qb\workspace\31779\source\igsc-master\lib\igsc_lib.c:igsc_device_subsystem_ids():1597) Failed to init HECI driver

I have not compared them with any software other than OBS and ffmpeg.

Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

JedG_Intel — Mon, 24 Feb 2025 08:43:32 GMT

Hi nanashi,

Thank you for sharing all this information. I will be investigating this matter and I will get back to you as soon as possible.

Best regards,

Jed G.

Intel Customer Support Technician

Re: QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

Jachia — Tue, 25 Feb 2025 08:57:01 GMT

I also have same problem

Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

JedG_Intel — Wed, 26 Feb 2025 00:55:29 GMT

Hi nanashi,

I am reaching out to provide you with a series of steps to assist with the ongoing investigation.

Try to install the latest driver 101.6559
Launch OBS with Admin rights

Once done, kindly inform me if the HECI error persists and if you are still unable to select the encoders.

Best regards,

Jed G.

Intel Customer Support Technician

Re: QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

nanashi — Wed, 26 Feb 2025 08:46:48 GMT

I installed driver version 32.0.101.6559, restarted OS to confirm (did not change OBS or ffmpeg versions).

I started each of OBS and ffmpeg with administrator privileges and both had no problems. I am attaching the logs as before, just in case.

However, there is some risk in continuing to run them with administrator privileges in the future, so I have reverted the drivers back to 32.0.101.6460 again.

In another thread, I saw that a driver update is planned to address this issue. So I am also planning to wait for a driver fix.
https://community.intel.com/t5/Intel-ARC-Graphics/Intel-Driver-Causing-Issue/m-p/1669199#M21274

Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

JedG_Intel — Thu, 27 Feb 2025 05:30:31 GMT

Hello nanashi,

I really appreciate this information, it is really helpful. I'll be continuing the investigation and I'll give you an update again as soon as possible.

Best regards,

Jed G.

Intel Customer Support Technician

Re: QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

bo1983 — Thu, 27 Feb 2025 22:06:41 GMT

same problem with handbreal or vlc

Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

Felipe_Intel — Fri, 28 Feb 2025 20:48:20 GMT

Hello all, this issue is not seen in our latest driver 32.0.101.6632. Please download (link below), install and test with this driver. I'd really appreciate your feedback on this. https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html

Re: Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

bo1983 — Fri, 28 Feb 2025 21:59:49 GMT

can confirm, bugs are gone

Re: Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

nanashi — Sat, 01 Mar 2025 00:17:03 GMT

The problem is gone with driver version 32.0.101.6632 for both OBS and ffmpeg. Thank you very much for your help.

Re:QSV HW encoding not working in OBS with driver version 32.0.101.6557 and above

JedG_Intel — Fri, 07 Mar 2025 03:02:11 GMT

Hi @nanashi @bo1983,

After further testing, we can confirm that the issue is fixed and I agree with @Felipe's response. Since you were able to confirm that the problem is resolved, I will now proceed with closing this inquiry. If you need further assistance, please submit a new question as this thread will no longer be monitored.

Best regards,

Jed G.

Intel Customer Support Technician