And then it went silent again, anyone knows how to get in contact with some high enough in Plex to get some attention, most of us are paying for a service after all…
Let me join the “same issue here” parade in order to try to get some more attention. LG OLED model 2016 here with WebOs 3.
Hi everyone, like you have i have this problem aswell.
Iv already listet my problems in my earlyer post.
I would like to help finding out which exact version this breaks in.
but for that i need to know the exact version numbers for plex media server
example that works: 1.16.3.1402-22929c8a2
does anyone have a complete list of pervious versions numbers?
if not maybe we can try and compile our own:
let me know what you think
Best Regards
Footlocker
Hi, for me last working version was 1.16.0.1469-6d5612c2f-x86 hope this helps
I just found an older deb server file for my Debian server. So far it works fine.
Download, rename it to plex.deb and install it using the command dpkg -i plex.deb. Since I was at it, I decided to put together a list of working versions for different platforms so none has to google them:
Ubuntu/Debian amd64:
Plex 1.16.5.1488 Ubuntu/Debian amd64
Windows x86
Ubuntu/Debian ARMv7
Plex 1.15.8.1198-eadbcbb45 Ubuntu/Debian ARMv7
Ubuntu/Debian ARMv8
Plex 1.15.8.1198-eadbcbb45 Ubuntu/Debian ARMv8
Mac
1 Like
@anon18523487 Been a week since I last pinged you, though you never answered those questions. Pinging you now, I saw another Plex major version update (1.18 -> 1.19) as well as a webOS client update and still no fix.
Again, would be good to have some more open communication here. I’m just trying to understand the timeline or path to getting this bug resolved. You have to understand, from our side, there seems to be no visible progress whatsoever over the last 4 months.
People are now reporting issues of varying impact on webOS 4 and webOS 5. Those seem to be isolated to transcoding with subtitles, but the behavior is the exact same. The new X lineup for LG TVs is coming out very soon, and imagine someone buying a multi-thousand dollar product from one if, if not the top TV line, during a period where almost is staying at home, only to learn it struggles massively as a Plex client. It would be a very bad look for Plex. Of course, you guys did just enable your own Movies/TV on the webOS client, so maybe you don’t care and were prioritizing studio partners over paying customers?
@elan pinging you to get some understanding on how a confirmed bug remains undiagnosed despite being over 4 months after confirmation (and 6 months since being first introduced 3 major versions of PMS ago). Is the dev team just not interested in supporting LG TVs? There is a very noticeable lack of communication or effort from the devs here, even compared to other bugs found throughout the Plex forums.
1 Like
Unfortunately, I have no news. The issue is open with the server team to investigate, but there is nothing to share so far. I promise that as soon as I hear something to share, I will.
Those are different issues so please keep those discussions in their own threads and not bring it up here to muddle the situation.
@anon18523487 Are there any special builds we can test out, maybe with some enhanced logging that help isolate the changes made from 1.16->1.17 that introduced this issue? Do the server teams have plenty of access to the impacted webOS devices, which is why they are not communicating with us?
See, if you told me they have figured out the bug, but just haven’t been able to fix it yet, that’s different. That means that a fix will come at some point down the line. However, by indicating that they haven’t been able to diagnose it and are not interested in troubleshooting with us, it at least seems like they’ve just thrown their arms up in the air and given up, especially considering the amount of time that has passed.
It would be good to know which steps the dev team are actively taking, which causes they have eliminated, what they suspect, if there are workarounds (seems sometimes changing the bitrate of the transcode helps for a temporary basis, but other times it does not), etc.
The reason I’ve been pinging you every week/every two weeks is simply for visibility. Once the diagnosis of the bug is done, it gives comfort to us that the problem will be fixed; however, with a bug that remains undiagnosed for over 4 months and no communication, it honestly feels like they have no interest in actually fixing this.
Basically, tl;dr, has the status of this bug changed even remotely in the last 4 months?
Hi
The issue of buffering is not fixed on PLEX Server PlexMediaServer-1.19.1.2645 and LG latest client.
the issue is related to transcoding SRT subtitles, see attached PLEX server Logs.
ThanksPlex Media Server—.log (235.9 KB)
@anon18523487 It’s been 2 weeks since your last message (and again, you didn’t reply to my follow up questions). Can you give us the latest status update? Did the dev team get closer to diagnosing the issue? Do they have some builds with enhanced logging that we can test out?
I noticed that when the issue occurs, I am able to temporarily fix it by downgrading the quality. So, I paused a movie, with my default speed at 8mbps. I start it up, audio and video stutter. I then downgrade to 4mbps, watch 15 minutes, then the issue occurs again. I then downgrade again to 3mbps, and am able to watch more. The amount of time before the issue occurs again seems variable. I assume the dev team is already aware of this due to the heavy testing they must be doing, right? Still, would be curious to know if there was a way to “smoothen” this workaround (make the fix last longer). It’s a very rough way to watch a movie, but at least it allows you to watch it compared to before, where pausing may as well have meant you needed to restart.
Server Version 1.18.8.2468
Player Version 4.29.3
webOS 3.8.0
Hi. I just wanted to say that I too am effected by this issue.
I’d like to note that I actually was on a 1.16 server before this, but had to upgrade due to another Plex on LG issue. So I seem to be screwed either way here. Not having the letters index is not something that sits well with the other person in the household, and not being able to fast-forward on anything that requires transcoding to play is annoying to me since most of my media does due to the lackluster subtitle support (I’m not faulting Plex on that point, though).
Any update would be appreciated.
1 Like
Here are the download links for the last working version, 1.16.6.1592-b9d49bdb7, before version 1.17 broke Plex for LG TVs.
Windows:
downloads.plex.tv/plex-media-server-new/1.16.6.1592-b9d49bdb7/windows/PlexMediaServer-1.16.6.1592-b9d49bdb7-x86.exe
Mac:
downloads.plex.tv/plex-media-server-new/1.16.6.1592-b9d49bdb7/macos/PlexMediaServer-1.16.6.1592-b9d49bdb7-x86_64.zip
Synology:
downloads.plex.tv/plex-media-server-new/1.16.6.1592-b9d49bdb7/synology/PlexMediaServer-1.16.6.1592-b9d49bdb7-x86_64.spk
Qnap:
downloads.plex.tv/plex-media-server-new/1.16.6.1592-b9d49bdb7/qnap/PlexMediaServer-1.16.6.1592-b9d49bdb7-x86_64.qpkg
FreeBSD:
downloads.plex.tv/plex-media-server-new/1.16.6.1592-b9d49bdb7/freebsd/PlexMediaServer-1.16.6.1592-b9d49bdb7-FreeBSD-amd64.tar.bz2
Ubuntu/Debian:
downloads.plex.tv/plex-media-server-new/1.16.6.1592-b9d49bdb7/debian/plexmediaserver_1.16.6.1592-b9d49bdb7_amd64.deb
Fedora/CentOS/SUSE:
downloads.plex.tv/plex-media-server-new/1.16.6.1592-b9d49bdb7/redhat/plexmediaserver-1.16.6.1592-b9d49bdb7.x86_64.rpm
2 Likes
Not much to contribute. Same issue here with my LG B6, stuttering as soon as I fast-forwarded, and wouldn’t resolve unless I restarted videos from the beginning (resuming from xx:xx wouldn’t solve the problem).
I downgraded to 1.16.6.1592 as others here suggested and the problem went away.
Some things I noticed:
- Switching from original to transcoding didn’t make a difference, and I tested several bit-rates. My computer is plenty good enough to handle those, so it wasn’t a CPU bottleneck.
- I didn’t try deactivating subtitles, perhaps I should have. I do watch most stuff with subtitles however and as far as I know, I haven’t had this issue with non-subtitled stuff.
Thanks for the fix guys!
Hi and welcome
Glad we could help.
just to clarify, it is NOT a fix but a temporary workaround.
at some point we will need to update/upgrade our PMS servers, maybe @anon18523487 can give us a status update.
I also had the problem on my LG. Thanks for the workaround! I hope Plex will implement a fix soon.
@anon18523487 You might have missed my ping a week ago, however pinging again so you can provide me and the additional posters above a more up to date status of the bug.
@nocrophile, Thanks, but how can I downgrade on Synology? I got this error message (bild attached)
I saw the ping. I don’t have anything more to share at this time. The issue is filed with the team and is being investigated.
Is there anyone who knows how to escalate this issue to some of the responsible at the Plex organization? Can’t believe this is a kind of support they would be proud of, looking at all the nice words used on the homepage…
1 Like
Hi MovieFan,
I am replying you since you seem the one who are trying to help us and get the rid of this annoying issue.
I see that this thread is up since a long time as they never fixed it. I can share my experience. At the moment I have Plex server on a Synology DS918+, fully updated:
Plex Server version1.19.2.2737
No issues from any player but my local LG TV:
PLex for LG 4.29.3
webOS 4.1.0
I tried remotely and it works fine (from PC Web browser or Mobile app). It definitively has a problem with LG tv player. I am uploading my debuggin log Plex Media Server Logs_2020-04-29_22-13-35.zip (4.0 MB) . I hope someone could help all us out…
I just can say that this problem occurs only with some kind of videos. So, not every file is impacted. Actually I do not understand which could be the discrimination in here.
I tried of course reboot to NAS, TV, router, anything: no way.
I keep my all stuff very updated, but this issue seems to be up since a very long time. If could help, I remember that it started since a 1.16 or 1.17 server release. After a certain update, it began this behaviour. In that case, I think I worked it out avoiding to use a kind of subtitle. So, I am not sure this is the same problem…
Hope I could help you to help us with this.
Thank you very much.
