Live TV (Stream) - Recovering from playback error

[mike3821 61]

Why am I getting this when watching live tv? Live TV works, but what is this?

"Recovering from playback error" ?

 

[Luke 37095]

Hi, it means the player had difficulty playing the original stream so we automatically switched to transcoding.

[ebr 14921]

Hi.  Also, in the case of that app, you may have the option to direct stream Live TV disabled.  The app stats for nerds will tell you if this is the case.

[bandit8623 48]

i have the same issue,  but mine is doing it direct play and transcode.  the pic attached is with my brother forcing transcode because his internet isnt fast enough. the second picture is from my pc on the same 1 gig network switch.  no error and i dont get the hiccups

 i get random hiccups every few minute or so ( 2 sec freeze) on the errored devices.  everything is hardwired 1 gig.   my server is a 14 core supermicro e5-2690 v4  with 128 gig ram. (shouldnt matter anyway on direct plays :)) 

my local firestick shows the same error as well as my brothers fire stick remotely.  when my wife watches her shows that have been recorded she sees no hiccups at all. so seems to be related to just live play.

 

thanks

local pc below

 

Edited September 18, 2022 by bandit8623
added 2nd and 3rd and 4th

[bandit8623 48]

So no video freezing. Just direct bistream audio cutouts.  Just direct play.

Transcode doesn't cut out at all.

Edited September 19, 2022 by bandit8623
Update

[bandit8623 48]

update..

tried the latest android apk app as well.  .  the android APK doesnt show the playback error on the server.  regular does like above.  

seeing this error alot in server logs while playing mpeg2 direct play streams

"2022-09-25 13:26:27.457 Info Server: http/2 Response 200 to myipaddress. Time: 3ms. https://‌‍‍servername:8920/emby/videos/1895/live.m3u8?DeviceId=9859713b23bd65bf&MediaSourceId=native_09199925f216a92048cad748bf859d1d_0366e67a4a2c49658cb7b1e23932761f&PlaySessionId=9f5a64c36b83440fbf1e5ab53b63bc5b&LiveStreamId=06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_native_09199925f216a92048cad748bf859d1d_0366e67a4a2c49658cb7b1e23932761f&VideoCodec=h264,mpeg2video,hevc,h265&AudioCodec=aac_latm,mp4a_latm,ac3,eac3,aac,mp3&VideoBitrate=4616000&AudioBitrate=384000&MaxHeight=2176&AudioStreamIndex=1&VideoSideDataSubs=100&CopyTimestamps=true&SegmentContainer=ts&MinSegments=2&AllowInterlacedVideoStreamCopy=True&BreakOnNonKeyFrames=True&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline&h264-level=51&hevc-profile=Main,Main10&aac_latm-audiochannels=8&mp4a_latm-audiochannels=8&ac3-audiochannels=8&eac3-audiochannels=6&aac-audiochannels=8&mp3-audiochannels=8&TranscodeReasons=ContainerBitrateExceedsLimit,DirectPlayError"

 

59:39.289 Info Server: http/1.1 Response 200 to ‌‍‍192.168.2.114‌. Time: 2ms. http://‌‍‍192.168.2.12‌:8096/emby/videos/1896/live.m3u8?DeviceId=bd4f7f029ecae150&MediaSourceId=native_38e2ec422972cf18ae399822dbeeeca8_0366e67a4a2c49658cb7b1e23932761f&PlaySessionId=ad9f53d8d6204731aa6cf9301fd6a4ab&LiveStreamId=06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_native_38e2ec422972cf18ae399822dbeeeca8_0366e67a4a2c49658cb7b1e23932761f&VideoCodec=h264,mpeg2video,hevc,h265&AudioCodec=aac_latm,mp4a_latm,ac3,aac,mp3&VideoBitrate=109616000&AudioBitrate=384000&MaxHeight=2176&AudioStreamIndex=1&VideoSideDataSubs=100&CopyTimestamps=true&SegmentContainer=ts&MinSegments=2&AllowInterlacedVideoStreamCopy=True&BreakOnNonKeyFrames=True&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline,high10&h264-level=52&hevc-profile=Main,Main10&aac_latm-audiochannels=8&mp4a_latm-audiochannels=8&ac3-audiochannels=8&aac-audiochannels=2&mp3-audiochannels=8&TranscodeReasons=DirectPlayError

 

2022-09-25 23:59:35.279 Info Server: http/1.1 GET http://‌‍‍192.168.2.12‌:8096/emby/videos/1896/live.m3u8?DeviceId=bd4f7f029ecae150&MediaSourceId=native_38e2ec422972cf18ae399822dbeeeca8_0366e67a4a2c49658cb7b1e23932761f&PlaySessionId=ad9f53d8d6204731aa6cf9301fd6a4ab&LiveStreamId=06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_native_38e2ec422972cf18ae399822dbeeeca8_0366e67a4a2c49658cb7b1e23932761f&VideoCodec=h264,mpeg2video,hevc,h265&AudioCodec=aac_latm,mp4a_latm,ac3,aac,mp3&VideoBitrate=109616000&AudioBitrate=384000&MaxHeight=2176&AudioStreamIndex=1&VideoSideDataSubs=100&CopyTimestamps=true&SegmentContainer=ts&MinSegments=2&AllowInterlacedVideoStreamCopy=True&BreakOnNonKeyFrames=True&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline,high10&h264-level=52&hevc-profile=Main,Main10&aac_latm-audiochannels=8&mp4a_latm-audiochannels=8&ac3-audiochannels=8&aac-audiochannels=2&mp3-audiochannels=8&TranscodeReasons=DirectPlayError. Connection=keep-alive, Host=192.168.2.12:8096, User-Agent=Emby/2.0.80g (Linux;Android 11) ExoPlayerLib/2.16.1, Accept-Encoding=gzip

Edited September 26, 2022 by bandit8623

[ebr 14921]

Hi.  Those log entries you posted are not errors.  They are just the playback urls.

[Luke 37095]

Hi, yes, please attach the complete server log files. Thanks.

[bandit8623 48]

2 hours ago, Luke said:

Hi, yes, please attach the complete server log files. Thanks.

i have looked at the logs when im seeing the freezing nothing is there but these.  

only happens on shield and fire sticks.

i only watch live tv on the weekend for football.  so ill try to grab new logs then

Edited September 27, 2022 by bandit8623

[bandit8623 48]

On 9/27/2022 at 9:32 AM, Luke said:

Hi, yes, please attach the complete server log files. Thanks.

i moved to Version 4.8.0.10 beta

and i no longer have freezing.  the playback error is still showing the recovering from playback error when using firetv on the android tv app,  but doesnt seem to be causing issues.  

the sideloaded app 3.2.76 still does not show this error.

[Luke 37095]

Great, thanks for the update.