PMS sends maximum bitrate to client despite asking only for 96k

Plex Media Server
1

Server Version#: 4.145.1

The developer of Symfonium asked me to report the below bug in PMS. PMS is sending clients the highest bitrate of a file when a client asks for 96k, essentially making the transcode pointless as no data is saved :frowning:

Streaming Resource: Reached Decision id=9076 codes=(General=1001,Direct play not available; Conversion OK. Direct Play=3000,This app cannot play this item. The reason is: audio.bitrate limitation applies: 1408 > 96. Transcode=1001,Direct play not available; Conversion OK.) media=(id=8354 part=(id=8467 decision=transcode protocol=http streams=(Audio=(id=12718 decision=transcode bitrate=512 encoder=libopus channels=2 rate=48000))))

Plex says: “audio.bitrate limitation applies: 1408 > 96” then “decision=transcode” and then get mad: “decision=transcode bitrate=512”

This looks like something to report to Plex; they have broken something here with the public API.

Debug log: pms log ($4) · Snippets · GitLab

2

The issue persist on the latest beta

3

I hope I posted this in the right place

4

Hello?

Where are pass subscribers meant to get support?

5

Hello?

6

I could be wrong but from what i see it looks like Symfonium is not identifying itself properly to pms. So it sends the request to perform a transcode, but pms can’t tell what client it is, so it reverts to a generic profile and the bitrate limit isn’t used.

Did Symfonium create their app with plex help or did they do it themselves? I think they did something incorrectly.

7

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