@ChuckPa Here are new debug logs (both server and client) for the current versions.
Full log file: Plex Media Server.log (342.2 KB)
Some important parts that I found in the log file:
At playback start direct play works fine:
Sep 30, 2023 09:28:45.968 [140639437130552] DEBUG - [Req#c0/Transcode] Streaming Resource: Reached Decision id=47 codes=(MDE=1000,Direct play OK.) media=(id=47 part=(id=47 decision=direct play protocol=hls streams=(Video=(id=223 decision= width=1280 height=688) Audio=(id=224 decision= channels=0 rate=0) Subtitle=(id=225 decision=copy languageCode=deu location=sidecar))))
[...]
Sep 30, 2023 09:28:48.950 [140639480851256] INFO - [Req#b8] [Plex for LG] [cremor:hn3o5tiz99m0tzx1cji9svgs] [MDE] Server decision, directPlay: true, directStreamVideo: true, directStreamAudio: true
Then the errors start around here:
Sep 30, 2023 09:29:14.251 [140639480851256] ERROR - [Req#320/Transcode/f5ns50urbnaw9kcgb1p5cre3/64d639e9-b83d-4543-b064-f91b095a068d] [segment @ 0x7f5a975b8040] Failed to open segment 'chunk-00000'
Sep 30, 2023 09:29:14.252 [140639435021112] ERROR - [Req#321/Transcode/f5ns50urbnaw9kcgb1p5cre3/64d639e9-b83d-4543-b064-f91b095a068d] Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory
Sep 30, 2023 09:29:14.252 [140639437130552] ERROR - [Req#322/Transcode/f5ns50urbnaw9kcgb1p5cre3/64d639e9-b83d-4543-b064-f91b095a068d] Error initializing output stream 0:0 -- 
Sep 30, 2023 09:29:14.253 [140639448193848] ERROR - [Req#323/Transcode/f5ns50urbnaw9kcgb1p5cre3/64d639e9-b83d-4543-b064-f91b095a068d] 
Sep 30, 2023 09:29:14.255 [140639534918456] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 355 is 1 (failure)
[...]
Sep 30, 2023 09:29:14.256 [140639426583352] DEBUG - Streaming Resource: Terminated session 0x7fe92e1d2618:hn3o5tiz99m0tzx1cji9svgs with reason Conversion failed. The transcoder exited due to an error.
[...]
Sep 30, 2023 09:29:16.638 [140639435021112] WARN - [Req#31f] Denying access to direct play of part 47 due to terminated session
[...]
Sep 30, 2023 09:29:17.989 [140639437130552] ERROR - [Req#344] [Plex for LG] [cremor:hn3o5tiz99m0tzx1cji9svgs] Playback error occurred. Reason: ServerTerminatedStream, Server terminated stream: Konvertierung fehlgeschlagen. Der Transcoder wurde aufgrund eines Fehlers beendet.
PMS: 1.32.6.7557 (still happening with 1.32.8.7639)
Plex for LG: 5.69.1 (platform 4.9.0) (still happening with 5.85.0)
Also ping @sa2000 because you said that we can ping you with remaining subtitle issues after version 1.32.6.7468 here
Here is everything I know about the issue so far:
- The problem is that after seeking/jumping in the timeline of the file the client shows the following error: “Conversion failed. The transcoder exited due to an error”
- This only happens after seeking/jumping. Normal playing and pause/resume all work without errors.
- This only happens with an active subtitle stream. (I can confirm the error for SRT subtitles. I don’t know about other formats.)
- This happens with all video and audio codecs that I tested. Those are: H.264, HEVC (incl. HDR), DTS (no transcoding!), (E)AC3, AAC. Everything in an MKV container.
- From the logs it looks like the server switches the client from direct play to transcoding for some (wrong) reason. But I’ve disabled video transcoding on the server!
 I assume this “falling out of direct play” then causes the transcoder error if video transcoding is disabled.
- I can reproduce the issue on a LG OLED C9. @Sptz87, who initially created this topic, also confirmed it for a LG C9. Multiple other users also confirmed the bug on a LG OLED CX (see post #75, post #84, post #85). And we also have one confirmation for the LG NANO99 (see post #102).
- I couldn’t reproduce the issue with the alternative LG client “XPlay”. So this is either a bug in the Plex for LG app, or it is a bug in Plex server that is only triggered by the Plex for LG app.
- I also couldn’t reproduce the issue with Plex for Samsung or Plex for Windows. But @Xorag and @sa2000 also get the error on a Samsung TV (see post #84 and post #108) and @kevin_marchant gets it on an XBox (see post #90).
- The issue started with a client or server version that was released sometime in Q4 2022. (I never had this problem before Q4 2022.)
- I currently don’t know of a way to create a short sample clip to reproduce the issue. (The issue isn’t reproduceable with a short clip.)
 But I’ve already provided a full sample movie to @ChuckPa and @sa2000