There are numerous features, both functional and security, that are going to be missing from downgrading 1.19 -> 1.16. My personal suggestion is to use the other workaround I mentioned (dropping playback quality when it stutters, then dropping once again when it starts stuttering again).
The above works for me even on 1.19. It might even work if you drop quality twice right away. Of course, it’s not a perfect solution, but it might be better than giving up those features. If the double drop reduces the quality too much, you can bump up the default playback quality. If you’re direct playing, this bug should not impact you, so it would only happen if you were transcoding. The workaround will not be great if you are transcoding due to subs and want to still watch in original quality though.
FYI, there are some major security flaws that were patched in later versions (1.18.2 or higher, with additional hardening in 1.19). Run 1.16 at your own risk.
Of course, this is such a major bug that Plex shouldn’t force you to choose between their software working or having proper security. The only thing I can suggest is the workaround above and pinging the proper people consistently to remind them that this remains a major flaw. @elan has yet to comment on how the bug has managed to go undiagnosed for over 7 months now, despite it causing people to run insecure versions of Plex Media Server.
Yesterday I try again with version 1.19.4.2935 and have the same problem with LG and Samsung: pause, play, pause, play, pause… go back to 1.16.6.1592 and problem solved. 1.16.6.1592 have some problems with loses subtitles, but at last with the “always on” option for subtitles I can watch TV. For me, after 1.16 Plex is unusable, its a shame.
I got asked to test out the new Early Access Plex client on webOS. It is really a nice client, honestly, but the issue does not seem resolved by it, at least on very preliminary testing
@anon18523487 Are you aware if the Early Access client is going to have a fix for this issue? I assume it’s a PMS issue and not a client one since the “fix” requires rolling that back.
Yep, I just jumped at the early access client hoping I’d be able to use subtitles again on my LG OLED B6 without having to boot up a console to watch some of my content, but no luck still.
Please try my workaround to see if it helps alleviate the issue for you. I am not sure if it will work with the subtitle related issues on webOS 4, but it definitely works for stuttering on any transcode on webOS 3. I’ve tested it multiple times, and I can usually play 10 minutes on the first drop in quality, and then the rest of the movie/show on the second drop if needed.
Every Plex Update
Plex: New update available! Want to see the new Plex Icons?
Me: Oh, lets test this new icons, maybe they solved the problem with subs and TV apps that they introduced with version 1.17+…
10 Min Later: dpkg -i plexmediaserver_1.16.6.1592-b9d49bdb7_amd64.deb
Look at the bright side – they’re gonna have to fix this if they ever want to roll out the new player. …unless they plan to rename the “Skip Intro” button to “Start Stuttering”.
Been watching this thread since it was started. I also have this issue on my LG 49UH661V.
Seems like the devs would rather focus on going through 2 UI/UX regressions, removing pointer support with the magic remote, and adding that online thing I don’t think anybody is using.
Xplay does not have this issue, so it’s not a hardware limitation. Just plain ol’ bad code.
This is why people generally don’t submit bug reports I guess.
i upgraded to the latest docker version from linuxserver.oi - plex version 1.19.5.3112
and i can confirm that it now works for me, no more stuttering and micro buffering when transcoding
