Same issue with 1.8.2.4209 and plex.tv
Upgraded to 1.8.3, now the behavior has followed to the local web app as well. The issue is with the new web player.
I see this issue with 1.4.4.3495 and Plex.tv player.
I stopped upgrading the server precisely because of bugs like this, but I guess even a version freeze isn’t enough.
1.8.3.4235, problem still present
We really need a fast solution on this. It’s killing our servers!
@ChuckPA said:
It’s only going to cause issues for your machine if it can’t handle 4 concurrent sessions(i know… it’s not funny but trying to find some humor)
1 stream of a 1080p encode: ![]()
on a ~15, 000 passmark cpu? that image is literally just one stream, imagine trying 4 at the same time.
@l3uddz said:
@ChuckPA said:
It’s only going to cause issues for your machine if it can’t handle 4 concurrent sessions(i know… it’s not funny but trying to find some humor)
1 stream of a 1080p encode:
on a ~15, 000 passmark cpu? that image is literally just one stream, imagine trying 4 at the same time.
Same isssue. One transcode hammering cpu.
They haven’t fixed it yet. I don’t know Engineering’s scheduling for this
@ChuckPA said:
They haven’t fixed it yet. I don’t know Engineering’s scheduling for this
But they do understand that this is a high severity issue right? Not to be placed on a back burner behind some weird feature for naming our pictures or something, right?
Agree with @foebik
It made my server unusable.
Hello,
My server is unstable after each time someone watch something on plex.tv
Would it be possible to rollback to an earlier version not impacted?
@foebik said:
@ChuckPA said:
They haven’t fixed it yet. I don’t know Engineering’s scheduling for thisBut they do understand that this is a high severity issue right? Not to be placed on a back burner behind some weird feature for naming our pictures or something, right?
Yes, they do. What’s been happening is the implementation of DASH protocol which replaces HLS. It’s a major change and caused major ripples.
Any update in this issue ? As i still see files being 100% transcoded no matter clients progress.
There has been no word.
So… any news? Average CPU usage and power consumption has gone up 50% while average amounts of playbacks has been the same since this started.

Not even a whisper. Sorry
So is this official fixed? For me it doesn’t occur anymore and I see my transcodes being throttled again, any feedback @ChuckPA ?
Mine seems to be fixed as well, I haven’t noticed it happening for a week or so.
1.9.1 was supposed to have the release note:
- (Transcoder) Corrected throttling of DASH transcodes (#7474)
but it appears to have been lost along the way.