2024-09-18, 06:59 PM
> Can you share your full jellyfin log via pastebin?
There isn't anything especially revealing in there unfortunately. I restarted JF, went to TV (192.168.130.2) to reproduce the issue and came back to get this log: https://gist.github.com/nagisa/54528f36d...8a0e3c6448. You can see here that it doesn't even get to spawning ffmpeg or anything of the sort that which is what would be the usual behaviour when using the web browser on the TV. The client behaves as if the user exit the app. (Which jibes with my observation that the iframe becomes empty, effectively unloading the client.)
> Also, do you have "Prefer fMP4-HLS Media Container" enabled in the WebOS app?
Setting this option either way changes nothing.
> Also, is the content HDR? Does this only happen with some content or with any content?
My particular test files are not HDR. Happens with any video or audio file for me. Photos work fine.
There isn't anything especially revealing in there unfortunately. I restarted JF, went to TV (192.168.130.2) to reproduce the issue and came back to get this log: https://gist.github.com/nagisa/54528f36d...8a0e3c6448. You can see here that it doesn't even get to spawning ffmpeg or anything of the sort that which is what would be the usual behaviour when using the web browser on the TV. The client behaves as if the user exit the app. (Which jibes with my observation that the iframe becomes empty, effectively unloading the client.)
> Also, do you have "Prefer fMP4-HLS Media Container" enabled in the WebOS app?
Setting this option either way changes nothing.
> Also, is the content HDR? Does this only happen with some content or with any content?
My particular test files are not HDR. Happens with any video or audio file for me. Photos work fine.