Hardware transcode broken after updating to 4.8.x

[Lessaj 467]

The only other package I have related to libva is libva-mesa-driver, might need that.

[Luke 42077]

Hi, did you find anything?

[hlidskialf 5]

No luck yet. (Didn't get to it yesterday/today) but I'm wondering if Emby is having trouble finding the driver or ffmpeg installation after the changes made by the updates. I hope to wrestle a bit more with it tomorrow or Thursday as I go away next week and want this issue locked down before then!

[hlidskialf 5]

Alright, I've gotten it working and it turns out the culprit was Cuda. I've spent an ungodly amount of time on this trying to determine what was the issue, but it seems that anything after Cuda v12.1.0 will cause Transcoding to fail. Everything else on my system is back up to date, running Emby-Server-Beta v4.9.0.12 and utilizing the AUR provided ffmpeg 2023.06.25 version.

Hopefully this helps someone else out, I appreciate all the assistance from the community.  

[binghunlong 0]

On 3/22/2024 at 12:06 PM, Luke said:

Hi, that would be great, thanks.

I encountered the same issue and had to revert to version 4.7. I hope the cause can be identified as soon as possible. My graphics card model is Tesla P4.

[binghunlong 0]

logs

4 minutes ago, binghunlong said:

I encountered the same issue and had to revert to version 4.7. I hope the cause can be identified as soon as possible. My graphics card model is Tesla P4.

 

hardware_detection-63890090630.txt embyserver.txt ffmpeg-transcode-ae36bb69-edc9-4c62-b5bb-8559efba9c3f_1.txt

[Luke 42077]

On 8/6/2025 at 3:39 AM, binghunlong said:

logs

 

hardware_detection-63890090630.txt 253.92 kB · 0 downloads embyserver.txt 93.73 kB · 0 downloads ffmpeg-transcode-ae36bb69-edc9-4c62-b5bb-8559efba9c3f_1.txt 108.27 kB · 1 download

Hi, we are looking into this. We'll have a new ffmpeg build on the server beta channel in the near future, so stay tuned for that.