2025-03-31, 06:25 PM
(This post was last modified: 2025-03-31, 06:28 PM by raulo1985. Edited 1 time in total.)
(2025-03-29, 09:39 PM)Ereb_Zx Wrote: Enabling fMP4 also breaks subtitles sync. https://github.com/jellyfin/jellyfin-webos/issues/253
This happens with your jellyfin-web modded build as well, when audio is being transcoded to AAC, after fast forwarding, subtitles get out of sync, or precisely media gets out of sync. It's another strange issue, so far mitigated by using .ts.
Hi. Thanks for this fix, I have a LG C2 Smart TV with the official Jellyfin app and I can say that using hls.js indeed fixed (so far) an issue I had while fast forwarding or seeking (basically it just kept loading, with hls.js it works as expected). I'm using your last modified jellyfin-web (I compiled it from source), so using hls.js 1.6.0. Haven't had issues with playback (neither direct playing or transcoding), audio or subtitles. I can say that everything is working as expected now, and not being able to fast forward or seek properly was an important issue for me. So thanks for that!
A question regarding using fMP4. So far you've suggested to leave it enabled when using hls.js. I've always had it disabled regardless of the client (in my case, WebOS, JMP and iOS app), and never had an issue. And I've also read here at the forums that it's recommended to disable it when using the WebOS app, apparently there's an issue/bug when using fMP4 on that specific client (maybe regarding native hls?). When I used your modded jellyfin-web and tested it with my TV, I didn't have an issue, and I tested it with fMP4 disabled. Do you still recommend to enable it when using hls.js? So far I've mostly tested it with direct play, just only a couple of transcodes (so I can't really say for sure that your fix works as expected when transcoding in all scenarios yet).
Thanks in advance!