Jelly can´t play X265 on LG Webos5 on proxmox server

[blueman]

I have the LG app on webos5 (lg cx model 2021) and jellyfin on LXC on a proxmox server with quicksync via IGPU.
When trying to play x265 files on the lg it shows the movie picture and and the circle loops indefinitely and you can´t do anything but restart jeyllyfin. When looking in dashboard it doesnt show that the movie is playing. It seems like it wants to "direct play" and not transcode on the lg. I cant find anything in the ffmpeg trancoding log.


When I try the same file on a computer (browser) It seems to work and transcode. 



Server: jellyfin
Version: 10.8.10
Operating System: Linux
Architecture: X64

A snippet from the log:
[2023-09-23 09:10:53.433 +00:00] [INF] Processing playback tracker : "TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzExNi4wLjAuMCBTYWZhcmkvNTM3LjM2fDE2OTQzMzM1MjkxMDg1-cad1fdc0c0fe4d28938f7ad2552736b4-8f5ec4f2ff6f81d10ad745d1062cdbf3" [2023-09-23 09:11:23.442 +00:00] [INF] Processing playback tracker : "TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzExNi4wLjAuMCBTYWZhcmkvNTM3LjM2fDE2OTQzMzM1MjkxMDg1-cad1fdc0c0fe4d28938f7ad2552736b4-8f5ec4f2ff6f81d10ad745d1062cdbf3" [2023-09-23 09:12:33.349 +00:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets. [2023-09-23 09:12:39.435 +00:00] [INF] Processing playback tracker : "TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzExNi4wLjAuMCBTYWZhcmkvNTM3LjM2fDE2OTQzMzM1MjkxMDg1-cad1fdc0c0fe4d28938f7ad2552736b4-8f5ec4f2ff6f81d10ad745d1062cdbf3" [2023-09-23 09:13:29.819 +00:00] [INF] Playback stopped reported by app "Jellyfin Web" "10.8.10" playing "Live and Let Die". Stopped at "0" ms [2023-09-23 09:13:29.891 +00:00] [INF] Playback stop tracker found, processing stop : "TW96aWxsYS81LjAgKFdlYjBTOyBMaW51eC9TbWFydFRWKSBBcHBsZVdlYktpdC81MzcuMzYgKEtIVE1MLCBsaWtlIEdlY2tvKSBDaHJvbWUvNjguMC4zNDQwLjEwNiBTYWZhcmkvNTM3LjM2IFdlYkFwcE1hbmFnZXJ8MTY5NDg5NTM3NDkwMA11-cad1fdc0c0fe4d28938f7ad2552736b4-45e36260a31a774c7a83f7b33c56c4ed" [2023-09-23 09:13:29.891 +00:00] [INF] PlaybackTracker : Adding Stop Event : 09/23/2023 09:13:29 [2023-09-23 09:13:29.891 +00:00] [INF] Saving playback tracking activity in DB [2023-09-23 09:13:33.348 +00:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets. [2023-09-23 09:13:34.791 +00:00] [INF] FFmpeg exited with code 0 [2023-09-23 09:13:39.420 +00:00] [INF] Processing playback tracker : "TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzExNi4wLjAuMCBTYWZhcmkvNTM3LjM2fDE2OTQzMzM1MjkxMDg1-cad1fdc0c0fe4d28938f7ad2552736b4-8f5ec4f2ff6f81d10ad745d1062cdbf3"

[TheDreadPirate]

We would need more than this snippet to diagnose the problem. But it looks like it was trying to transcode due to the "FFmpeg exited with code 0" mean it ran and stopped normally.

We would need the FFmpeg log out how well it was transcoding and the rest of the jellyfin log to figure out why it was transcoding.

[blueman]

Thank you my good Sir. Of course, please find the logs attached. What do you make of it?

[TheDreadPirate]

Which one of the ffmpeg logs is associated with the problem? Both? From the server side, everything looks fine. The only thing that MIGHT be a problem is that the direct play says that the video is using H264 HIGH instead of main. That MIGHT be a problem, but I can't find a detailed codec support list for that TV. Just vague "AVC" or "H264". But a lot of devices that support H264 MAIN do NOT support H264 HIGH. The client is probably mistakenly playing that back directly instead of asking for a transcode.

This github issue appears to be similar to yours. Check it out, if it matches your problem contribute these logs to the issue.

https://github.com/jellyfin/jellyfin-webos/issues/166

As a workaround, try lower the bit rate until it transcodes? Can you change the quality in the webOS version?

[blueman]

Thanks for the github link. I checked it but seems to be some other issue? I pasted both logs as I didn´t know which one to choose. I check a lot x265 (the james bond ones) and everyone of them are having the same issue.

Yeah sounds resonable. But how can I fix this on the client side? Should I check other x265 files as well?

Because it can´t be on ther server side because the transcoding is working on other devices, correct?

[TheDreadPirate]

The client requests a transcode, not the other way around. The TV SHOULD be requesting a transcode, but isn't.

Which is why I suggested, as a workaround, lowering the bitrate/quality on the TV app to see if it forces a transcode.

Your other option is to re-encode all your media and use H264 MAIN instead of high.