PMS 1.32.6+ HW transcoding issues and corrections

If I may add here?

1.32.6.7521 is CURRENT PlexPass Beta.
1.32.5.7516 is CURRENT Public.

Any previous 1.32.6 and 1.32.7 has been pulled back due to faults

I have asked for a member of the server team to correct the release notes as they are:

  1. Very confusing
  2. Appear to be incorrect
3 Likes

Did you mean to say that 1.32.5.7516 is current public?

MODERATOR NOTE: Fixed my post. Thanks :slight_smile:

1 Like

Never mind - fixed.

Thanks for the reply.

Made perfect sense to a numbnut5 like me so everyone else should understand.

Never mind.

@JohnAlex

Can I have some of whatever you’re drinking?

I NEED IT
(been struggling since last week when this all started)

:rofl:

:rofl: :rofl: :rofl:

I looked at the release announcement page before I posted in this thread and it just totally messed up my head.

Well, that is my excuse.

I got dumped on by a dozen staff who got booted in a restructure in the multinational company I worked for many years ago.

I ended up with marketing and sales jobs in addition to my R&D roles.

Good luck.

Is this available as a docker container image too? I’m at a loss of how to find the docker image tag for these test builds to test on my Synology NAS which isn’t use hw acceleration.

@ChuckPa not sure if you want this reported in here or in a new thread but i kicked off a Scheduled task scan and i get a crash report below and 2 segfaults. This is on my Unraid 6.12.4 12900K machine. I can provide whatever logs you need.

Sep 21 11:12:05 Server-Backup kernel: Plex Media Scan[16773]: segfault at 0 ip 00001490da2fb8cd sp 00007ffea868c4c0 error 4 in libavcodec.so.59[1490da185000+3e0000] likely on CPU 3 (core 3, socket 0)
Sep 21 11:12:05 Server-Backup kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f

Sep 21 11:13:57 Server-Backup kernel: Plex Transcoder[20102]: segfault at 0 ip 0000146c234fb8cd sp 00007ffc315cab80 error 4 in libavcodec.so.59[146c23385000+3e0000] likely on CPU 0 (core 0, socket 0)
Sep 21 11:13:57 Server-Backup kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f

****** PLEX MEDIA SCANNER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.32.6.7521-24e4dff81/PLEX MEDIA SCANNER/6023a941-ce01-4bfa-5474b4a9-b8fdef4d.dmp

@V3nom

Unraid is docker.
Which container base are you using? LSIO? Plex, inc?

I would like the server debug logs ZIP before they’re gone

Plex,Inc docker can be installed from inside the container itself using dpkg

you only need put the DEB file where the container can find it. Get into the container command line, run DPKG.

Im using the Plex, inc container.
No probs, ill grab the debug logs for you now.

@V3nom

Thanks, I’ll look first thing tomorrow

1 Like

Hmm good point. I have been working with containers as do-not-touch the image systems for so long, I didn’t even think about just updating the internals in-place. Thanks. I’ll locate this Debian package and see if I can get hardware encoding working. I suspect I may have other issues though.

I just did another scan with Debug logs enabled, started around 12:00 or so.

****** PLEX MEDIA SCANNER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.32.6.7521-24e4dff81/PLEX MEDIA SCANNER/4b0e072a-b8ed-48d4-a6699880-8b764442.dmp

Sep 21 12:05:47 Server kernel: Plex Media Scan[20149]: segfault at 0 ip 0000152f65afb8cd sp 00007ffe7164f600 error 4 in libavcodec.so.59[152f65985000+3e0000] likely on CPU 10 (core 20, socket 0)
Sep 21 12:05:47 Server kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f

Sep 21 12:10:22 Server kernel: Plex Transcoder[29002]: segfault at 0 ip 000014601c4fb8cd sp 00007ffe68a42830 error 4 in libavcodec.so.59[14601c385000+3e0000] likely on CPU 10 (core 20, socket 0)
Sep 21 12:10:22 Server kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f

I also have another machine, same Docker version, same Unraid Version but the processor is a 9600K an it also get the above 2 segfaults.

Logs attached are for my 12900K Machine. These Segfaults happen daily when the Scheduling runs. Please let me know if you need additional logs. Its easily reproducible so i can get you fresh logs whenever you want.

If you would like the complete unedited debug logs i can message them to you if you like.

HW transcode with HDR tonemapping enabled working like a charm again on 1.32.6-7521.

unRAID 6.12.4
Intel i5-11400 (Rocket Lake-S)
LSIO container latest

Thanks for your work @ChuckPa

1 Like

Can I get confirmation that anything later than 1.32.5.7349 including 1.32.6.7521-24e4dff81 has the needed for HW Tone Mapping fix?

The previous tested working version on Ubuntu amd64 was 1.32.6.7515-873995547 and download page is now showing 1.32.6.7521-24e4dff81 as of this post. The top post on this thread is edited to remove links and I don’t see a date on the edit or the version 1.32.5.7349referenced on the download page.

Thanks!

No

The fix for HW Tone Mapping on Linux is available in the new beta - 1.32.6.7515-873995547

Alright, but it looks like things are moving fast (good!) because BETA download for Ubuntu amd64 is now 1.32.6.7521-24e4dff81

@V3nom

  1. DEBUG logging really helps in these cases .

  2. Looks like you don’t have codecs but cannot tell because the DEBUG logging is turned off.


  • Stop Plex
  • Go into the 'Codecs` directory
  • Delete everything you see in that directory EXCEPT .device_id (your licence)
  • Restart PMS
  • Turn on DEBUG logging for a while so we can understand when it fails again.

@ChuckPa thats strange, i definitely did have debug logging enabled, perhaps i didnt leave it on long enough.

Ok no problem, ill do it all again now after i delete the files in the codecs folder and then ill run scheduled tasks and PM you the logs. :wink:

1 Like