IMHO, you should stay on the 20.04 LTS.
I tried 20.10 “groovy” but there are less kernels available compared to the 20.04 LTS, and you can’t install Intel’s media runtime packages.
I don’t know if your issues are related to mine (you have 10th gen CPU, I have 11th gen), but you can try to install the OEM “edge” kernel (5.10 based) and Intel’s runtime packages
I tested the build ( plexmediaserver_1.21.1.3830-6c22540d5_amd64.deb ). I did not notice anything different. This one shows “(hw)” on the 1080p blu-ray remux when transcoding to 720p. And, just like the latest built, it does not show “(hw)” on the 4k blu-ray remux with the Tone Mapping setting on. However, when I disable Tone Mapping, then the “(hw)” text appears. (I am not sure if this is different than the latest build, because I never tested the 4k remux transcode to 1080p with the Tone Mapping setting off — I had always left it on.)
In my previous comment, I mentioned the “latest” build. When I stated that, I was referring to the original installation I mentioned in the original post. I was unaware that since there was a release today, it was no longer the “latest” build.
So I’ve installed the latest build (PlexMediaServer-1.22.0.4136-3ca7898f3) and seeing the same behavior: all transcodes are showing “(hw)”, except 4k remuxed HDR content when Tone Mapping is on – that continues to not show “(hw)”.
I need to differentiate betwen Intel Core processors 4xxx → 9xxx and 10xxx +
There are different dependencies which I need test for.
I’ve written about 1/2 of the new logic. I hope tomorrow to finish first pass of it.
If you and other CometLake owners are interested, I’m willing to create a Developer’s Preview thread so we can finalize it works as it should.
This is a significant effort because I’m now being selective about which CPU is installed and if it’s HW transcoding capable.
There are a lot of details (whether packages are installed or not) to keep track of.
It isn’t complex but, as we call it, “detail rich” and I need make certain not to miss any.
The preview thread will allow us to test , debug & refine if needed, then finalize the update.
@ChuckPA, I’ve got hardware on order to build a new server, based on an I9-10900F CPU. I’ll probably be running it on OpenSuSE (due to utter dislike for what’s happened w/ CentOS.) Are you interested in a guinea pig for that environment, this is a perfect opportunity to tinker.
Sounds great! Yes, we can tinker. – soon as I figure out this D%$^* package LOL
I thought I had a proper solution until I realized there are Xeon CPUs with this capability which also must be supported.
What I’m trying to achieve is meaningful tests in preinstall and accurate output for you to know the status / what needs to be done (e.g. add packages/drivers).
Intel’s lack of a clear numbering scheme on Xeon CPUs scuttled all the nice work I have for Intel Core cpus
@ChuckPa isnt there another thread which says that installing the intel drivers is a workaround ? Is this a different issue?
Thanks for looking into this.
Yes. I do. And the same issue as above. Quicksync doesnt work with 4k HDR with tone mapping on. (CPU hovering at 60%).
10th Gen Intel® Core™ i5-10400 processor(6-Core 12M Cache 2.9GHz to 4.3GHz)
@ChuckPA, I’ve got a basic server set up, I9-10900 and a GTX 1650 running on OpenSuSE. Let me know if I can be of assistance. I’m still running on the other server (probably will be for at least a couple of weeks yet,) so we have at least a little time.
You guys are amazing. Was just poking through my own, I also noticed (for the very first time) that my results suggest Intel QSV Hardware: Not found after updating to latest (beta channel) version, via lifetime PlexPass.
This sounds EXACTLY correct. I’m running a little type2 Ubuntu Server VM under Win10 Pro, do not have any GPU passed through. Unsure exactly what the i915 is, perhaps mobile chipset? The 1080 Ti needs to stay with my Winblows machine for gaming purposes, but perhaps I could consider passing through the intel onboard UHD630, hrmm. I won’t waste any more of your precious time poking through my logs (unless they are genuinely helpful to you, i’m happy to spin up whatever tests that may help), you immediately were able to identify the problem. Thank you for sharing your big brain with me, sir.
Apparently I have misunderstood the capabilities of my hardware here. Mostly work around this by encouraging end-user devices to Direct Play / Direct Stream media – guess that’ll have to suffice for now. I have a bunch of really old nVidia Quadro (2000, i think) but unsure if this ancient hardware is even supported, or worthwhile to set up if i were to migrate my Plex VM to an ESXi host. Thanks again, Chuck. Stay safe, sir.
Windows isn’t going to let you pass through the i915, which is needed to access the UHD630, AND keep the display output running.
The i915 (which is a chip inside the CPU), is primary interface to the chip’s GPU and QSV ASIC.
This same issue occurs in all VMs. I run ESXi and , in order to use QSV, I must disable the HDMI output because the i915 & GPU for display get assigned as a pair by the display driver which precludes pairing the i915 & UHD630 ASIC.
If you had an Nvidia card, you could pass it and be done.
I have a 1080 Ti in this Windows 10 box, but i use it for gaming, so can’t really devote it to Plex. The other options are to migrate (or rebuild) my Plex VM on the ESXi host, which has 3 Quadro 2000 GPUs. Despite their age, would this still be suitable for basic transcoding purposes?
Thank you immensely for holding my hand and taking the time to describe exactly what the i915 chip is, as well as its primary function. Guess i need to make sure the old Xeons (single E5-1620 & dual E5-2665, both v1) actually support QSV before i get too far ahead of myself. Cannot begin to thank you enough for the supremely helpful information and prompt response(s).