Intel N 355 hardware transcoding not available

[cantchooseaname 0]

5 minutes ago, Velun said:

So, from what I gather, Emby can't use the latest Intel GPU's? I just moved to an Ultra 9 285k, and I can't seem to get HW transcoding working. On Plex and Jellyfin I managed to do it in like 2 minutes, and on Emby I've wasted hours with no luck, and from what I gather here, it's impossible for now.

Sounds exactly like what I just went through. And yes, sounds like Emby just doesn’t work with new GPUs until they fix it. 
 

@LukeDo you have an ETA on when this will be updated to work?

[EHRETic 7]

1 hour ago, Velun said:

So, from what I gather, Emby can't use the latest Intel GPU's? I just moved to an Ultra 9 285k, and I can't seem to get HW transcoding working. On Plex and Jellyfin I managed to do it in like 2 minutes, and on Emby I've wasted hours with no luck, and from what I gather here, it's impossible for now.

As mentioned above, I have the same CPU... same issue... and also working on the other 2 platforms!
Hopefully they can fix it soon 

[Seger 123]

On 8/8/2025 at 12:28 PM, Ra'Jiska said:

No this won't work using Ubuntu 24.04, this is because the ABIs used by Emby are linking with older versions which is the reason why I used Ubuntu 16 as base image, I suspect Emby is built against Ubuntu 16 image as well, which is why this one works.

@zofielIf you don't feel like building it all yourself, you can just use the automatically built images that include the latest dependencies that makes the new processors supports, image is `rajiska/emby-n150-fixed:latest` (you can replace `latest` with whatever version you want, starting at 4.9.0.0), dockerhub repo. You can find the build happening on Github, automated by Github Actions, which I have setup as this processor issue has been known since at least December 2024, and yet no fixes came out.

Can confirm that this build also works with Ultra 9 285k! THANK YOU!!! @LukePlease update, we would all be very happy!

[EHRETic 7]

6 hours ago, Seger said:

Can confirm that this build also works with Ultra 9 285k! THANK YOU!!! @LukePlease update, we would all be very happy!

Euh, I'm confused... I wanted to test the rajiska version this morning, so before I went straight to rajiska, I upgraded my version to the latest beta 4.1.29 (docker tag 4.1.29 on official repo).

I could see the QuickSync and VAAPI appearing in the transcoding options:

But QuickSync doesn't seems to work on a normal 4K DV HEVC movie, when VAAPI does.

QuickSync selected (uses CPU):

VAAPI:

Rajiska version seems to have the same issue. Can anybody confirm this?

So @Luke, did you update anything lately on beta? I could not spot anything in release notes.

(sorry in advance if I notice something everybody knows... I only noticed the whole issue recently and I don't have all the history)

PS: I tested QuickSync on my "productive" Emby platform (4.8) running on an holder CPU, QuickSync works (just to be sure)

[Luke 42077]

16 hours ago, EHRETic said:

Euh, I'm confused... I wanted to test the rajiska version this morning, so before I went straight to rajiska, I upgraded my version to the latest beta 4.1.29 (docker tag 4.1.29 on official repo).

I could see the QuickSync and VAAPI appearing in the transcoding options:

But QuickSync doesn't seems to work on a normal 4K DV HEVC movie, when VAAPI does.

QuickSync selected (uses CPU):

VAAPI:

Rajiska version seems to have the same issue. Can anybody confirm this?

So @Luke, did you update anything lately on beta? I could not spot anything in release notes.

(sorry in advance if I notice something everybody knows... I only noticed the whole issue recently and I don't have all the history)

PS: I tested QuickSync on my "productive" Emby platform (4.8) running on an holder CPU, QuickSync works (just to be sure)

The new ffmpeg build that I've been mentioning is not in the beta yet. 

How are you defining it as not working?

[cantchooseaname 0]

9 minutes ago, Luke said:

The new ffmpeg build that I've been mentioning is not in the beta yet. 

How are you defining it as not working?

You’ve been mentioning a new ffmpeg build for months and months which is supposed to solve this issue. Can you please let us know when this is expected? We’re all waiting for an honest answer

[EHRETic 7]

7 hours ago, Luke said:

The new ffmpeg build that I've been mentioning is not in the beta yet. 

How are you defining it as not working?

With version 4.8, I'm not able to see my Intel "GPUs" at all, I only see NVIDIAs:

But with last beta or the Rajiska (same Docker host with Ultra 9 285K Intel CPU), I can see all Intel GPUs... but QuickSync is not working while VAAPI does work:

That is why I'm confused: only Rajiska was supposed to offer Intel drivers and not the last official beta! But it does (only for VAAPI)!!!

[Luke 42077]

On 9/11/2025 at 2:56 AM, EHRETic said:

With version 4.8, I'm not able to see my Intel "GPUs" at all, I only see NVIDIAs:

But with last beta or the Rajiska (same Docker host with Ultra 9 285K Intel CPU), I can see all Intel GPUs... but QuickSync is not working while VAAPI does work:

That is why I'm confused: only Rajiska was supposed to offer Intel drivers and not the last official beta! But it does (only for VAAPI)!!!

It could be that some are updating the driver in the docker container.

[EHRETic 7]

On 9/26/2025 at 2:10 AM, Luke said:

It could be that some are updating the driver in the docker container.

What is your base image for Emby Docker container ?

[alucryd 315]

We don't really have a base image, it's a barebones busybox base, even smaller than alpine. We are currently upgrading our graphics stack to support newer CPUs and GPUs, it should hopefully be ready for the next beta.

[Seger 123]

On 9/10/2025 at 1:07 AM, Seger said:

Can confirm that this build also works with Ultra 9 285k! THANK YOU!!! @LukePlease update, we would all be very happy!

@Luke,

Do you expect that the current beta can replace this build? I saw that you added drivers.

Thank you and many greetings

Seger

 

[Luke 42077]

15 minutes ago, Seger said:

@Luke,

Do you expect that the current beta can replace this build? I saw that you added drivers.

Thank you and many greetings

Seger

 

Eventually, yes, once we've worked out the issues with it.

[Seger 123]

@Ra'Jiska, If you are so sweet and turn the current stable version into a Docker version again, since the drivers are still in the beta, I will not switch to the official version yet. Thank you very much!!!