So two weeks ago, everything was playing great. Now, no content will play (only on my WebOS TV) as long as subtitles are ON and are using server-side burn-in.
I’m not sure if the SmartTV (WebOS) client was updated. I’ve tried rolling back the PMS server a few versions, with no effect. All other device types seem to be unaffected (with Subtitle Burn-in set to “Always” for testing).
All content types are affected (h264, as well as HEVC and HEVC Main 10).
Everything plays just fine on WebOS with subtitle burn set to “never”.
Reducing the (local) desired bitrate has no effect, but plays correctly… so transcoding is working.
When I turn on Subtitles Burn-in to Always (on WebOS), I immediately get “Playback Error: An unexpected playback problem occurred.” (tested with both PGS and ASS subtitles)
Hardware Transcoding works fine. I’ve got my PlexPass configured and working.
Plex for other clients is working correctly with Subtitle Burn-in set to “Always” for testing.
Server Version#: 1.41.8.9834
Web Player Version#: 4.147.1 (Working)
Plex for LG Version#: 5.92.0 platform 9.2.3 (not working)
Plex for Chromecast with Google TV: 10.26.0.2578 (working)
Intel GPU:
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD Graphics (rev 04) (prog-if 00 [VGA controller])
DeviceName: Onboard - Video
Flags: bus master, fast devsel, latency 0, IRQ 161, IOMMU group 0
Memory at 60e7000000 (64-bit, non-prefetchable) [size=16M]
Memory at 4000000000 (64-bit, prefetchable) [size=256M]
I/O ports at 4000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [100] Process Address Space ID (PASID)
Capabilities: [200] Address Translation Service (ATS)
Capabilities: [300] Page Request Interface (PRI)
Capabilities: [320] Single Root I/O Virtualization (SR-IOV)
Kernel driver in use: i915
Kernel modules: i915, xe
Good idea. I tried that and no improvement. At this point, I’m fairly certain it’s Plex for WebOS (LG) that is broken. It seems like everything else can play and burn subtitles. But for some reason the WebOS client cannot properly inform the server that subtitles need to be burned during content negotiation. I’ll update my original post and move it to “Smart TVs”.
alllllmost. The WebOS client is (in fact) incapable of playing PGS and ASS subtitles. That’s never been a problem. It’s always used server-side burn-in to play them. What is new is the error screen (with the same settings).
I tried your suggestion of disabling both DirectStream and DirectPlay in the client. It had no effect. Since we’re focusing on the client now, I enabled server logging and will attach it here:
@SE56 Even files that used to play without issue are now unable to play. The problem has started with either an update to WebOS or Plex for WebOS or both, but there’s no way to roll back to an older version, so I’m unable to test.
Yes. Tried that too. Even tried to turn off hardware-accelerated encoding entirely. Had no effect. So I left the settings enabled since they work for other clients just fine. At this point the problem seems to be entirely on the client side.
i’ve been getting similar issues. i can play anything i want on any device except my LG tv, and its apparent it’s only affecting shows that have subtitles that require transcoding. diving into the logs shows the following:
I think that the error starts at the very beginning with the “ET”, attempting the transcoding, when I think it should be “GET”. It attempts this 11 times before giving up and spitting out the “playback error” message. This should really get passed up the line somehow to some devs to get this fixed.
I think the missing first character ET ... is a red herring. I’ve seen a few other posts on here about it. Apparently it’s not important enough for plex to fix. But I promise that it isn’t the problem. It’s been that way for a long time.
I did finally give up and I factory reset the LG TV… I had already deleted the app and reinstalled it. Logged out and back in… all of the typical troubleshooting steps. But this time I used the TV menu to factory reset… AND IT WORKS NOW! Plex is 100% working with and without subtitles, HDR, HEVC… all of it.
I also factory reset, but no luck. Whenever Plex server decides to burn subtitles I get a playback error. Disabling Subtitle burn on the player fixes it for some media but makes other media unplayable. Disabling subtitles completely circumvents this issue but that’s no good if you want to watch foreign media.
Hello, I confirm the problem with burn-in subtitles on Plex client for WebOS. It’s related to recent plexmediaserver upgrade. I’ve upgraded to 1.42.1.10060 on Debian and can’t watch any movies with burn-in subtitles (like PGS). Rollback to my previous version 1.41.6.9685 resolves the problem. Transcoding itself works fine. Only burning-in subtitles doesn’t work.
A lot of my media uses the “ass” codec for subtitles and it was always erroring on my C2 OLED when trying to play with them enabled for a while now, but rolling back to 1.41.6.9685 has fixed the problem for me as well.
The original problem was resolved with a WebOS factory reset. (The whole TV, not just Plex) I recommend opening a new thread with whatever logs you can find since this is a complicated problem that involves a few different versions of a few different projects.
