Server Version#: 1.32.5.7210
Player Version#: Browser 4.100.1 Android Player: 9.26.0.2526
HDR Tone mapping with HW Transcoding broken for the 12900K. I’m on Unraid 6.12.1 Linux kernel 6.1.34 and plex 1.32.5.7210 and if I try and play a 4K HEVC movie with Tone mapping enabled it wont Hardware transcode and will transcode using the CPU.
If I uncheck HDR Tone mapping then it HW transcodes fine.
The only solution that i have found was to roll back my Official PMS Docker container back to 1.32.1.6999-91e1e2e2c all later versions after this break the HDR Tone Mapping HW Transcode and the CPU gets hammered.
The native installation is working as it should be
chuck@plexqa-av1:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server$ dpkg -l | grep -i plexm
ii plexmediaserver 1.32.5.7210-77f7f99fa amd64 Plex organizes all of your personal media so you can easily access and enjoy it.
chuck@plexqa-av1:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : 13th Gen Intel(R) Core(TM) i5-13400
chuck@plexqa-av1:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server$
Hi @ChuckPa,
I dont think its Unraid because as soon as i rolled back my official Plex Docker container to version 1.32.1.6999-91e1e2e2c it all started working again as normal.
Also, im using 12th Gen Alder Lake and i see you are using a 13th Gen chip, perhaps the 13th Gen is working fine.
Essentially what im seeing is that anything not HEVC will hw transcode but as soon as there is a HEVC file then it does not hw transcode and the only way to get around that is to disable Tone mapping.
Rolling back to the version mentioned above resolves all these issues.
@ChuckPa I can roll back to 1.32.5 Latest version and provide logs if that helps.
Its just very strange that version 1.32.1.6999-91e1e2e2c works perfectly but any other later versions wont hw transcode HEVC files.
Yeah i have another Unraid box and its using an i9600K Coffee Lake and that works without any issue on Plex version 1.32.5.7210. That Unraid Box is the same Unraid Version and Linux version as the 12900K thats having issues.
So i dont think its Unraid or the Linux kernel version thats causing the issue.
It’s not plex if I can do this (source of the screenshots above):
chuck@plexqa-av1:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server$ dpkg -l | grep -i plexm
ii plexmediaserver 1.32.5.7210-77f7f99fa amd64 Plex organizes all of your personal media so you can easily access and enjoy it.
chuck@plexqa-av1:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : 13th Gen Intel(R) Core(TM) i5-13400
chuck@plexqa-av1:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server$
I’m starting my unraid box now and will see what I get
Fair point
Thanks for testing this. Im interested to hear what you find out on your Unraid box.
Just for completeness i did another test with Plex version 1.32.5.7210 on the Alder Lake CPU but this time i disabled “HDR Tone Mapping” and only then the hw transcoding works.
I used the plexpass image
Does the plexpass image give the same container as yours? i can try and specify the container like you did and see if that makes a difference.
root@BabyNUC:~# uname -a
Linux BabyNUC 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz GenuineIntel GNU/Linux
root@BabyNUC:~#
FWIW: Our QA AlderLake machine is also 5.19 kernel
chuck@plexqa-av1:~$ uname -a
Linux plexqa-av1 5.19.0-45-generic #46-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 7 09:08:58 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
chuck@plexqa-av1:~$
ah well. ill just have to downgrade back to 1.32.1.6999-91e1e2e2c then.
I know at least of another person having the same issue as me. Posted on the Discord support and reverting back to 1.32.1.6999-91e1e2e2c also worked for him.
I dont want to be a pain but are you able to upgrade your Kernel? when i was on 5.19 kernel it was working perfectly so perhaps a compatibility thing?