SOLVED: Low Transcoding FPS with Intel A380

SOLVED: Low Transcoding FPS with Intel A380 - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Low Transcoding FPS with Intel A380 (/t-solved-low-transcoding-fps-with-intel-a380)

Pages: 1 2

RE: Low Transcoding FPS with Intel A380 - TheDreadPirate - 2024-07-04

As always, you are correct. I missed that.

RE: Low Transcoding FPS with Intel A380 - container_ship - 2024-07-04

(2024-07-04, 02:50 AM)nyanmisaka Wrote: Hardware decoding is not enabled.

What do you mean? Shouldn't that be enabled when HWA is on?

RE: Low Transcoding FPS with Intel A380 - TheDreadPirate - 2024-07-04

Simply enabling HWA does not enable hardware decoding. There are separate check boxes for it. Can you share screenshots of Dashboard > Playback?

Here is mine for reference.

RE: Low Transcoding FPS with Intel A380 - container_ship - 2024-07-04

Hi, these are my settings

RE: Low Transcoding FPS with Intel A380 - TheDreadPirate - 2024-07-04

Mimic my settings and see if that changes your transcode performance.

RE: Low Transcoding FPS with Intel A380 - container_ship - 2024-07-04

Well a new issue came up and I don't know if this is the right place to ask.
Please tell me and I will create a new post.

After running the Jellyfin Docker for a while, it crashed (no idea why) and wouldn't start again. The logs for the restart said that /dev/dri/renderD128 is missing.
Well checking that and somehow the ARC GPU is now unclaimed in lshw -C display with no usable driver.

This is the second time this happened. First I thought adding dg2_huc_gsc.bin was the problem but I guess not. A rollback to a snapshot before installing docker and jellyfin restores the gpu and it's drivers.

(2024-07-04, 05:59 PM)TheDreadPirate Wrote: Mimic my settings and see if that changes your transcode performance.

I did and it improved to about 70fps-80fps but then the other issue came up.

RE: Low Transcoding FPS with Intel A380 - TheDreadPirate - 2024-07-04

My main Jellyfin is directly installed on bare metal Ubuntu. But my test instances are running on docker and I've never experienced what you described. Are you passing in renderD128 explicitly or are you just passing in /dev/dri entirely? It SHOULDN'T matter but sometimes makes a difference for some users.

RE: Low Transcoding FPS with Intel A380 - container_ship - 2024-07-04

I'm passing in renderD128 explicitly.
This is my compose file:

Code:
version: '3'

services:

  jellyfin:

    image: jellyfin/jellyfin

    container_name: jellyfin

    user: 1000:1000

    group_add:

      - "104" # Change this to match your "render" host group id

    ports:

      - 8096:8096

      - 8920:8920 #optional

      - 7359:7359/udp #optional

      - 1900:1900/udp #optional

    volumes:

      - /home/vm/jellyfin/config:/config

      - /home/vm/jellyfin/cache:/cache

      - /home/vm/jellyfin/media:/data/media:ro

    devices:

      - /dev/dri/renderD128:/dev/dri/renderD128

    restart: unless-stopped

RE: Low Transcoding FPS with Intel A380 - TheDreadPirate - 2024-07-04

Try just passing in /dev/dri entirely. The Intel driver will automatically select the first available Intel device if you have more than one, but you only have one.

RE: Low Transcoding FPS with Intel A380 - container_ship - 2024-07-05

(2024-07-04, 07:27 PM)TheDreadPirate Wrote: Try just passing in /dev/dri entirely. The Intel driver will automatically select the first available Intel device if you have more than one, but you only have one.

I did. The System is still working after a couple of reboots, so I *think* this fixed it.