Closed hmonteiro closed 2 weeks ago
jellyfin-bot
commented
2 weeks ago Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
gnattu
commented
2 weeks ago Can you try Chrome and see if it plays fine?
It might be firefox cannot handle hls stream with this high bitrate (due to transcoding).
You may also try disable the "prefer fMP4 Media container" option to see if it helps.
When I'm testing your channel it loads slow but eventually plays in chrome and safari, but firefox will refuse to play it in fmp4 container, probably due to too high bitrate settings.
gnattu
commented
2 weeks ago I can confirm that capping the bitrate to a lower value makes it work in Firefox with auto-loop enabled.
It turns out the Firefox really doesn't want to play your media with fmp4 enabled, reason unknown.
Tested with more your channels, and now I believe at lot of them just loading very slow, because a lot of them do continue playback after a few seconds.
hmonteiro
commented
2 weeks ago Thank you for your help. I have tested unchecking "prefer fMP4 Media container" in both clients and I can confirm it works. This made me wonder if there was some issue with the encoding of the content. I went to check the transcoding folder and verified that when I tick the box it produces mp4 files that I cannot open with VLC whilst if I untick it it produces .ts files that I can open normally.
Does this mean that there is something wrong with my transcoding settings that is leading to corrupt mp4 files during encoding?
gnattu
commented
2 weeks ago Does this mean that there is something wrong with my transcoding settings that is leading to corrupt mp4 files during encoding?
No, I tested across multiple browsers, and it seems like a firefox bug because it does not even play properly with pure software transcoding, capped to 3Mbit bitrate either, and in other browsers like Chrome and Safari, it plays despite the loading speed might be a little bit slow due to the too high default transcoding bitrate.
hmonteiro
commented
2 weeks ago I wonder why it also doesn't work on the WebOS client on my LG TV which is supposedly based on the Chrome engine. I left it running for many minutes, with no luck.
gnattu
commented
2 weeks ago webOS does not use chrome's playback engine and they implemented their own native player, and that one does have known-issues with fmp4. To workaround that it can even accept HEVC codec in ts container, a non-standard behavior.
hmonteiro
commented
2 weeks ago Great, thank you very much for your help.
Feel free to close the issue, unless you feel there is anything else to debug here.
Please describe your bug
When using the M3U tuner, if I atttemp to start a stream, it doesn't work, but doesn't display any errors in the log. If I enable Auto-loop live streams in the provider, I get the first frame and then the video pauses. If I don't enable that option, nothing gets displayed. The log pattern is always the same in both situations, no errors are displayed, ffmpeg continues processing through the stream as if nothing is wrong but the stream doesn't get displayed in the client.
I have tried with 2 different clients:
The same M3U file works correctly on VLC.
Reproduction Steps
All my streams (from here) exibit the same issue, but if you create a new m3u file with the following content (one channel extracted from that source source) and then try to play said stream, it will replicate the issue I am seeing:
Jellyfin Version
10.9.0
if other:
10.9.2
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct