HW Tone Mapping Transcoding no longer works after updating to 4.9.1.80 (Synology 220+)

[e2zippo 25]

2 hours ago, Bims0n said:

@e2zippo: Sometimes the assigned rights on the corresponding transcoding driver files reset, you then have to reset them again manually to the correct user. This once broke transcoding for me, and it took forever to diagnose.

You can find them under "/dev/dri" with the rights split into [owner/group/0600]. For me they are:

• card0 (root/root)
• renderD128 (root/videodriver)

Thanks, I'll take a look how that looks on my end! 

[e2zippo 25]

5 hours ago, e2zippo said:

Thanks, I'll take a look how that looks on my end! 

Looks Ok here i guess? 

 

[rekit 16]

1 hour ago, e2zippo said:

Looks Ok here i guess? 

 

is h265 transcoding enabled on yours, or only h264? h265 has never worked on my 220+ but h264 always worked fine. (it's only HW tone mapping that broke in this new server update)

[e2zippo 25]

10 minutes ago, rekit said:

is h265 transcoding enabled on yours, or only h264? h265 has never worked on my 220+ but h264 always worked fine. (it's only HW tone mapping that broke in this new server update)

I'm not using h265 transcoding, only h264. And HW transcoding h264 has always worked fine up until maybe 6 months ago or something, when it stopped working with tonemapping on. If I turn it off it works again, which is where I'm at today. 

[Bims0n 14]

On 10/6/2025 at 7:03 PM, e2zippo said:

Looks Ok here i guess? 

 

Looks good to me. Is a reason mentioned in the transcoding log why it fails?

[Luke 42077]

51 minutes ago, Bims0n said:

Looks good to me. Is a reason mentioned in the transcoding log why it fails?

The ffmpeg log will have the raw error message. We are looking into this,. Thanks guys.

[rekit 16]

17 hours ago, Luke said:

The ffmpeg log will have the raw error message. We are looking into this,. Thanks guys.

looks like a possible fix in the 4.9.2.1 beta? that was quick!

[heffeque 78]

Just as a quick comment, DSM 7.3 just launched.

Hopefully it doesn't break anything regarding Emby. 

(It broke my "Active Backup for Business" which I managed to fix, and some people were having issues with the USB UPS not working, so... It's not a solid update yet).

[rekit 16]

4 minutes ago, heffeque said:

Just as a quick comment, DSM 7.3 just launched.

Hopefully it doesn't break anything regarding Emby. 

(It broke my "Active Backup for Business" which I managed to fix, and some people were having issues with the USB UPS not working, so... It's not a solid update yet).

par for the course with synology unfortunately

[Luke 42077]

6 hours ago, rekit said:

looks like a possible fix in the 4.9.2.1 beta? that was quick!

It has an updated Intel drivers, but that comes with the possibility of new problems so it will need to stay in beta for a little bit. 

But yes, testing and feedback on it would be helpful in the testing area.

[softworkz 5065]

Unfortunately, OpenCL is broken in some of our packages for quite a while.

 

Please try switching to VAAPI.  With VAAPI, you should be able to use VAAPI HW tone mapping on GeminiLake iGPUs.

To do so, go to the Transcoding page on the server dashboard, change HW Acceleration from Yes to Advanced, and then move all VAAPI decoders and encoders to the top of each list.

(with QuickSync, only OpenCL tone mapping is possible which is pointless when OpenCL isn't working)

[bjjones 22]

I'm the same boat with an Apollo Lake chip, is OpenCL broken on that generation as well, I don't remember ever having a problem with HW transcode or tonemapping? Luke, I'm still on 4.8.11 so can provide whatever media combination that I could log if it would be useful

Edited October 15, 2025 by bjjones

[softworkz 5065]

1 hour ago, bjjones said:

I'm the same boat with an Apollo Lake chip, is OpenCL broken on that generation as well, I don't remember ever having a problem with HW transcode or tonemapping?

Does it work for you or not?

[Meursault 2]

Hi,

I have tested with 4.9.2.4 beta and  4.9.1.80. HW transcode works but not with tone mapping. I tried with both quicksync and vaapi settings, with a Raptor Lake chip. It is all perfect in 4.8.11. I posted some logs before, but if you need any more feedback let me know! 

Thank you!

[softworkz 5065]

8 minutes ago, Meursault said:

Hi,

I have tested with 4.9.2.4 beta and  4.9.1.80. HW transcode works but not with tone mapping. I tried with both quicksync and vaapi settings, with a Raptor Lake chip. It is all perfect in 4.8.11. I posted some logs before, but if you need any more feedback let me know! 

Yours is probably a different issue.

But: I'm seeing to successfull logs with 4.8.11 => VAAPI

and one failing log from 4.9.1.80 => QuickSync

 

So that's not evidence for anything yet. 
PS: Please do not post logs with subtitle processing involved - as long as it's not specifically about that part,

Thank you

 

 

 

[bjjones 22]

20 hours ago, softworkz said:

Does it work for you or not?

It's, QSV, always worked fine in 4.8.x for me for both transcoding and tone mapping

[softworkz 5065]

4 minutes ago, bjjones said:

It's, QSV, always worked fine in 4.8.x for me for both transcoding and tone mapping

Do you have logs from both 4.8 and 4.9 (non-working) for comparison?

[bjjones 22]

2 hours ago, softworkz said:

Do you have logs from both 4.8 and 4.9 (non-working) for comparison?

no, I've not updated to 4.9 yet (awaiting the outcome of this). That's why I asked if there are any scenarios I could run and create the log on 4.8 (Synology intel) that would be helpful to compare the processing to the non working ones out there from the 4.9 users. Sorry for not being more clear

Edited October 16, 2025 by bjjones

[softworkz 5065]

1 hour ago, bjjones said:

no, I've not updated to 4.9 yet (awaiting the outcome of this). That's why I asked if there are any scenarios I could run and create the log on 4.8 (Synology intel) that would be helpful to compare the processing to the non working ones out there from the 4.9 users. Sorry for not being more clear

Alright thanks, got it.

A log from 4.8 would be helpful - but only if it's from the same hardware like the ones where it's failing in 4.9.

[bjjones 22]

The the Synologys named in the thread are the 2020 variety running Celeron J4125 Gemini Lake, I'm running a 2018 with the previous gen J3455 Apollo Lake as the only difference. Intel QSV had a small change between the 2 (10 bit HEVC encode added) https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video 

Happy to help out if I can

[softworkz 5065]

12 hours ago, bjjones said:

The the Synologys named in the thread are the 2020 variety running Celeron J4125 Gemini Lake, I'm running a 2018 with the previous gen J3455 Apollo Lake as the only difference. Intel QSV had a small change between the 2 (10 bit HEVC encode added) https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video 

Happy to help out if I can

Thanks, that's helpful and also answers all the questions:

Elkhard Lake and Gemini Lake have limited HWA support in the iGPUs, both hardware and software-wise.
Among other limitations, they do not support OpenCL data sharing with VAAPI contexts, so it's no surprise that they do not support hw accelerated tone mapping using OpenCL.

What this means is:

• You can update Emby Server without worries
• Those who were claiming that it would have been working before will like have had it working via VAAPI

 

On 10/15/2025 at 7:54 PM, softworkz said:

Unfortunately, OpenCL is broken in some of our packages for quite a while.

This does NOT apply to Synology packages (but Docker is one example).

 

@rekit (and all others having Gemini or Elkhard Lake) =>

On 10/15/2025 at 7:54 PM, softworkz said:

Please try switching to VAAPI.  With VAAPI, you should be able to use VAAPI HW tone mapping on GeminiLake iGPUs.

To do so, go to the Transcoding page on the server dashboard, change HW Acceleration from Yes to Advanced, and then move all VAAPI decoders and encoders to the top of each list.

 

[rekit 16]

27 minutes ago, softworkz said:

Thanks, that's helpful and also answers all the questions:

Elkhard Lake and Gemini Lake have limited HWA support in the iGPUs, both hardware and software-wise.
Among other limitations, they do not support OpenCL data sharing with VAAPI contexts, so it's no surprise that they do not support hw accelerated tone mapping using OpenCL.

What this means is:

• You can update Emby Server without worries
• Those who were claiming that it would have been working before will like have had it working via VAAPI

 

This does NOT apply to Synology packages (but Docker is one example).

 

@rekit (and all others having Gemini or Elkhard Lake) =>

 

FWIW I always had vaapi disabled on mine.

[heffeque 78]

27 minutes ago, softworkz said:

Thanks, that's helpful and also answers all the questions:

Elkhard Lake and Gemini Lake have limited HWA support in the iGPUs, both hardware and software-wise.
Among other limitations, they do not support OpenCL data sharing with VAAPI contexts, so it's no surprise that they do not support hw accelerated tone mapping using OpenCL.

What this means is:

• You can update Emby Server without worries
• Those who were claiming that it would have been working before will like have had it working via VAAPI

 

This does NOT apply to Synology packages (but Docker is one example).

 

@rekit (and all others having Gemini or Elkhard Lake) =>

 

That's strange because I'm not getting errors when using QuickSync + OpenCL for tone mapping (DS918+ J3455 on 4.8).

Or are you saying that the QS+OCL combo is working on Apollo Lake (old), but not on Gemini Lake(less old), and that the Gemini Lake and newer need VAAPI? 

[softworkz 5065]

3 hours ago, heffeque said:

Or are you saying that the QS+OCL combo is working on Apollo Lake (old), but not on Gemini Lake(less old),

Yes

 

3 hours ago, heffeque said:

and that the Gemini Lake and newer need VAAPI? 

No. Only Gemini Lake and Elkhard Lake.

 

[softworkz 5065]

3 hours ago, rekit said:

FWIW I always had vaapi disabled on mine.

And you think that OpenCL tone mapping would have been working before?

Yours is Gemini Lake, right?