Jump to content

Emby Server not using hardware transcoding with Intel A310.


Recommended Posts

Posted

I've just set up a new machine and installed an Intel Arc A310. I've configured the hardware transcoding settings, and as far as I can tell, everything is set up correctly. However, it appears to still be transcoding on CPU, and will not use the A310.

Posted

Include the hardware detection log along with the other details requested in the support post.

 

Posted

Almost definitely the same issue as here:

 

  • 1 year later...
AV1Opus
Posted

I could still confirm this issue under 4.9.3.0 (production) and 4.10.0.4 (beta), unfortunately. The suspicion of a frontier LLM on the underlying cause is "ffdetect probes encoders via libmfx, and libmfx still doesn't enumerate Arc A310 encode".

Meanwhile showing up properly in vainfo:

# vainfo --display drm --device /dev/dri/renderD129 2>&1 | grep -i enc
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileHEVCMain               : VAEntrypointEncSliceLP
      VAProfileHEVCMain10             : VAEntrypointEncSliceLP
      VAProfileVP9Profile0            : VAEntrypointEncSliceLP
      VAProfileVP9Profile1            : VAEntrypointEncSliceLP
      VAProfileVP9Profile2            : VAEntrypointEncSliceLP
      VAProfileVP9Profile3            : VAEntrypointEncSliceLP
      VAProfileHEVCMain422_10         : VAEntrypointEncSliceLP
      VAProfileHEVCMain444            : VAEntrypointEncSliceLP
      VAProfileHEVCMain444_10         : VAEntrypointEncSliceLP
      VAProfileHEVCSccMain            : VAEntrypointEncSliceLP
      VAProfileHEVCSccMain10          : VAEntrypointEncSliceLP
      VAProfileHEVCSccMain444         : VAEntrypointEncSliceLP
      VAProfileAV1Profile0            : VAEntrypointEncSliceLP
      VAProfileHEVCSccMain444_10      : VAEntrypointEncSliceLP

 image.thumb.png.101479dc6a77a96cabda86adbf36172f.png

Even with Anonymize log contents turned on, the hardware_detection still contains the MachineName and other personal info, I am happy to share the full version via DM. However, I attached the encoders array from the log, where all the action happens.

Money quote:

        {
            "DeviceIndex": 1,
            "DeviceInfo": {
                "VendorName": "Intel Corporation",
                "DeviceName": "DG2 [Arc A310]",
                "VendorId": 32902,
                "DeviceId": 22182,
                "SubsytemVendorId": 5935,
                "SubsytemDeviceId": 16960,
                "DevPath": "/sys/bus/pci/devices/0000:07:00.0",
                "DrmCard": "/dev/dri/card1",
                "DrmRender": "/dev/dri/renderD129",
                "IsEnabled": 1,
                "IsBootVga": 1
            },
            "Error": {
                "Number": -17,
                "Message": "Error setting VAAPI device handle: MFX_ERR_DEVICE_FAILED"
            }
        }

I hope we can get this resolved, not sure whether I will keep this card if I can't use it in here.

Thanks

encoders.json

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...