PMS 1.32.6+ HW transcoding issues and corrections

Intel NUC11PAHi5 with TigerLake-LP GT2 [Iris Xe Graphics] running 1.32.6.7515-873995547 in a Proxmox LXC working great again with Tone Mapping enabled.

Was able to run 3 x HDR → SD transcodes of different sources without an issue.

1 Like

Version 1.32.5.7349
Also Present in 1.32.6.7515
Intel UHD 630 QuickSync
Unraid Docker

I am not sure if this is related so can delete if needed. I am seeing transcodes that are really having issues playing and noticed that Plex is showing transcoding to HEVC from H.264 and AC3 to EAC3. Any thoughts on a workaround for this for now outside of turning off HW transcodes? Any help would be great.

image

people running the latest build, is the early reports that autoscan and pmm stopped working correct? anyone running autoscan docker can connect to plex?

@annihilatethee

Need your server and player logs please. Cannot replicate on iOS with 1.32.6.7515

Screenshot from 2023-09-20 11-31-21

Can you please do the following?

  1. Confirm DEBUG logging is enabled
  2. Restart PMS
  3. Wait 3 minutes (idle)
  4. Download Logs ZIP file
  5. Attach.

We’ll look to see if the table is filling up (most common scenario)

35 years in software and I am convinced that that is the dumbest response in the history of computers… “We F’d up, you need to uninstall and re-install the software to make it work”

I can’t seem to PM you them. I don’t feel comfortable posting them in the thread.

Where do you see that?

In this thread, I have been completely open about what happened and our efforts, in light of the staff reduction, to address and correct the problems.

It seems as if, without being specific, you’re referring to Synology NAS system which DO NOT PERMIT direct downgrade from a higher numbered version to a lower numbered version (e.g. 1.32.7 → 1.32.6). They (Synology) impose very strict version control on their products

2 Likes

I’m on a 920+ (Geminilake) am I correct in staying on 1.32.1.6999 for HW HDR Tone mapping to work?

Since this thread is linked from the release announcement, I will ask here.

Are we even sure that this bug does not affect Windows? Frankly, the information in this thread is very unclear.

@d2freak

This thread addresses Linux.

I cannot speak to Windows.

I know Windows transcoding is handled completely differently but that’s as far as my knowledge goes

If someone has windows, might they be able to test and report ?
(I do not have anything Windows here)

If you need HDR tone mapping, please do stay where you’re at.

We have HW SDR transcoding working for everyone (including GeminiLake)
We have HDR tonemapping working for everything except GeminiLake – we see the error.

We have not done any new development for AMD HDR yet.

Does “see the error” refer to GeminiLake or to “everything except…”?
Hopefully the former which would mean a potential fix. If the latter, has support essentially been dropped for GeminiLake? If so, that’s very concerning (I have a DS 920+ as well) because only so long we can stay on an older release before security vulnerabilities start developing.

It refers specifically to the Gemini Lake OpenCL hardware platforms errors you will see in the Server Logs when HDR tone mapping is enabled.

From a security vulnerabilities standpoint, I don’t know of any (not saying there weren’t) any security problems.

wget is redirecting to https://downloads.plex.tv/plex-media-server-new/1.32.5.7516-8f4248874/debian/plexmediaserver_1.32.5.7516-8f4248874_amd64.deb when the server is saying there is an update, and to download manually. You aren’t serving plexmediaserver_1.32.6.7521-24e4dff81_amd64.deb

Actually it just looks like the message in the server update anouncement uses the wrong link, I’ve acquired it with my ebuild, so you are serving it.

Just updated to the latest Plex Beta 1.32.6.7521 and im happy to report that HW Transcoding with HDR Tone Mapping enabled on Unraid 6.12.4 with a 12900K is working again!! woohoo :slight_smile: thanks @ChuckPa and team!

2 Likes

I may well be posting this in the wrong thread but it is closest to my question…

I am currently on PMS for Windows ver 1.32.7.7484.

I saw an update pop up on the Update page but it is ver 1.32.6.7521

The public facing download for Win 64 is 1.32.6.7521

I downloaded it but my current install says it is an older version.

Do I uninstall and install this older version or just stick with what I have.

@JohnAlex Are you observing an issue? It’s up to you if you wish to drop back to 1.32.6 or you can keep 1.32.7 if you’re not observing an issue. With the Windows 64bit installer you can just run the installer to update or downgrade depending on the version you’re installing. There is no need to uninstall.

1 Like

Done. I’d rather use what is on offer publicly.

Thanks for the quick reply.

For the Windows users who are wondering if they should update/downgrade to 1.32.6.7521:

If you are currently on 1.32.6.7468, this is what has been added since, according to the release notes:

  • (Transcoding) Some HW encoded video would not play on Android (#14384)
  • (Transcoding) Hardware transcoding failed on linux machines (#14553)

If you are currently on 1.32.7.7484, this is what has been added since, according to the release notes:

  • (Transcoding) Hardware transcoding failed on linux machines (#14553)

And this is what is in 1.32.7.7484, but not in the other (newer) releases:

NEW:

  • (TerraMaster) Improve multi-volume support when adding folders to libraries.
  • (Transcoder) Enable hardware transcoding by default where available (#14282)

FIXES:

  • (Hubs) User could order a hub before Continue Watching hub (#14236)
  • (Library) In some cases, media item presence and accessibility could fail to be reported (#14307)
  • (Photos) Autotag data was not visible even if photos had pre-existing autotags (#14493)
  • (Photos) Places filter was not visible even if photos had pre-existing place data (#14519)
  • (Preferences) Adjust library section preference text for intro and credits detection (#14152)
  • (Scanner) Episodes with absolute numbering of 264 and 265 could get ignored (#14084)
  • (Security) Certain requests could trigger unwanted notifications (#14524)

Confusing? :wink: