2025-11-12, 02:35 PM
(This post was last modified: 2025-11-12, 03:03 PM by raulo1985. Edited 3 times in total.)
Hi:
What's the current recommendation regarding the prefer fMP4-HLS setting when it comes to the WebOS and iOS clients with JF 10.11.2? I understand that there's a bug on the native HLS player in WebOS that causes playback issues, that apparently are mitigated when enabling the short HLS segments settings while having fMP4-HLS enabled, and leaving it disabled has the trade off that probably Dolby Vision files are most likely going to get converted to standard HDR. Some months ago there was a change on jellyfin-web that made it use hls.js instead of the WebOS native player and I read in a couple of threads that it was recommended to leave fMP4-HLS enabled in that case (since the native player was not used, enabling fMP4-HLS shouldn't have issues and you preserved the capability to play Dolby Vision files without issues), but now that change was reverted due to other issues apparently caused by hls.js (so back to native HLS player again). Should I leave that setting disabled and just accept the trade off with Dolby Vision? Has anyone had experience with the native player (no hls.js), fMP4-HLS enabled and short HLS segments enabled and still experienced playback issues? I'm kind of confused as to what is the recommended way to set my WebOS client now after the changes made to jellyfin-web, and I can't find a definitive official answer.
And the same question regarding the iOS official client. Should I leave fMP4-HLS enabled?
Thanks in advance!
What's the current recommendation regarding the prefer fMP4-HLS setting when it comes to the WebOS and iOS clients with JF 10.11.2? I understand that there's a bug on the native HLS player in WebOS that causes playback issues, that apparently are mitigated when enabling the short HLS segments settings while having fMP4-HLS enabled, and leaving it disabled has the trade off that probably Dolby Vision files are most likely going to get converted to standard HDR. Some months ago there was a change on jellyfin-web that made it use hls.js instead of the WebOS native player and I read in a couple of threads that it was recommended to leave fMP4-HLS enabled in that case (since the native player was not used, enabling fMP4-HLS shouldn't have issues and you preserved the capability to play Dolby Vision files without issues), but now that change was reverted due to other issues apparently caused by hls.js (so back to native HLS player again). Should I leave that setting disabled and just accept the trade off with Dolby Vision? Has anyone had experience with the native player (no hls.js), fMP4-HLS enabled and short HLS segments enabled and still experienced playback issues? I'm kind of confused as to what is the recommended way to set my WebOS client now after the changes made to jellyfin-web, and I can't find a definitive official answer.
And the same question regarding the iOS official client. Should I leave fMP4-HLS enabled?
Thanks in advance!