Missing AMF encoder after installing Intel Arc drivers

[end2endzone]

The AMD Advanced Media Framework Encoder is now missing from available encoder list. I think this is because I just installed Intel Arc video drivers for an Intel a380 GPU. I have rebooted to make sure the problem is not because the encoder is used by another application.

I have look at the logs and I think this is because OSB is loading up D3D11 on adapter Intel(R) Arc(TM) A380 Graphics instead of my integrated AMD Radeon(TM) Graphics :

18:37:35.129: Initializing D3D11...
18:37:35.129: Available Video Adapters:
18:37:35.129:     Adapter 0: Intel(R) Arc(TM) A380 Graphics
18:37:35.129:       Dedicated VRAM: 2055208960
18:37:35.129:       Shared VRAM:    3919446016
18:37:35.129:       PCI ID:         8086:56a5
18:37:35.129:       Driver Version: 31.0.101.3490
18:37:35.130:       output 0:
18:37:35.130:         name=DELL S2421HS
18:37:35.130:         pos={0, 0}
18:37:35.130:         size={1920, 1080}
18:37:35.130:         attached=true
18:37:35.130:         refresh=60
18:37:35.130:         space=RGB_FULL_G22_NONE_P709
18:37:35.130:         sdr_white_nits=80
18:37:35.130:         nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
18:37:35.130:       output 1:
18:37:35.130:         name=DELL S2421HS
18:37:35.130:         pos={1920, 0}
18:37:35.130:         size={1920, 1080}
18:37:35.130:         attached=true
18:37:35.130:         refresh=60
18:37:35.130:         space=RGB_FULL_G22_NONE_P709
18:37:35.130:         sdr_white_nits=80
18:37:35.130:         nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
18:37:35.130:     Adapter 1: AMD Radeon(TM) Graphics
18:37:35.130:       Dedicated VRAM: 519847936
18:37:35.130:       Shared VRAM:    3919446016
18:37:35.130:       PCI ID:         1002:1638
18:37:35.130:       Driver Version: 30.0.21023.1015
18:37:35.132: Loading up D3D11 on adapter Intel(R) Arc(TM) A380 Graphics (0)
18:37:35.164: D3D11 loaded successfully, feature level used: b000

The AMD module seems to be found by OSB :

18:37:36.219: [AMF] Version 2.7.0 loaded (Compiled: 1.4.14.0, Runtime: 1.4.25.0, Library: 1;4;25;0;22.10.17.01;202205170126;AMD-Radeon-Driver/drivers:5548348e1fc53d521207686e4bfa6612312eaba7).
18:37:36.248: [AMF] <Id: 1> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
18:37:36.275: [AMF] <Id: 2> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
18:37:36.278: [AMF] [Capability Manager] Testing Direct3D 11 Adapter 'AMD Radeon(TM) Graphics (VEN_1002/DEV_1638/SUB_88091043/REV_00c8)':
18:37:36.278:   H264/AVC: Supported
18:37:36.278:   H265/HEVC: Supported
18:37:36.278:

I am uncertain if converter trans characteristic errors are normal or not.

I cannot find a location in settings where I can force D3D11 to load using my Adapter 1: AMD Radeon(TM) Graphics.
Is there a way to have both AMF and QSV at the same as available encoder?
I doubt OSB is not able to support a computer that have 2 graphic adapters. I would assume that people that have nvidia and amd graphics cards in their system would have seen this kind of issue before.

Any help is appreciated.

 

[end2endzone]

I forgot to mentioned that after installing the Intel graphics drivers, I also updated OSB from 27.1.3 (64 bit) to 28.0.3 (64 bit).

I have done more investigation. I have updated different things think that it could help:

• The AMD drivers from version 22.6.1 to latest version (22.10.3).
• Windows 10 from version 21H2 to version 22H2.

but the problem persist.

I have found more examples of the same error: "Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)". This issue does not seems related to an incompatibility between AMD and Intel drivers.

 

[end2endzone]

I finally solved the problem by reverting to OSB 27.1.3. Both AMD AMF and QuickSync encoders are now available in the list. I have kept the latest AMD drivers.

To me it does not seems like the AMD drivers are at fault because OSB 27 is working fine with AMD drivers 22.10.3. To me, it looks more like a change was implemented between OSB 27 and OSB 28 that resulted in an incompatibility between the two.