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

[rekit 16]

QuickSync HW transcoding has been working fine for the last couple years, but I just updated server and now HW is broken -- using software transcoding only and can't keep up with playback.

EDIT: actually it looks like it's only related to tone mapping.

[Luke 42077]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[rekit 16]

3 minutes ago, Luke said:

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

I was mistaken, it's only broken when HW tonemapping is enabled for HDR playback. When I disable HW accelerated tone mapping, quicksync is used. Still testing and will upload logs in a few.

edit: ok so when HW accelrated tone mapping is activated, quicksync seems to not work (software encoding only), even when both quicksync tone mapping method and caapi tone mapping method are set to disabled (or set to any of the other options). the only way to make HW transcoding work with quicksync is by setting "enable hardware acclerated tone mapping" to disabled

Edited September 30, 2025 by rekit

[rekit 16]

26 minutes ago, Luke said:

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

Ok these two logs are from playing something when HW/quicksync transcoding wasn't working (HW tonemapping was enabled)

ffmpeg-remux-d43d4440-4de1-4121-9d15-423a068416f9_1.txt ffmpeg-transcode-e9598e55-e1e0-44e3-b871-206be1e2935b_1.txt

edit: fwiw, second file says:

18:57:54.606 [AVHWDeviceContext @ 0x235b280] Failed to get number of OpenCL platforms: -1001.
18:57:54.607 [hwmap@f3 @ 0x26628c0] Failed to created derived device context: -19.
18:57:54.607 [hwmap@f3 @ 0x26628c0] Failed to configure output pad on hwmap@f3
18:57:54.607 Error reinitializing filters!
18:57:54.607 Failed to inject frame into filter network: No such device
18:57:54.607 Error while processing the decoded data for stream #0:0
18:57:54.609 [aac @ 0x20e93c0] Qavg: nan
18:57:54.610 Conversion failed!
18:57:54.610 EXIT

Edited October 1, 2025 by rekit

[rekit 16]

16 minutes ago, Luke said:

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

and these were from when HW transcoding was working and using quicksync (HW tone mapping was disabled)

embyserver.txt ffmpeg-transcode-3d28f587-f5dc-4c21-a1f1-bab3a6f0e5a8_1.txt ffmpeg-transcode-5aca2b4a-8087-4751-9cb2-04d9df8c9866_1.txt ffmpeg-transcode-c891392b-530c-4621-9d52-4264fed7dd47_1.txt ffmpeg-transcode-08aee66b-6080-4c87-89a5-313894864cc7_1.txt ffmpeg-transcode-195d5ec2-7e8a-40df-953b-7f90f88edcd0_1.txt

[Luke 42077]

Hi, do you have a log from the previous version to compare with ?Thanks.

[rekit 16]

6 minutes ago, Luke said:

Hi, do you have a log from the previous version to compare with ?Thanks.

Here’s one from an old post

 

[Luke 42077]

OK so you haven't actually used this recently on 4.8?

[rekit 16]

Just now, Luke said:

OK so you haven't actually used this recently on 4.8?

I had HW tone mapping and transcoding enabled for a while on 4.8 and was working as expected. Let me know if a different old log might be helpful and I’ll see what I can find.

[Luke 42077]

6 minutes ago, rekit said:

I had HW tone mapping and transcoding enabled for a while on 4.8 and was working as expected. Let me know if a different old log might be helpful and I’ll see what I can find.

Right I'm just saying that unless it was used recently and you still have that log file then we don't actually know that the problem is caused by the 4.9 release.

What I mean is, a change in the hardware detection result will end up changing the resulting ffmpeg command lines that get used, so if this happened then might also see the issue on 4.8 and you just hadn't noticed it yet.

Obviously we will investigate and try to reproduce.

[rekit 16]

Oh I see. Well my particular server model is pretty much useless at software transcoding and tone mapping 4k HDR, so it’s noticeable enough when something is wrong that it’s safe to say it only just happened after updating. For now I can just disable tone mapping. And If I figure anything out that might be helpful I’ll update the post. Thanks Luke

[Luke 42077]

5 minutes ago, rekit said:

Oh I see. Well my particular server model is pretty much useless at software transcoding and tone mapping 4k HDR, so it’s noticeable enough when something is wrong that it’s safe to say it only just happened after updating. For now I can just disable tone mapping. And If I figure anything out that might be helpful I’ll update the post. Thanks Luke

Can you look through the ffmpeg logs in your logs folder and see if you might have one from the last three days of a similar example but on 4.8 ?

[rekit 16]

5 minutes ago, Luke said:

Can you look through the ffmpeg logs in your logs folder and see if you might have one from the last three days of a similar example but on 4.8 ?

Some things have transcoded the past 3 days but unfortunately nothing hdr (that needed to be tone mapped). Would a log with transcoding but no tone mapping be of any help?

[NeverReadyEddie 2]

I have a Synology 220+ and still on 4.8 so can I provide some logs or is that not going to work since it may not be exactly the same?

I am not happy to upgrade to 4.9 yet until this is resolved but can help test the same hardware on 4.8 for comparison.

Edited October 1, 2025 by NeverReadyEddie

[Meursault 2]

16 hours ago, Luke said:

Can you look through the ffmpeg logs in your logs folder and see if you might have one from the last three days of a similar example but on 4.8 ?

Hi!

I have the same problem with HW Tone Mapping. Maybe the attached log files can help?

Thank you!

logs.zip

Edited October 1, 2025 by Meursault

[heffeque 78]

Any updates on this?

I have a DS918+ (with a slightly older QuickSync version than the DS220+), and I'd like to also wait until there's a confirmation that the new branch's HW transcoding works OK.

[Luke 42077]

Hi, we are looking into it. Thanks.

[firefox1970 12]

I have Update to Version 4.9.1.80 on my Synology 720+ today and the HW transcoding is still working.

 

[heffeque 78]

16 minutes ago, firefox1970 said:

I have Update to Version 4.9.1.80 on my Synology 720+ today and the HW transcoding is still working.

 

With tone mapping it isn't. 

Edit: check here

 

Edited October 5, 2025 by heffeque

[firefox1970 12]

 

[rekit 16]

12 hours ago, firefox1970 said:

 

That shows it’s enabled but not necessarily that it’s working. Also it may be software tone mapping since you also have that enabled.

[e2zippo 25]

I've also had this issue for quite some time, I posted about it but never really got any attention. 

I've got a DS918+

 

Check here. 

 

Edited October 6, 2025 by e2zippo

[firefox1970 12]

If I am right you need Emby Premiere for HW-Transcoding/Tone-Mapping.

[e2zippo 25]

1 hour ago, firefox1970 said:

If I am right you need Emby Premiere for HW-Transcoding/Tone-Mapping.

I've had premiere for like 6 years. And hardware transcoding with tone mapping was working fine until something broke it. 

[Bims0n 14]

@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)

Edited October 6, 2025 by Bims0n