Live TV

[TheDreadPirate]

The initial delay appears to be from jellyfin probing the stream to see what is in it. I'm assuming to see the codecs and container used to help determine if transcoding needs to occur. The initial probe didn't find anything in the stream. Probably because the provider hadn't started serving the stream yet so Jellyfin added a 3 second delay before probing again to allow the provider to actual start streaming content.

Code:

[2025-04-05 12:58:35.741 +02:00] [INF] [18] Jellyfin.LiveTv.DefaultLiveTvService: Streaming Channel "m3u_7147f8ddcd474314e2f449260d6d98452a47ff8e4b0ffde20ed869594d0d86a2"
[2025-04-05 12:58:35.785 +02:00] [INF] [18] Jellyfin.LiveTv.TunerHosts.M3UTunerHost: Live stream opened after 0.0022ms
[2025-04-05 12:58:35.786 +02:00] [INF] [18] Jellyfin.LiveTv.DefaultLiveTvService: Returning mediasource streamId "2a47ff8e4b0ffde20ed869594d0d86a2", mediaSource.Id "2a47ff8e4b0ffde20ed869594d0d86a2", mediaSource.LiveStreamId null
[2025-04-05 12:58:35.786 +02:00] [INF] [18] Emby.Server.Implementations.Library.MediaSourceManager: Waiting 3000ms before probing the live stream
[2025-04-05 12:58:40.221 +02:00] [INF] [18] Emby.Server.Implementations.Library.MediaSourceManager: Live tv media info probe took "4.4355143" seconds

It does not appear to be transcoding, which also means that the client will be directly connecting to the live TV stream, thus requiring another new connection and a new delay. If that initial probing delay was caused by something on the providers side, that essentially means that 9-10 seconds is possibly the minimum start time for this provider. Which does match up with the logs. 5 seconds after the above log the server reports that Jellyfin Media Player started watching live TV. For a total of ~10 seconds.

If the providers is experiencing high loads than that can add more delay on top of that.

AFAICT, it is not an issue with your server.