Live TV Stalls After 4 Hours Due To Invalidated M3U8

[n1xkm 3]

Hey,

I'm using the newest beta of Emby (4.9.0.4-beta) and after attempting to play live tv on my apple tv for more than 4 hours it just stops at exactly after that 4 hours. In the logs it says that the (temporary) M3U8 returns a 410 Gone error and I was wondering if there is anyway to automatically restart playback when this happens instead of restarting it manually on the TV or Device.

Thanks.

(The live tv m3u8 that Emby requests redirects to a temporary stream that only is valid for 4 hours. It would be nice if it could automatically repeat this every time the stream is invalidated.)

I did not attach my server log because it is huge so, instead, this is the error that is related to the playback.

2024-02-17 06:49:55.010 Info Server: http/1.1 Response 200 to host2. Time: 10ms. GET https://emby_remote_ip:8920/emby/videos/813753/live.m3u8?DeviceId=366A2529-8968-4E59-8B7E-5BCBA931D24F&MediaSourceId=9b669e432b979bd83daeb862d7fae19b&PlaySessionId=69bac3a0bef74c2bb7011a1151eec54c&api_key=x_secret1_x&LiveStreamId=06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_9b669e432b979bd83daeb862d7fae19b&VideoCodec=h264,hevc,mpeg2video&AudioCodec=ac3,eac3,mp3,aac&VideoBitrate=159808000&AudioBitrate=192000&MaxWidth=3840&AudioStreamIndex=1&VideoSideDataSubs=100&TranscodingMaxAudioChannels=6&SegmentContainer=ts&SegmentLength=3&MinSegments=1&BreakOnNonKeyFrames=True&hevc-profile=Main,Main10
2024-02-17 06:50:55.892 Info SessionManager: Session 69bac3a0bef74c2bb7011a1151eec54c has gone idle while playing
2024-02-17 06:50:55.892 Info SessionManager: Playback stopped reported by app Emby for Apple TV 1.8.3 (1) on Apple TV playing ESPN. Stopped at 14423573 ms
2024-02-17 06:50:55.893 Info MediaSourceManager: Live stream 9b669e432b979bd83daeb862d7fae19b consumer count is now 0
2024-02-17 06:50:55.893 Info MediaSourceManager: Closing live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_9b669e432b979bd83daeb862d7fae19b
2024-02-17 06:50:55.893 Info SharedHttpPipelineSource: Closing SharedHttpPipelineSource
2024-02-17 06:50:55.893 Info SharedHttpPipelineSource: Deleting temp files 
2024-02-17 06:50:55.893 Info MediaSourceManager: Live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_9b669e432b979bd83daeb862d7fae19b closed successfully
2024-02-17 06:50:55.893 Info SessionManager: Removing playSession 69bac3a0bef74c2bb7011a1151eec54c from session 48306c35e109541c12edaa95812a5bea
2024-02-17 06:50:55.893 Info PlaybackReporting - EventMonitorEntryPoint: _sessionManager_PlaybackStop : Entered
2024-02-17 06:50:55.893 Info PlaybackReporting - EventMonitorEntryPoint: Saving final duration for Item : 366A2529-8968-4E59-8B7E-5BCBA931D24F|bfeaabfaa0d54de79021d9e8f77974ec|813753|Transcode (v:direct a:direct)
2024-02-17 06:50:55.898 Info PlaybackReporting - EventMonitorEntryPoint: Removing Old Key from playback_trackers : 366A2529-8968-4E59-8B7E-5BCBA931D24F|bfeaabfaa0d54de79021d9e8f77974ec|813753|Transcode (v:direct a:direct)

 

ffmpeg-directstream-d64581a3-8403-4057-8a0a-4ff281ec231d_1.txt

[Luke 37095]

Hi, yes this is something we can look at improving. Thanks.

[n1xkm 3]

32 minutes ago, Luke said:

Hi, yes this is something we can look at improving. Thanks.

Alright thanks again, I can give you my m3u8 file if that can help.