fwiw I also ended up rolling back to 1.14.1.5488 and the issue is completely gone
I’m so glad to enter the forums and find this, I was driving nuts trying to understand what the problem was and it’s a relief that you have posted this.
I will try to go back to 1.14. I used to have 24 Transcodes with a P4000, almost no CPU usage and now It’s always at 100% even when I’m doing only directplay but with srt haha.
I rolled back to 1.14.1.5488 on Windows and everything came back to normal, now my CPU is lower than 10% all the time.
Thank you guys, I hope the Plex team can fix this soon so we can have all the new features of 1.15.
Is there team member I can PM logs? A user of mine just finished a stream & I have logs where SRT to ASS on Xbox One caused really high CPU usage again.
Same problem here, on Windows. Rollback to 1.14.1.5488 also fixed the problem. Plex, please fix it 
It would be pretty neat if someone from the Plex team could acknowledge this issue…
3 Likes
Any news please @ChuckPa?
I have no news to report at this time.
I will update when there is something.
The only known workaround I know of is to turn off UPNP on those modems/routers and use manual port forwarding.
1 Like
Sorry but UPNP is unrelated to subtitles transcoding issues (and it’s turned off for me)… Wrong thread?
Also seeing this issue on ubuntu, non-docker. Rolled back to the version specified and it resolved the issue.
UPNP was always off and before that version everything worked right. I checked my Mikrotik again but UPNP is off. I hope this get resolved soon so we can use the awesome new features you have.
Until that I’m sticking with 1.14.
Also I can test my server if you want to try to install a newer version to check if the issue still occur.
Thank you all !
I confirm, I have this issue to with my rysen 1700 and 16 go of ram.
My CPU used by 100 % for one user with SRT To Ass subtitle !
Fix this issue please
1 Like
No-one at plex cares apparently 
3 Likes
Why we don’t get any updates on this problem? You will have a hard time to compete with Jellyfin.
There are no updates coming from me because I don’t have anything to report. Sorry, but I can only report what I know. I have no feedback / information about this getting fixed.
1 Like
I don’t think it’s only about giving feedback @ChuckPa, I think it’s also about caring about your customers (as Plex, not as yourself specifically).
For now we don’t even have acknowledgment that this is even taken care of, or reproduced or getting fixed in the future. In my company, a paying customer is given attention to, whether he spends 2$ or 2M$ he gets the same treatment.
@nawiro I didn’t know about the Jellyfin project but I’m definitely going to see what this project is about, especially because it’s Open Source and we can act on things!
A few folks here and I collected the data.
We know what the root cause is and how to reproduce it.
We even know how (for most users) how to work around it.
I wrote it all up and submitted it all to Engineering.
If I had any influence on scheduling, it would be done.
Unfortunately, it is what it is. Until decisions (above me) are made, this is how it will likely remain. Sad, but true.
6 Likes
Would you mind sharing the work around?
Disable DLNA on Plex and UPNP on your router.
For me it was going back to 1.14.
Disable DLNA and UPNP on router, didn’t work for me with 1.15.
1 Like
