Glad to hear 
Let me know if at some point there’s a private release I need to test (I don’t know if that’s a thing at Plex)
He does things in a big way HAHA
It will be part of a release because he will have passed it to me . If he sees the problem is solved and I see the problem is solved then he will push it to release. This is of sufficient importance to not delay.
4 Likes
Any news on this?
Also as you earlier blamed this on docker, I have tried now to run Plex on ubuntu vm, clean install, single media file, and problem still reproduces, so It’s not Docker problem.
1 Like
There have been some improvements. (Look at the release notes for details)
I know of some cases where it’s been resolved.
That’s all I know.
As you all know, I can’t reproduce it on the equipment I have so there’s nothing I can contribute.
Are we again going into this discussion of it has been resolved/I can’t reproduce?
The last PMS release is dated from 9 days ago, you sent everything to engineering 5 days ago (at least that’s what you said)… So no it has not been resolved for anyone… At least not the issue on this thread (SRT → ASS conversion…)
I hope this still stands.
I am telling you what I know.
If this isn’t sufficient, you are more than welcome to contact plex directly.
I understand everyone’s frustration but, please understand, I have no control over engineering’s schedule, nor am I here to be the whipping boy.
Thank you for your understanding.
1 Like
I agree with @RomRider42
I asked about stuff discussed in this thread and you have sent for developers and now you say something was fixed even if there was no release after logs where uploaded…
BTW @ChuckPa, why is this topic unlisted?
I don’t want to speak for ChuckPA but perhaps he meant keep an eye out on the release notes of forthcoming releases?
He said "There have BEEN some improvements. "
And that’s quite possibly true; and it’s also quite possibly true that haven’t been released as of yet.
Development / test / release; improvements could be in development, could be in test, could be queued for a future release.
Let’s stop arguing about communication issues.
We all hope for a fix (for the past 4 months now!), and hopefully now this is of sufficient importance to not delay.
But, I’m still wondering why this topic has been unlisted 
Don’t know why it’s unlisted but I listed it.
As for WHAT is happening in the PMS code, I understand it.
If I could fix it, I would but I can’t. I’m not in the Engineering dept.
I will not debate which needs are greater than others.
However, one might argue that everyone having TheTVDB metadata with the new API is more important than the subset who experiences this problem.
Again, and hopefully to end, I do not have influence or visibility into Engineering resources and scheduling.
Thats why I asked for status, because there was no release
FYI, just tested the latest version 1.16.4.1469-6d5612c2: it still doesn’t work 
@ChuckPa something maybe to add to your discussion with devs: At first it uses 100% of one core, then whenever you seek in the video (like going forward or backwards by 5min for example) it adds 100% on one more core. Every time you seek that happens until all the cores are at 100% and kinda makes the whole host completely unusable.
Regarding “Still doesn’t work”. — It’s not going to get fixed immediately. Please don’t keep pushing ? I’m the one who sees the posts and all that happens at this point is I become annoyed. Sorry, but that’s how it is.
It took me time to figure this out and get pushed into Engineering. As I have stated countless times, I have no visibility or influence in Engineering resource scheduling.
When it’s fixed it most likely will be in the release notes. Until then, there’s nothing for users to do but wait.
@ChuckPa, @darcilicious I wasn’t complaining, just being helpful for folks on this thread
I only tagged you on the other part of the message with something that could be somewhat useful new information.
1 Like
Experiencing the same issue here, so I found this thread.
Fully read through it, and I can attest that @ChuckPa is the worst customer service rep I’ve ever seen.
And, although not his fault as it’s the dev team’s fault, the fact that this issue hasn’t been resolved for close to 6 months is a disgrace.
But hey, I guess creating a whole new desktop app that nobody asked for was more important than fixing a regression that can literally damage users’ computers, and cost them money by rising their electricity bills.
What a freaking joke.
Pinging @elan for the love of god.
6 Likes
