Strange, I have the file playing then skip multiple times, no need to press play again.
But it will hang “spinning”, quite easily reproducible for me.
Very weird you cannot reproduce.
Have you done a force kill of the Plex app in WebOS ?
I’ve seen it get all ‘junked up’.
I just reproduced that.
It plays perfectly but will NOT seek.
That’ll make them scratch their heads. 
It’s weird yeah, but I’ve only noticed this in that test file. I can seek/jump in my files just fine - until the playback completely stops with that (wrong) transcoder error message.
That file is ripped from the BluRay so it’s not like it’s a ‘questionable source’ 
So is there anything else I can do to help find the original issue?
I’m working on it.
I’m ripping the BluRay again. The lack of seek tells me there must be a problem with the original rip.
Yes my TV gets physically powered off every night.
I still can’t seek/jump in this file.
Another thing I noticed is that the Plex server doesn’t generate chapter preview thumbnails for this file (neither the first one nor the new one).
I’ve also tried to test the Match of the Day 2.ts file from @e10kstarfire but I can’t get that one to even show up in a library. My Plex Server log shows errors when I add the file:
Nov 26, 2022 09:58:23.679 [0x7fca48f88b38] INFO - Library section 1 (Movies) will be updated because of a change in "/data/User/Movies/Testfile.tts"
Nov 26, 2022 09:58:28.805 [0x7fca48ad2b38] WARN - [Req#6cbf] QueryParser: Invalid field 'sectionID' found, ignoring.
Nov 26, 2022 09:58:28.805 [0x7fca48ad2b38] WARN - [Req#6cbf] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Nov 26, 2022 09:58:28.805 [0x7fca48ad2b38] WARN - [Req#6cbf] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Nov 26, 2022 09:58:28.808 [0x7fca48d46b38] WARN - [Req#6d17] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Nov 26, 2022 09:58:28.808 [0x7fca48d46b38] WARN - [Req#6d17] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Is there maybe somewhere a library of other test files I could try? Best would be MKV with H.264 or H.265 video, E-AC3 audio and SRT subtitles, because that would represent most of my media.
Off topic, but this is not good for the life expectancy of an OLED TV. OLED TVs run “pixel restoration” processes while they are off.
Yes, but AFAIK it typically does this after you put it into standby which will be a number of hours before it’s turned off.
Can we get back on topic please?
Thanks
Tried the gods2 testfile and can reproduce my spinning circle issue easily enough: Start playback, hold down skip forward until it reads say 5 minutes, let go, and it sits there spinning away.
No transcoding occurs during this period (checking the folder it uses under cache).
Client 5.50.1, Platform 6.3.1, FW 03.33.11 on an LG C1
ps: this plays as direct stream video and dts-ha ma to aac transcode
I have the same firmware on mine. LG C1 48" (2021 model).
I’ll take this up with the android tv team.
I assume you mean WebOS TV team? LG TVs are not running Android
I agree. The topic is about playback on C9 completely stopping and showing a (wrong) transcoder error message. Maybe that problem has the same root cause as the spinning circle on C1. But please don’t forget about it if it’s something different!
If you upload a sample file I can see if I can recreate on my C1, may help narrow down the issue.
Folks
My apologies about the previous test file. 
I had forgotten to rewrite the MKV info at the end of file before uploading.
That’s what was blocking seek-rewind.
This video header still says full run length but actual video in the file is 8 minutes.
This is DirectPlay on the LG C1.
https://drive.google.com/file/d/1FDBk7gFMXD95BQ4BEu_KrzysZtjYwb3T/view?usp=sharing
If you want me to continue my spinning circle issue on my original thread and leave this one with the transcoder error let me know.
Maybe it would be better to keep the two separate from an interaction point of view but the two are closely intertwined. I’m trying to help out the devs when they come in here for info.
1 Like
I can now seek in your new test file. But I’m unable to reproduce the error from the topic with it.
I’ll try to create a sample file on the weekend.
@ChuckPa Sorry for the late reply. Although I now have a way to reliably reproduce the error with a specific file, I’m unable to create a sample for it.
I’ve tried using mkvtoolnix to create the sample, but the error doesn’t happen with it. I’ve also tried to create the sample with dd, but the file isn’t seekable with that. And if I run the dd sample through mkvtoolnix to fix seeking the error doesn’t happen.
But mkvtoolnix doesn’t “fix” the error by itself. Because if I just remux the whole file with mkvtoolnix then the error is still reproduceable.
Do you have any other idea how I could create a sample?
I could also provide the whole file if you want. It’s about 4 GB.
Otherwise, here is some additional information that I found:
The file has a very simple video track (4445 kbps 720p H.264) and standard audio track (1536 kbps DTS 5.1). But it’s important that I enable the SRT subtitle tack. If the SRT subtitles are disabled the error does not happen.
But no subtitles are shown in the locations that I seek to. The subtitle track only contains forced subtitles, so there are just a few lines in it.
