There are some PMS changes which come along with the IHD driver update.
I think this is one of them.
I’ve seen some cases (the fire closeup you show) where the flames oversaturate.
(That might be part of what’s coming with other half of this update)
I’m working on another issue right now but this sounds more like a problem with the source media than the server.
I believe so, see screenshot:
Results below:
00:00.0 Host bridge [0600]: Intel Corporation Gemini Lake Host Bridge [8086:31f0] (rev 03)
00:00.3 System peripheral [0880]: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model [8086:3190] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 03)
00:0e.0 Audio device [0403]: Intel Corporation Celeron/Pentium Silver Processor High Definition Audio [8086:3198] (rev 03)
00:0f.0 Communication controller [0780]: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface [8086:319a] (rev 03)
00:12.0 SATA controller [0106]: Intel Corporation Celeron/Pentium Silver Processor SATA Controller [8086:31e3] (rev 03)
00:14.0 PCI bridge [0604]: Intel Corporation Gemini Lake PCI Express Root Port [8086:31d6] (rev f3)
00:14.1 PCI bridge [0604]: Intel Corporation Gemini Lake PCI Express Root Port [8086:31d7] (rev f3)
00:15.0 USB controller [0c03]: Intel Corporation Celeron/Pentium Silver Processor USB 3.0 xHCI Controller [8086:31a8] (rev 03)
00:17.0 Signal processing controller [1180]: Intel Corporation Celeron/Pentium Silver Processor I2C 4 [8086:31b4] (rev 03)
00:17.3 Signal processing controller [1180]: Intel Corporation Celeron/Pentium Silver Processor I2C 7 [8086:31ba] (rev 03)
00:1c.0 SD Host controller [0805]: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller [8086:31cc] (rev 03)
00:1f.0 ISA bridge [0601]: Intel Corporation Celeron/Pentium Silver Processor LPC Controller [8086:31e8] (rev 03)
00:1f.1 SMBus [0c05]: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model [8086:31d4] (rev 03)
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
02:00.0 SATA controller [0106]: JMicron Technology Corp. JMB58x AHCI SATA controller [197b:0585]
@trollop_earthly_hassock would love to see if you’re having any luck with this new build on your system.
how do I prevent downgrading to the latest published version with each container restart?
Weird. I can restart the container and the custom version persists. It only reverts to the latest published version if I update the image.
Could you share your container configuration please?
Well crap - actually after checking myself it looks like the PMS version reverted to the old one. That’s strange, it didn’t use to work that way in the past.
This fixed it for me. I’m using a script currently to stop the default plex instance and then installing this deb, any idea when this goes live to the beta channel?
@gonenutsbrb what CPU do you have?
Folks:
The engineer and I are working right now to finalize everything.
For those who applied the Developer build, only to have it revert, Check your update settings / scripts.
Out-of-cycle builds can get overwritten by automation
@ChuckPa Sorry I responded late to some of your questions a few days ago, my answers can be seen here: Hardware HDR tonemapping still broken on 1.31.0.6654 - #143 by matthe6038
Unfortunately I don’t think this build resolves the HDR tonemapping issue for J4105 and J5005 processors.
Xeon E-2146G (8th gen), using UHD P630 for graphics.
I thought HDR tonemapping with QSV only working with 7th gen+?
Do 3rd gen processors actually work with that?
Edit: Realized I had two replies replying to the same person.
J4105 and J5005 are 9th gen and support QSV
Edit: they might be 8th gen actually. I hate the references to “generations” because it’s so confusing lol. Regardless, the J5005 should support HDR tonemapping, and did in the past before an update broke it.
If you use the official Plex docker image (plexinc/pms-docker) the tag you use determines whether or not it is updated automatically on start/restart. Both the “plexpass” and “public” image tags result in containers which will auto-update. The “latest” tag does not.
If you use the Linuxserver image, the “VERSION” property determines much the same thing.
Got it, my quick google search failed me and I misread it.
You have UHD 600, so I think it should fix it. You can confirm that the dev version is the one actually running in the container? On your Plex Settings->Settings->General page it should show this:
Using custom scripts with the linuxserver version (not sure if the plexinc version supports custom scripts), you can have a script that looks like this which will pin version to the deb file linked above from ChuckPa:
#!/bin/bash
s6-svc -d svc-plex
dpkg -i /config/plexmediaserver_1.32.2.6977-3494ca766_amd64.deb
s6-svc -u svc-plex
This stops the plex instance that’s running, installs the dev version, and starts it. Just make sure you remove/comment the script after they post the fixed version.
I was hoping to help others understand why their containers were continually updating, not looking for a solution myself. But thanks. 
So we have the entire family J4105, J5005, N5105, and N5095 ?
Intel is playing games with their naming. UHD600 / UHD630 should be OK.
What I see in the 5xxx CPU families is “UHD Grahics” .. which tells me NOTHING and , given the issues, might explain why OpenCL fails.
We need to figure out what’s failing but given all the diagnostics I’ve seen + the logs + documentation. Either the OpenCL capabilities of the processor are incorrect or the OpenCL side of it is too darn small to run the microcode (which is tiny)
I’ve been eyeballs deep in how HW transcoding works for the past week.
So much I just helped complete that developer update PLUS a little more 
I would love to tell folks (public forum preview) but first want to confirm on a few machines privately THEN I’ll open it up for everyone.
Biggest issue for me is I have no clue how to best suggest “the goodness this the new stuff radiates on everyone” (If you hear me – don’t say it – Ask and I’ll open PM)
There’s a lot to unpack here, but most of it is explained on the Intel media-driver GitHub page.
Specifically, the Decoding/Encoding Features and Video Processing Features tables, and the final notes at the bottom of the page (note 3 is particularly interesting as far as Jasper Lake and Elkhart Lake is concerned), describe exactly what features and codecs you can expect to work for each generation.
In general, my experience suggests that an N5105 processor with a recent kernel and GuC/HuC enabled allows for hardware accelerated decoding with encoding with HDR → SDR tone mapping enabled (though not performed in hardware for this processor, per the above-referenced notes).
Again, with this processor (Celeron N5105), I can successfully transcode (both decode and encode) in hardware, with HDR → SDR tone mapping. The tone mapping is occurring in software, as it isn’t supported by the iGPU in this CPU.
