Plex Media Server 1.24.6.5145 - New Transcoder Preview

[enduser]

I did in my initial post.
Server: Mac (Intel)
Clients: shield/web/android
I played with forcing transcoding on MKV that was having an issue and it appears to make a difference with the stops and freezing. I need to do more long term testing.

[jfreiman]

I’m having the same issue trying to download the Windows build. Was this build removed? Will there be another?

{
“errors” : [ {
“status” : 404,
“message” : “File not found.”
} ]
}

[staknhalo]

@Ridley can you answer is it intentional or accident the build are now pulled/links non-functional?

[Ridley]

@staknhalo

@Ridley can you answer is it intentional or accident the build are now pulled/links non-functional?

Apologies; I was off last week. I should have a new build up today.

@mwahlert

Can you explain which drivers and libraries must be updated to enable support for Tiger Lake and Rocket Lake chips?

It’s all internal components that we’ll need to get updated; nothing that you’d have to do as a user.

@lost444

Installed this couple days ago, for me it has been inconsistent, seems that plex will crash

What was crashing? The client or the server?

@karbowiak

Does this updated ffmpeg stack mean that we’ll get VAAPI encoding under Linux, so AMD will work for hardware encoding ?

We already have VAAPI encoding under Linux; what we don’t have yet is the appropriate drivers for AMD.

@Mitzsch

Decoding h264 constrained baseline files is still not done on the gpu, even though they support it.

Hmm, I could switch that on fairly easily. Could you link a sample file? TBH the only reason this isn’t enabled is that I don’t have an appropriate real-world sample to test it with; I’d kinda assumed nobody really used it for on-disk files in practice these days.

@enduser

Curious if the updated transcoder will support AV1 encoded media soon.

I can’t give a specific timeline on this, but we’re working on it.

@enduser

When playing a show or movie, the playback just stops unexpectedly.

As noted in the top post:

@Ridley

If you notice any new issues[…] include your Plex Media Server logs and a sample file that reproduces the issue.

[Ridley]

I’ve updated the links in the top post to point to a new build (1.24.6.5136). There are no new transcoder changes in this build.

[mwahlert]

@Ridley

It’s all internal components that we’ll need to get updated; nothing that you’d have to do as a user.

I realize that, but I am curious as to what components must be updated and why are they integrated into the Plex package? Would it make sense to define them as requirements or dependencies instead so that perhaps we can have a faster MTTR for Tiger Lake and Rocket Lake?

[mwahlert]

@Ridley

We already have VAAPI encoding under Linux; what we don’t have yet is the appropriate drivers for AMD.

@Ridley

No, but I could switch that on fairly easily. Could you link a sample file? TBH the only reason this isn’t enabled is that I don’t have an appropriate real-world sample to test it with; I’d kinda assumed nobody really used it for on-disk files in practice these days.

I’m confused WRT AMD hardware acceleration. Your first statement indicates VAAPI encoding is supported under Linux but the blocker is AMD drivers. Second statement indicates the feature can be switched on with relative ease but the blocker is media files to test with?

[Ridley]

@mwahlert

I realize that, but I am curious as to what components must be updated and why are they integrated into the Plex package? Would it make sense to define them as requirements or dependencies instead so that perhaps we can have a faster MTTR for Tiger Lake and Rocket Lake?

Unfortunately, VAAPI’s versioning system makes it impractical for us to use OS-installed drivers; we would end up incompatible with any driver newer than PMS itself. Additionally, we have to ship our own drivers on any platform that doesn’t ship them itself, and often even on desktop platforms we need to ship our own in order to access newer features than what’s available in stable distros. Loading drivers from the system also tends to result in stability problems, since PMS is built with a non-glibc toolchain for increased cross-platform compatibility. Some users have had success building their own drivers and copying them into the PMS lib/dri directory, but we can’t provide official support for that kind of thing.

@mwahlert

I’m confused WRT AMD hardware acceleration. Your first statement indicates VAAPI encoding is supported under Linux but the blocker is AMD drivers. Second statement indicates the feature can be switched on with relative ease but the blocker is media files to test with?

Sorry, that’s my mistake; the second section was meant to be in reply to @Mitzsch. Fixed in the post now.

[mwahlert]

Understood on all accounts. In any case I and many others are waiting (patiently?) for hardware transcoding to be fully functional on Tiger/Rocket Lake. Hopefully as this is core functionality it will make its way up the priority list sooner rather than later.

[lost444]

Ridley, it was the Server that was crashing.

[DrRickDagIessMD]

HI, just updated to this new build on Windows and its been stuck on updating library for around 10 minutes. Is this expected?

Edit: This cleared almost as soon as I hit send and server has loaded, may just be the size of my library

[ArturoVF]

@mwahlert

Understood on all accounts. In any case I and many others are waiting (patiently?) for hardware transcoding to be fully functional on Tiger/Rocket Lake. Hopefully as this is core functionality it will make its way up the priority list sooner rather than later.

I hope this is a priority as well

[Mitzsch]

@Ridley

Hmm, I could switch that on fairly easily. Could you link a sample file? TBH the only reason this isn’t enabled is that I don’t have an appropriate real-world sample to test it with; I’d kinda assumed nobody really used it for on-disk files in practice these days.

Sure, how should I link it? The last time I have done so, my link was removed by a mod. And you are totally right it´s a pretty old h264 standard but lastly, I encountered it quite often. (trailers from the “user uploaded” menu on thedigitaltheater.com are often encoded in this profile)

[Ridley]

I’ve updated the links in the top post to point to a new build (1.24.6.5145).

NEW:

• (Transcoder) Support for hardware transcoding on Intel Xe/Gen12 (TGL, RKL) GPUs
• (Transcoder) Support for hardware transcoding of H.264 Constrained Baseline media

[mcury]

Updated to this version 1.24.6.5145, and now getting error 404 page not found when trying to open Plex through Google Chrome. It was working before, no changes to NAS configuration.

Checked the service and it’s running and listening…

netstat -an
tcp        0      0 0.0.0.0:32400           0.0.0.0:*               LISTEN

PMS: Synology NAS DS218+ DSM 7.0.1 RC

[Volts]

@Ridley

Yeah something’s wrong with the package. In the FreeBSD build WebClient.bundle is named funny and in a different place and empty.

# previous, works, has contents:
.../PlexMediaServer-1.24.6.5136-5479a7004/Resources/Plug-ins-5479a7004/WebClient.bundle

# new one, broken, empty:
.../PlexMediaServer-1.24.6.5145-dff9113d3/Resources/Plug-ins/WebClient.bundle-dff9113d3

[hmedia]

Will the new transcoder enable support for hardware transcoding on Raspberry Pi 4?

There’s a whole thread here:

Hardware transcoding for Raspberry Pi 4 plex media server

Hello, Can you please add hardware transcoding for Raspberry Pi 4 plex media server? All the best, P.

[Capitaine-Iglo]

So all these bug fixes and features will be available on the next public release ?
Nice job

[enduser]

I get a 404 error not found when trying to open 1.24.6.5145 on an Intel Mac.

I can access from players, but not the web server.

Reverting to previous build.

[Ridley]

The local web app issues are being looked into. Please use the hosted app at https://app.plex.tv for now (this is also recommended in nearly all normal-usage cases).