Strictly internal - sorry.
( you wouldn’t want to see the Friday Pizza chatter anyway 
)
Even as a team member, there are things I don’t see.
Allright @ChuckPa and thanks for your continous communication
What thread or part of the forum should we follow ?
Thanks,
Etienne
This is the place to be.
All other communications are internal.
3 Likes
would donating pizza help?
Anyways, please thank the dev team for looking into this and working on it.
1 Like
From what I’ve gathered from this thread, the issue people are having is specifically with HDR Tone-mapping.
So, if we disable HDR tone mapping until a solution is found, does everything else still work?
I’m finalizing a new build and want to make sure that the UHD750 is at least functional before purchasing.
Negative.
Hardware transcoding will cause an issue whether you are using HDR tone mapping or not.
Tone mapping causes visual glitches.
I think someone has it working if they only use HW decoding and not encoding (I possibly have that backwards). It’s somewhere further up in this thread.
I purchased another NUC to use in the mean time. But I’m eagerly awaiting a fix so that I can move back over to the NUC 11.
It seems that this thread will go dark until the issue has been fixed though. There doesn’t seem to be anywhere to track this bug which is annoying.
1 Like
I wonder if the new beta is the key…
FIXES:
- (Debian) Improve Intel CPU model parsing during installation for hardware transcoding detection and user messaging
Edit: just tried a 4K HDR to 1080p and PMS had crashed. So still no joy, yet
Just stumbled across this thread as the latest beta broke HW transcoding for me on Iris Xe Graphics (Rocket Lake).
Previously, I had used hardware encoding and decoding successfully for a couple of months, but then started getting green glitches on Live TV on some clients (such as chrome or android TV), so disabled HW encoding and left HW decoding on.
But as of yesterday, all HW decoding has failed when HW decoding Live TV with errors such as
Aug 31, 2021 09:49:40.065 [0x7fb705df0b38] ERROR - [Transcoder] [mpeg2video @ 0x7f87f7074dc0] Failed to end picture decode issue: 23 (internal decoding error).
Aug 31, 2021 09:49:40.065 [0x7fb708060b38] ERROR - [Transcoder] [mpeg2video @ 0x7f87f7074dc0] hardware accelerator failed to decode picture
I’m using Fedora 34 on the latest 5.13 kernel branch.
Very frustrating!
I just ran a bunch of tests since i wiped my box and had some free time today. I’ve been testing different kernel’s and neo versions with my plex docker image but this is all baremetal installs on a freshly installed box:
Ubuntu 20.04
Plex:1.24.2.4973 (baremetal install)
Neo: 21.34.20767
This is a rocket lake CPU but not a NUC: 11th Gen Intel(R) Core™ i5-11400 @ 2.60GHz
Kernel installed from ubuntu mainline kernel ppa
initrd.img-5.11.18-051118-generic (no gpu)
initrd.img-5.11.20-051120-generic (no gpu)
initrd.img-5.12.19-051219-generic (no gpu)
initrd.img-5.13.13-051313-generic (yes gpu) – No HW Transcode
initrd.img-5.14.0-051400-generic (yes gpu) – No HW Transcode
Ubuntu 21.04
initrd.img-5.11.0-31-generic (yes gpu) – Yes HW Transcode – Small amounts of static during transcode – More than 1 stream causes hangs
initrd.img-5.12.19-051219-generic (no gpu)
initrd.img-5.13.13-051313-generic (yes gpu) – No HW Transcode
initrd.img-5.14.0-051400-generic (yes gpu) – HW Transcode
This is an example of the plex logs when HW transcode doesn’t start. Its not hanging the trancoder, it just doesn’t use the GPU. (when i compile drm-tip it almost always hangs the transcoder and fails to start the stream)
This is an example of the static that i get in streams:
I have the same kind of issue on my 1135G7 CPU
Running on Docker, drivers properly forwarded.
1080p and SDR content are a blast and works fine, HDR transcoding is unwatchable because artifacts during playback. Transcoder sometimes wont even work at all even on some SDR content.
HDR to SDR yanks the CPU usage to orbit, strange considering that a J4105 can handle them no problem, what’s going on ?
Also is software transcoding supposed to be faster than hardware transcoding ? It’s kinda odd
I feel kinda disappointed, considering that these 11th gen are well suited for stuffs like these.
The problem is intel dropped the ball and didn’t get proper driver support into the linux kernel before they released them. This isn’t the first time they did this too. I want to say it was the 8th gen that had the exact same issue until they got the drivers sorted out. Once they get there these cpus/gpus are going to take practically anything you throw at them without a second glance. If you look at the DRM-TIP kernel source code commits the amount of i915 stuff they keep working on is crazy.
1 Like
Had you bothered to actually read the thread you just posted in, you’d know what’s going on.
Nuc11 uses tiger lake, not rocket lake
The Star Wars fan above is correct. This thread is specifically about Tiger Lake.
Hopefully when that is fixed the fix also applies to Rocket Lake, but the problem presents slightly differently on Rocket Lake.
Maybe start a seperate thread for Rocket Lake if you’re having issues so they they stay separated and don’t confuse things for the Plex engineering team.
I’m an i5-11400 user but unfortunately have zero knowledge of linux’s inner workings. I am experiencing the same issues as described in this thread, what kind of information could I provide to start a new thread specifically for Rocket Lake? My setup is Unraid 6.9.2 with Linxuserver.io’s plex docker.
1 Like
Yes, and it baffles me that nearly a year after launch no sign of fix from Intel’s side. When I buy a piece of hardware that cost $300 from big CPU compagny I expect it to work flawless.
11th gen seems not worth buing currently if you tends to use QuickSync, Windows also seems affected to this problem. And it’s hugely problematic if you use a media server where most of the scheduled tasks regarding media (not counting on database cleanup) and LiveTV for deinterlacing relies on Transcoding.
I can’t handle the fact that I’m prohibited to use hardware transcoding on a piece of hardware … That is advertised as being well suited for that case.
I’m sorry for being angry but there’s reasons behind this.
Not sure if it’s an Intel issue, but seems ich777 has it working in his Jellyfin builds;
https://forums.unraid.net/topic/105034-uhd-750-rocket-lake-igp-support/page/5/
Yeah, and they are using a Rocket Lake CPU. This thread here is specifically about Tiger Lake CPUs, on which it is a confirmed Intel issue that has not yet been resolved. Please don’t hijack the thread, guys.
Isn’t Tiger Lake using the same iGPU as Rocket ?
Please read the thread. Everything you ask has already been discussed.
1 Like
