Not sure what to expect. Forcing a 76Mbps → 8Mbps transcode, I get the HDR logo. Enabling a PGS subtitle I do not. Seems to look about the same either way. With the PGS subtitles I see les GPU utilization, more CPU, and soon get the “Server not powerful enough” error.
When using Plex Web, playing an HDR10 movie, and selecting “Convert Automatically” from Playback Settings, should I expect it to do hardware transcoding and hardware tone mapping?
I’m selecting “Convert Automatically” because it uses Direct Stream if I don’t. I get audio only (blank screen) in this case, which seems to be due to having:
“Use alternate streaming protocol for video playback”: true
“Automatically adjust quality (Beta)”: false
(I have it set this way due to horrendous playback skipping in edge/chrome bug)
When set to “Convert Automatically”, then Plex does transcode, but no (hw) tag - my CPU is pegged (can’t keep up), and my GPU is unused.
I have installed the Plex from this thread, am on Windows 11, have a 9th gen CPU (unsupported for hw tone mapping), but also have a Intel ARC A770. The A770 is selected in the Transcoder setting page.
If this is expected to work, let me know what I can try or what more info you need.
I second this, the compatibility matrix is unclear because the original post in this sub mentions the Intel VPL “library” is needed and to check the referenced GitHub page for compatibility. Upon checking the referenced page, we are greeted with a matrix that shows Intel VPL “dispatcher” choosing either the Media SDK or Intel VPL “Runtime”.
My initial guess is that the “library” the original post is mentioning must be the “Runtime” that is shown in the GitHub page - meaning that those processors using the Media SDK DO NOT support the new tone mapping.
But I am unsure what the “library” the original post is mentioning means; is it indeed the Runtime, or is it simply the dispatcher?
I tried to make it clear to them the first day this was posted that people were going to be confused by that compatibility matrix.
It looked to me like these CPU’s DID NOT have support.
7th Gen (Kaby Lake)
8th Gen (Coffee Lake S)
9th Gen (Coffee Lake Refresh)
10th Gen (Comet Lake)
13th Gen (Raptor Lake)
14th Gen (Meteor Lake)
(I’m not mentioning anything prior to 7th gen because there’s no h.265 support)
It appeared to me that only 11th and 12th gen were actually supported.
I’ve talked to some people that have tested this and the only CPU’s I can confirm are working are just that. 11th and 12th gen are working and everything else is failing
os: windows 11 64bit
hardware: i5-11600k and nvidia 4070 ti.
I know my nvidia gpu supports hardware tonemapping, but when i tried it a few months ago it was using 60-80% of the nvidia gpu to do the tonemapping, so i turned it off and switched back to using the intel uhd 750 with tonemapping off.
I installed the 1.40.1.8114-xxxxxx from this post, switched on tone mapping and tried from a few different devices to force trancoding. And for some reason I saw in task manager that it was transcoding on the nvidia gpu, even tho the intel uhd 750 was chosen in plex server settings.
So I went into windows graphics settings and forced the "plex transcoder.exe to use "low performance uhd 750), rebooted and tried again.
And it works! It works GREAT infact, on most of my devices. I can force the transcode and it uses a lot of the uhd gpu in the start, probably till it fills up the throttle buffer, and then it just does some small spikes after that, while the transcoded media played perfectly and with no buffering,
Cpu not even worth mentioning.
Colors looking much better then without tonemapping. So I am happy to report a sucess for this on these devices: apple tv, plex desktop app for windows, plex web app in edge and chrome, plex app on ios.
However, on chromebook the android play app was unable to play anything at all. I tried with and without hdr tonemapping, and no matter what, it would not play any transcoded media at all, erroring out with “An error occurred while attempting to play this video. Please check your connection and try again”
I have updated the test build to be based on the recently released 1.40.1 beta as well as addressed some identified issues. Additionally, Since the support matrix confused some users I have explicitly listed which GPUs we expect tonemapping to work on. While I understand it is disappointing that tonemapping will only work on the newer GPUs, we are limited to what Intel has chosen to support. That being said I am currently working on a feature which will hopefully eliminate the need for tone mapping in many cases
Server OS: Windows 11
Client: Edge on another Windows 11 machine
Following steps from @techsnot I set “Plex Transcoder.exe” to use the ARC card in Windows Settings. This seems to have worked as Task Manger shows the ARC in use and Plex is able to transcode without pauses.
I do notice that the picture is much darker and colors less vibrant than with the software tone mapping. This isn’t the same as “washed out”, just a darker image - I’m pretty sure the tone-mapping is happening.
Are there any picture controls available - it’s a bit dark for my preference.
Plex Version: 1.40.0.8074 (HDR Tone mapping HEVC in hardware works great)
Plex Version: 1.40.1.8114 (HDR Tone mapping HEVC in software only)
OS: Windows 11 64bit
Client: Android Plex App
Processor: 12th Gen Intel N100
Testing this on a low power Beelink N100 system. The first beta release 1.40.0.8074 works great handling 4k HEVC HDR hardware tonemapping perfectly. The second release will only tonemap in software.
I have tried both versions twice now and can replicate this behavior consistently
PMS 1.40.1.8114 is a regular beta release and not linked to the forum preview for Windows Tonemapping with Intel iGPUs.[edit: this was actually incorrect…]
8111 was released as beta on Thursday, 22 Feb, as was the 8114 preview release.
Build numbers do not imply content, only the order in which the builds occurred. So, 8114 was built after 8111, but does not necessarily have all the features/fixes as 8111. However, it seems the thumbnail bug is present in both.
Multiple transcoding engines at the application level not supported
Forgive me if I misunderstand that this means: does this mean that only one 4K transcode at a time? And if so, does that work on Linux instead of windows?