I rolled back to 1.32.4 to fix the problem, everything works.
Thats really good news! Thanks for sharing this with us.
Cant wait for the newer Kernel to come to Unraid now 
It would have been nice to see the PMS DEBUG logs ZIP file which captured this happening to confirm it’s ProxMox – BUT
- It is what it is
- You know what I’m going to say about ProxMox
- GPU passthrough to the OS in the VM is the key. Which OS distro version AND KERNEL is running in there ?
Remember, VM virtualizes the hardware. During passthrough, your VM’s kernel is in charge.
Supplemental:
chuck@plexqa-av1:~$ dpkg -l | grep plexm
ii plexmediaserver 1.32.5.7349-8f4248874 amd64 Plex organizes all of your personal media so you can easily access and enjoy it.
chuck@plexqa-av1:~$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : 13th Gen Intel(R) Core(TM) i5-13400
chuck@plexqa-av1:~$
I install docker directly in the host OS, no VM, no LXC. So plex should be using the host kernel.
I use sr-iov to share GPU with VMs.
root@pve:~# docker exec -it plex sh
# dpkg -l | grep plexm
ii plexmediaserver 1.32.5.7349-8f4248874 amd64 Plex organizes all of your personal media so you can easily access and enjoy it.
# cat /proc/cpuinfo | grep 'model name' | uniq
model name : 12th Gen Intel(R) Core(TM) i7-12700
# uname -a
Linux 43eae564b4ea 6.2.11-2-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.11-2 (2023-05-10T09:13Z) x86_64 x86_64 x86_64 GNU/Linux
I’m still really confused why this keeps getting brushed over - the ‘faulty’ kernel works with the ‘older’ Plex version, but not with newer versions of plex server. So, irrespective of what has happened to the newer Kernel, something has changed in Plex - what has changed, and why can it not be reverted?
As said:
1.32.1.6999-91e1e2e2c + Old Kernel (Unraid 6.11) - Works
1.32.1.6999-91e1e2e2c + New Kernel (Unraid 6.12) - Works
Newer Plex (1.32.5.7349-8f4248874) + New Kernel (Unraid 6.12) - Broken
So whilst there may have been a change in the Kernel, there is clearly also something different in Plex where the old version is not ‘affected’ by the Kernel change. What is it? Appreciate it might be something that cannot be rolled back for very good reason, but it would be useful to understand what it is rather than just keep ignoring it and saying the solution is to wait for a new Kernel (or roll back to the Plex version that magically circumvents this breaking kernel change).
1 Like
No-one has a view?
I do agree with what you are saying but i think we are all waiting to hear what the Plex Devs say since they are best to answer this question. Perhaps ping ChuckPa?
@ChuckPa Any thoughts on the above?
To recap:
1.32.1.6999-91e1e2e2c + Old Kernel (Unraid 6.11) - Works
1.32.1.6999-91e1e2e2c + New Kernel (Unraid 6.12) - Works
Newer Plex (1.32.5.7349-8f4248874) + New Kernel (Unraid 6.12) - Broken
What changed between 1.32.1 and 1.32.5 that can’t be reversed and seems to have an issue on the newer Kernel?
Let me recap recent history for you:
- 1.31.3.6868 - worked for (I think?) everyone.
- 1.32.0.xxxx - Intel Media Driver upgraded to current release
– Major breakage across all the platforms - 1.32.5.7210 - Fixed ApolloLake processors , Added AMD GPU support (SDR)
- 1.32.5.7349 - Hotfix for something else in PMS – works on our RaptorLake
- – work in flight for the next PMS release –
- – Staffing changes –
Now we’re at the point of figuring out, by looking at the code changes, what was being done. We have no notes, no plans, no in-code comments. (It’s rough)
We still have to fix known
- End of subtitles forces stopping playback.
– Empty subtitles track fails (related) - Gemini Lake CPUs still have no HW transcoding. (no work had been done after IMD update)
Now add on to this the new 6.2 kernel and the i915 / Iris/XE changes (GUC / HUC) which are needed to support this.
Can we “unwind” ? Sure, but not without angering a whole bunch of people.
We lost a lot of institutional knowledge which is hard to replace in only a few weeks time.
Recovering from this is sufficiently important that I’m tasked with transcoder development duties.
I still have HW transcoding on my older NUC with the new unraid kernel so there is that to use as a base
1 Like
Genuinely, thank you for the candid update. Position is now better understood! Guess I’ll stick to Unraid 6.11 for a while 
Thank you very much for the update @ChuckPa . I think we all head about the staffing changes there at Plex and can definitely understand the challenges you all are facing during this time.
Please feel free to reach out if you would like any of us here to do any testing for you, im sure you will find the community more than happy to assist
Take care and chat soon im sure.
I have J4125 (Gemini Lake Refresh) in an Asustor NAS and working HW transcoding with 1.32.5.
My only grief is the depreciation of i965, because that means no working subtitle burning anymore.
Thanks for your open words. I think its obvious that Plex management sucked big time here (you weren’t taken over by Elon Musk by coincidence?).
There never has been HW subtitle burning with PMS.
Deprecation of the i965 was Intel’s change.
In order to support the newer processors, we needed the newer Intel Media Driver.
In their work, they removed support for i965 on all CPUs above CometLake and ultimately removed the i965 driver from all CPUs.
If you have a hard-coded VaapiDriver="i965" in your Preferences.xml file, please remove it.
We had this discussion over and over and it seems you never seem to understand the thing!!
Where did I say there would be subtitle burning in hardware?
I said subtitle burning doesn’t work with iHD while it perfectly worked with i965, but you keep ignoring that simple fact!
What does this mean? “No working subtitle burning anymore”
The i965 has NO correlation to subtitle burning.
Yes, it has. We wrote again and again about that topic.
EDIT: Because you maybe cannot remember the countless time we talked about that issues:
iHD driver BROKE subtitle burning (that was even acknowledged by your team in late 2019). Its so slow, that real time transcoding is impossible (0.1 speed on a J4125 @FullHD).
The workaround was to switch over to i965 which again enabled flawless subtitle burning (2-4 speed on a J4125 @FullHD)
As that workaround is not possible anymore, we are standing there without subtitle burning unless the issue that iHD is creating with it can be finally fixed.
I assume the isse still persists? I wanted to chime in aswell. Unraid 6.12.4 - HEVC files in 4k, mostly with DV encodes will only make use of hw transcoding once HDR tone mapping is turned off.
i5-12500
Is this still being investigated? Thanks
1 Like
Just adding another data point. I’m using Unraid 6.12.4, with an i3-10100. Rolling back to 1.32.1.6999-91e1e2e2c (hotio container) restores 4K HW transcode functionality with tonemapping.
Appreciate it’s a tricky spot you’re in development-wise. Happy to help wherever I can.
2 Likes
Yeah issue still persists for me too on UnRaid 6.12.4 with 12900K 
Im also really hoping that the Plex team have this on their to-do list to fix too.
HDR tone mapping is broken.After I turned on HDR tone mapping, the HW transcoding failed and the CPU did all the work.
CPU:intel i5-13500
Unraid:6.12.4(6.12.3)
plex:1.32.6.7468
Linux kernel:6.1.49(6.1.38)
