Why is my local session being transcoded?

Plex Players Desktop Players
,
1

Server Version#: 1.25.6.5577
Player Version#: 1.41.0.2876-e960c9ca

When trying to play 4K stuff locally on a Mac desktop it gets transcoded. It doesn’t for, say, iOS devices. The logs say:

{
“type”: “log:message”,
“level”: 2,
“message”: “[MDE] Starting analysis of 4k (mkv, hevc, truehd, 153, main 10)”,
“time”: “2022-03-15T23:48:39.412Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[MDE] Analyzing direct play”,
“time”: “2022-03-15T23:48:39.412Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[MDE] Invalid profile property; bitrate: 58783 > 8000”,
“time”: “2022-03-15T23:48:39.413Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[MDE] Cannot direct play: validateProfileProperty:maxBitrate”,
“time”: “2022-03-15T23:48:39.413Z”
},

Which is fine, but I can’t find a player setting to tell it not to max the bitrate at 8Mbps. This is not done to iOS devices on the same network:

image

2

The Quality settings on the left side under the Plex for Mac section of settings

3

Well, yes, I had found that one. However, it’s set to “Maximum”, I’m still getting 8Mbps. It’s like it doesn’t even know 4K exists.

image

4

@BigWheel does that update make sense? Can the Mac desktop player not handle 4K or something?

5

Sorry i missed previous reply. the settings it more about the bitrate than the resolution. Maximum should be able to play 4k fine.

Question: though it is showing local I am wondering if you have “Limit remote stream bitrate” set on server in the remote access settings

6

Yes, and disabling that seemed to allow it to direct play. I think I saw a thread elsewhere that suggested this was a bug that another user had? I do have 192.168.0.0/24 defined as a local subnet (and it’s the same subnet that the Plex player and server are on).

7

Yeah that is possible. All the entries you have in the LAN networks setting are all comma separated like 192.168.0.0/24,192.168.4.0/24,192.168.8.0/24 correct?

8

There’s only the one, which is the same as the server’s subnet.

image

9

if it is the servers subnet why have it there at all?

( though does still seem like a bug as I would think it should treat it the same as blank if the only one )

10

Because in THIS thread (which seems to be the same bug I was hitting):

it was suggested as a fix. Now as far as it goes, I am running the server from a docker container on my NAS, but again using bridge networking and the client was seen as local. So this does seem to be some sort of bug in this configuration.

11

ok so on your server in remote access settings the IP that is shows as private is that same subnet?

i does seem like a possible bug I’m just trying to understand the whole picture.

12

Yes. Server is 192.168.0.69/24 (nice) and the client is 192.168.0.42/24. Same VLAN, same subnet.

14

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