A) I don’t want the server to burn subtitles. I even have the “disable video stream transcoding” setting enabled on the server.
B) No, the TV does not need to burn SRT subtitles. I can watch all my media with SRT subtitles with direct play (as you can see in the screenshot in my post above) as long as I don’t seek during playback.
So I assume the bug is that something switches to subtitle burn in although it is not actually needed?
Yes, without subtitles I don’t have the problem. I’ve already written that before.
But that doesn’t help me. I want/need the subtitles.
But why is it even falling out of direct play and switching to direct stream? If it wouldn’t switch to direct stream then it also wouldn’t need to burn the subtitles.
I meant, why does Plex fall out of direct play after seeking, even if it played the file for an hour in direct play before?
As far as I see it right now, this bug (falling out of direct play) only happens if all of the following conditions are true:
Play a file with Plex for LG. @Sptz87 and I have a LG C9, but further down multiple other users also confirmed the bug on a LG CX (see post #75, post #84, post #85).
I couldn’t reproduce the problem with Plex for Samsung or Plex for Windows. But @Xorag also gets the error on a Samsung TV (see post #84).
Have an active SRT subtitle stream
Seek/jump in the timeline of the file
Have a app version (or maybe server version) that was released sometime in Q4 2022.
(I never had this problem before Q4 2022.)
Especially the last point indicates that this is a bug in Plex.
This “falling out of direct play” then causes the transcoder error if video transcoding is disabled.
Given the 4 conditions you’ve found , which all must be true for the problem to occur,
I’ve not seen others report falling out of DirectPlay. With all I test, it’s never happened to me on my LG with all the interim builds of PMS I’ve tested as well , so I’m not inclined to suspect the server
LG has been doing a lot of firmware updates on my TV in the past few months so maybe ??
SRT w/ seeking with DirectPlay – If this were broken then every player regardless of platform would be reporting the problem.
App version Q4 2022 ? There’ve been releases since Q4 2022. What’s the verdict there? (App bug is the most likely candidate)
Yes, I also think that this is a LG client specific bug.
I currently have LG C9 firmware version 05.30.25 installed, which is the latest version. That version was released Dec 14, 2022.
I also had this problem with firmware version 05.30.11 (see post #12), which was released Oct 23, 2022.
I’m not sure if I saw the problem before Oct 23, 2022, so I can’t say if a firmware update might have triggered it. But I doubt it. How could the LG firmware influence when the Plex app switches to direct stream?
As I wrote, I also can only reproduce this with the LG app, but not with Windows or Samsung apps. So not all Plex apps are affected.
Of course I’ve updated to newer versions since then, but the problem remains. I just mentioned this because I first noticed this issue in Q4 2022. So maybe a change in an update that was released in Q4 2022 triggered the bug. That would be a release of Plex for LG app between 5.48.1 and 5.49.3. (Maybe starting earlier if I don’t remember the timeline correctly.)
@ChuckPa I’ve had (and am still having) a bad experience with the Plex app on Samsung TVs too. But that’s not the point.
What do the Plex for LG app developers say to this bug? Especially about post #68.
Also, there are client errors in the log file (see post #60) before the server tries to switch to transcoding. Could those not be an indication as to why the client aborts direct play?
This started happening to me on my 2018 Samsung TV after I upgraded Plex Media Server from 1.31.3.6868 to 1.32.3.7162. Using the older version of PMS, playback on the Samsung TV was totally fine. However, ever since upgrading, I’m getting Conversion failed. The transcoder exited due to an error either near the end of every playback, or at the end of the playback. The server logs show a request to transcode the media that was just playing, even though the playback is nearly finished or already finished, and the media was direct playing/direct streaming.
I’m experiencing the same issue. I have an LG OLED C2 with the latest firmware and the internal LG WebOS Plex App. PMS on my Synology NAS is on the latest version as well.
I can watch nearly everything until a couple of minutes before the end I get the “Conversion failed. The Transcoder exited due to an error.” message. Everything I watch is direct streaming/playing. Started happening a couple of weeks ago.
When I disable subtitles for a movie/show everything works without issues. Must be something that changed with the subtitle handling?
Plex really needs to copy the subtitle handling from Emby, everything works wonderfully there. Even on WebOS, there are no limitations that forces to burn-in.
Apr 06, 2023 21:11:37.163 [0x7f0350638b38] DEBUG - Completed: [127.0.0.1:59598] 206 PUT /video/:/transcode/session/xdxewo5wqafr7tulmzf0vn8k/a3154d02-39be-48f0-985b-a5c641973b2d/progress?duration=7602.560000 (9 live) #5e6 0ms 371 bytes (pipelined: 1) (range: bytes=0-)
Apr 06, 2023 21:11:37.163 [0x7f034c561b38] ERROR - [Req#5ea/Transcode/xdxewo5wqafr7tulmzf0vn8k/a3154d02-39be-48f0-985b-a5c641973b2d] [segment @ 0x7fd007d7f980] Failed to open segment 'chunk-00000'
Apr 06, 2023 21:11:37.164 [0x7f03482c9b38] ERROR - [Req#5eb/Transcode/xdxewo5wqafr7tulmzf0vn8k/a3154d02-39be-48f0-985b-a5c641973b2d] Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory
Apr 06, 2023 21:11:37.165 [0x7f034acdfb38] ERROR - [Req#5ec/Transcode/xdxewo5wqafr7tulmzf0vn8k/a3154d02-39be-48f0-985b-a5c641973b2d] Error initializing output stream 0:0 --
Apr 06, 2023 21:11:37.165 [0x7f034aadcb38] ERROR - [Req#5ed/Transcode/xdxewo5wqafr7tulmzf0vn8k/a3154d02-39be-48f0-985b-a5c641973b2d]
Apr 06, 2023 21:11:37.167 [0x7f035086eb38] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 413 is 1 (failure)
So your transcoder crashes with a segfault, while mine “just” exits with an error code.
From your other thread it seems like you have the crash at the end of files, after the last subtitle line is displayed. That is already discussed in other threads. This thread here is about the same error message, but when it appears after seeking in a file.
