Hardware Tonemapping and Transcoder Issues with beta version 1.41.0.8930

Plex Media Server Plex Pass Betas
1

Server Version#: Version 1.41.0.8930
Player Version#: Plex Web Version 4.136.1, Plex for Mac Version 1.100.1.221-94aa83fb
Sample File: Sony Swordsmith 4K HDR Demo
System: ASRock NUC-Box – Intel Core Ultra 125H
OS: Proxmox 8.2, running Kernel 6.8.12-1-pve
Plex Context: Running in an LXC container based on Ubuntu 22.04.04 with iGPU passed through.

Transcode Settings:

  • Enable HDR tone mapping: True
  • Tonemapping algorithm: Mobius
  • Use hardware acceleration when available: True
  • Use hardware-accelerated video encoding: True
  • Hardware transcoding device: Unknown (Intel)

Issues:

  1. Hardware transcoding works, hardware tonemapping gives ugly and weird results.
  2. The transcoding device shows “Unknown (Intel)” rather than its CPU generation.
  3. I can select a tonemapping algorithm but the tonemapping slider options don’t appear, even though my CPU is a newer generation than Tiger Lake.
  4. No matter which tonemapping algorithm I choose I can’t seem to get as good of results as software tonemapping.

Full Quality, No Transcoding:

plex-full-quality-no-transcode
plex-full-quality-no-transcode1058×472 32.3 KB

1080p 20mbps Hardware Tonemapping using Mobius:

plex-1080p-20mbps-hardware-tonemapping-mobius
plex-1080p-20mbps-hardware-tonemapping-mobius1065×470 46.5 KB

1080p 20mbps Hardware Tonemapping Disabled:

plex-1080p-20mbps-hw-tonemapping-disabled
plex-1080p-20mbps-hw-tonemapping-disabled1069×468 33.2 KB

Log Procedure:

  1. Rebooted PMS
  2. Played the HDR sample file using Plex for Mac
  3. Switched to 1080p 20mbps transcoding
  4. Let playback continue for 15-20 seconds.
  5. Waited 2 minutes, then downloaded logs

Plex Media Server Logs_2024-08-29_14-19-23.zip (875.5 KB)

Ubuntu 22.04 and Ubuntu 24.04 HW transcoding
2

@jakemauer

I’ll make you a deal… :smiling_imp:

Help me get Proxmox installed on the new N100 (alderlake) box
-AND-
I’ll be able to help you.

What I get is it starts creating LVs.. and hangs at 3%.

ISO 8.2-2.

Can’t explain it.

Do I need a different version ? From where please ?

EDIT: It fininished.. Now what? :rofl:

1 Like
3

Hey @ChuckPa! Thanks for going on this sidequest with me.

So for my current setup I’ve used TTeck’s scripts to create the Plex LXC. It handles the LXC creation and passes through the iGPU. Proxmox VE Helper-Scripts. To install you run the command from that link in the proxmox console for the proxmox node itself, then follow the prompts.

I don’t think it would make a difference, but I’ve considered re-creating my LXC using this guide instead: How to Install Plex on Proxmox (+ Hardware Acceleration)

4

@jakemauer

Screenshot from 2024-08-30 03-57-55
Screenshot from 2024-08-30 03-57-55726×517 63.6 KB

Screenshot from 2024-08-30 03-53-11
Screenshot from 2024-08-30 03-53-11974×513 62.1 KB

Screenshot from 2024-08-30 03-22-43
Screenshot from 2024-08-30 03-22-431056×473 63.5 KB

Did this last night before bed.

5

Nice! Do you feel like tonemapping created visually pleasing results? What does the dropdown for transcoder engine show, Unknown (Intel)?

Also do you get the tonemapping fine tuning controls?

6

VERY pleasing.

It’s using Hable now versus oversaturated Mobius
(user selectable now too! )

This annoyed me.

I could not screen capture WITH a dropdown . STUPID GNOME / Javascript.

N100-CPU-Plex
N100-CPU-Plex816×612 109 KB

Hint: We’re considering going to full up BT.2390 tonemapping. This means you get the full HDR , as encoded, mapped into SDR as the spec defines it. (No more 3->2 axis interpolations)

7

Well that’s good. Any ideas why I’m seeing the results I’m seeing, and why my CPU is showing up as Unknown (Intel)?

8
  1. Prox 8.2-2 installed
  2. PMS Version 1.40.5.8921-836b34c27
  3. Used that recommended script to create the container and pass the iGPU

That’s all I know.

9

Can we do a bake sale to get you a meteor lake box?

10

If you want to do a bake sale, that’ll be great.
Just wire the :moneybag: :wink:

I almost bought a meteorlake
I was in the final evaluation phase and even gotten a quote for one.

I found the photos of the MeteorLake and RaptorLake where the die wires solder to the physical chip carrier substrate (the pins)
They were burned.

As I further discovered, this is a known problem with both Raptor and Meteor Lake CPU generations.

Intel’s current “fix” isn’t a fix at all. They’re simply going to send out microcode to everyone which reduces the maximum performance level (what most bought it for) down to a level which won’t burn.

For those whose CPUs are already damaged – too bad.

… And now you know why I have a 12th Gen with fewer problems :rofl:

PS: I have a RTX 2000 in my NUC12 as well.
It also comes up in Plex as Unknown. :rofl:

I know what your “unknown” is and have submitted the issue to update the list of GPU IDs from Intel and Nvidia into PMS.

2 Likes
11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.