LG webos new app playback in 15 FPS

Server Version#:1.22.1.4228
Player Version#: 5.11.1
I was using Plex on my LG Oled c9 tv without an issue for a year now. Avoided using the early access version as it was laggy. Today the Plex app was updated and what do you know

  • the playback sucks it is like 15 FPS is the best way to explain it. Files that were playing just fine and smooth yesterday with the older version are not playing well (so 15 FPS instead of 30) today.

Anybody else experiencing this ? My computer still plays them fine via Plex.web so it’s the LG app for sure.

I wish I could roll back …

It happens only with h.265 files (so no direct play and with transcoding of video )

I investigated further and
It seems to transcode some mkv files to h264 mpegts (see print screen with playback info) which causes the problem with playback. This was not the case two days ago with same file and the previous LG app. Something has changed. Now most of my mkv library inn4 k doesn’t playback well.

For some reason some files do not activate the transcoded and playback well see second print screen …

Only difference between them is the protocol used
Http streams well
HLS streams with 15 FPS effect

Why did the app began using HLS For some files and not for others is a mystery to me. This causes the throttling .

I guess it’s a bug any ideas ?

I found a workaround turning off the subtitles which were automatically on solves it doesn’t transcode without the soft subs.

It remains a bug which was introduced with latest LG Plex app as thus wasn’t so a couple of days ago

HTTP means it’s direct playing (video, audio and subtitles do not require transcoding).
HLS means it’s direct streaming (audio being transcoded) or transcoding, video is being transcoded. In this case you’re transcoding 4k to 1080p and the server is probably not keeping up.

The webOS app requires a video transcode if the the audio is being transcoded (would normally direct stream) and subtitles are being displayed, which appears to be the case here.

The first file has EAC-3 audio (Enhance Dolby Digital), but the second and third have AC-3 audio (Dolby Digital), make sure both are enabled for direct playback in the Audio settings for the app. Also try playback without subtitles enabled to see which playback method is used.

Hi. No it’s transcoding mkv 4K to mpeg 4k Also. Not hd

I want to stress it was not doing this in the previous version if the client. I found out it goes away when I deactivate the burn subtitles. Otherwise it is stutters. Again it wasn’t the case previous version. This is why I think it is not good behaviour. But a bug.

The audio is not the problem also tried other formats and the burn subtitle is the problem every time

This is not a bug, this is the behaviour if the video, audio and subtitles cannot be direct played. That said I misread the transcoding, and it’s not not grading the quality (which is expected unless the output quality is changed) and AC3 direct play is allowed, but Burn subtitles is set to automatic, which will only direct play srt and other simple text formats, changing that setting to Only image formats will allow the app to direct play ASS/SSA subtitles (and other supports enhanced text subtitles), but the trade off is they will lack enhanced formatting that can be included with them.

You’ll need to change that setting (if you haven’t already) to allow for direct playback of the files in the second and third screenshots.

I did that already indeed.

So the previous version acted differently ? Until couple of days ago I got direct play with subtitles set to automatic. Maybe the behaviour of the client was changed?

Also just a curiousity - the transcoding that takes place is done by the server which is an extremely powerful desktop and has no problem with it I check the cpu load so I wouldn’t expect it to stutter anyways.

It shouldn’t have and if it was then the bug was in that app and the new app correctly follows the settings. I know the preview app at one point did direct play ASS/SSA subs, but that was changed.

4k transcoding basically boils down to, avoid it at all costs. I would expect CPU usage to be fairly high on most systems, though hardware transcoding would reduce that.