2025-08-29, 04:05 PM
(This post was last modified: 2025-08-29, 08:17 PM by raulo1985. Edited 16 times in total.)
Currently (master branch) JF is using hls.js for the WebOS client in newer LG TV models because of reported playback issues with WebOS native player, but the stable version (10.10.7) is still using the native player. Honestly, I tested JF Web with hls.js and it still had some playback issues in my LG Smart TV (in fact, some that I didn't have previously), so I'm using the native player without much issues. Native player is reported to have some bugs related to using fmp4-hls, and some threads suggest to enable it when using hls.js. If you're using the last stable version without modifications, I would check the fmp4-hls setting and disable it if it's enabled. Fmp4-hls apparently is needed for HEVC and AV1 playback, but I have it disabled and had no issues so far while playing HEVC HDR and SDR movies like the ones in your screenshots.
The other thing is to check your network, to see if something is bottlenecking the bandwith to handle the bitrate of those files (which shouldn't be the case if both files behave differently with similar bitrates).
There's another thing you could try if you know how to build JF from source. Currently there's a new setting available that's only visible using the WebOS client, to use short segments. It can fix some playback issues. Idk if that could be of help regarding your issue, but you could give it a try if you know what you're doing. If you know how to build from source I can tell you which files to modify, so you can enable that setting while keeping JF 10.10.7 (I wouldn't recommend to build the entire JF Web from the master branch. It still has some bugs, at least in my experience. JF 10.10.7 is the most stable and up to date version you should try if you're not helping with debugging). But if you don't know how to build from source and don't have a general understanding of what I said, then maybe it's not a good idea to mess with the source, it could mess your entire setup.
But as stated previously, ffmpeg and JF logs are needed if you need more help.
PS: It's really worth it to learn the basics of Linux, servers are a lot more stable than on Windows in general. Linux Mint or Ubuntu are good distros to start with, specially Linux Mint, since it's pretty similar to Windows, rock solid stable, easy to use and constantly updated. Just a side note.
The other thing is to check your network, to see if something is bottlenecking the bandwith to handle the bitrate of those files (which shouldn't be the case if both files behave differently with similar bitrates).
There's another thing you could try if you know how to build JF from source. Currently there's a new setting available that's only visible using the WebOS client, to use short segments. It can fix some playback issues. Idk if that could be of help regarding your issue, but you could give it a try if you know what you're doing. If you know how to build from source I can tell you which files to modify, so you can enable that setting while keeping JF 10.10.7 (I wouldn't recommend to build the entire JF Web from the master branch. It still has some bugs, at least in my experience. JF 10.10.7 is the most stable and up to date version you should try if you're not helping with debugging). But if you don't know how to build from source and don't have a general understanding of what I said, then maybe it's not a good idea to mess with the source, it could mess your entire setup.
But as stated previously, ffmpeg and JF logs are needed if you need more help.
PS: It's really worth it to learn the basics of Linux, servers are a lot more stable than on Windows in general. Linux Mint or Ubuntu are good distros to start with, specially Linux Mint, since it's pretty similar to Windows, rock solid stable, easy to use and constantly updated. Just a side note.