Minisforum N5 Pro with AI 9 HX PRO 370 HW transcoding problem

[Smiehu 6]

Hello,

I have problem with HW transcoding with AMD AI 9 HX PRO 370 and Radeon™ 890M GPU. Transcoding seems to work but I have no video during playback (only audio).

OS: Unraid 7.1.4
Emby: 4.9.1.80 (docker by linuxserver)

GPU is recognized in Transcoding options (screen in attachment).

During playback there is info that movie is transcoding by GPU (Vaapi) but no video during playback only audio and subtitles.

A lot of errors in log.

What can I do?

 

ffmpeg-transcode-23429bfd-39d8-4f62-bcfe-ef7d3b1badc8_1.txt

[Luke 42077]

Hi, have you tried with another file to see how things compare?

[ApfelVonStrudel 0]

Hello,

Same issue here with same device & emby version but different OS

Hardware : N5 Pro AI 9 HX PRO 370 and Radon 890M iGPU, 92Go.

OS: Truenas Scale 25.04

Emby : 4.9.1.80 (from official emby docker repository)

Hardware decoding seems activated still no video only audio. I tried on few videos.

From within the container this command seems to provide a correct transcoded video from HW. 

/bin/ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i /data/input.mkv -vf 'format=nv12,hwupload' -c:v 
h264_vaapi -packed_headers 0 -b:v 3M -maxrate 3M -bufsize 6M -f mp4 /data/output.mp4
p4

I am not sure about these options and how I could solve this issue ? 

ffmpeg-transcode-19a5f6f6-01e2-4c2f-849b-e3d5f5dc5523_1 2.txt

[Smiehu 6]

On 10/29/2025 at 8:03 PM, Luke said:

Hi, have you tried with another file to see how things compare?

Yes, all 4K HDR HEVC and all 1080p HEVC have this same effect.

[Happy2Play 9780]

Devs will have to explain the errors more but suggests a driver issue.

17:06:21.737 Stream mapping:
17:06:21.737   Stream #0:0 (hevc) -> scale_vaapi:default
17:06:21.737   Stream #0:2 (pgssub) -> scale:default
17:06:21.737   hwupload:default -> Stream #0:0 (h264_vaapi)
17:06:21.737   Stream #0:1 -> #0:1 (copy)
17:06:21.737 Press [q] to stop, [?] for help
17:06:21.737 subtitle_kickoff: call subtitle_resend_current 330340 frame->format: 1
17:06:21.752 subtitle input filter: decoding size 1920x1080
17:06:21.752 Auto-inserting subfeed filter
17:06:21.752 Auto-inserting graphicsub2video filter
17:06:21.781 subtitle_kickoff: resend - pts: 330372
17:06:21.781 subtitle_kickoff: call subtitle_resend_current 330382 frame->format: 1
17:06:22.185 [subfeed @ 0x17d1bc0] frame queue count: 4
17:06:22.287 [subfeed @ 0x17d1bc0] frame queue count: 5
17:06:22.299 [subfeed @ 0x17d1bc0] frame queue count: 6
vpe: output pixel format not supported 27
vpe: fail output support check. status 8
SIVPE ERROR ../src/gallium/drivers/radeonsi/si_vpe.c:951 si_vpe_processor_process_frame Check support failed with result: 8
SIVPE ERROR ../src/gallium/drivers/radeonsi/si_vpe.c:987 si_vpe_processor_process_frame Failed
17:06:22.459 [h264_vaapi @ 0x1044ec0] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).

 

[Happy2Play 9780]

AI response

These SIVPE errors you're seeing in the Emby logs point to a failure in the AMD GPU's video processing engine (VPE) during hardware-accelerated transcoding. Here's a breakdown of what they mean:

Error Explanation

• File: si_vpe.c — This is part of the AMD RadeonSI Gallium driver, used in Linux environments for AMD GPUs.

• Function: si_vpe_processor_process_frame — This function handles frame processing via the VPE.

• Error Message:

  Check support failed with result: 8 — The GPU driver determined that the requested pixel format or processing operation isn't supported.

  Failed — The frame processing couldn't proceed due to lack of support.

What’s Likely Happening

• The Emby server is attempting to transcode video using VAAPI (Video Acceleration API) on an AMD Radeon 890M iGPU.

• The pixel format or codec combination (e.g., HEVC to H.264 with subtitles) might not be supported by the VPE on this GPU.

• The driver is rejecting the operation, leading to no video output—only audio and subtitles are rendered.

Possible Fixes

• Try different pixel formats or filters: Modify the ffmpeg command to avoid unsupported formats. For example, try removing format=nv12 or changing it to yuv420p.

• Update drivers and Mesa stack: Ensure your system has the latest AMD GPU drivers and Mesa libraries, as support for formats and VAAPI improves over time.

• Use software transcoding: If hardware transcoding consistently fails, consider switching to software transcoding for affected formats.

• Check Emby container permissions: Make sure /dev/dri is correctly mounted and accessible in your Docker container.

[Luke 42077]

Do those items under Possible Fixes help at all ?

[bfogdb20825 4]

On 11/3/2025 at 3:41 AM, Luke said:

Do those items under Possible Fixes help at all ?

The same model running Docker is experiencing the same issue... It shows that incompatible streams cannot be played. According to AI, the GPU of this model is too new, while the driver is too old, and this particular chip could not be found.