TVEverywhere/Live TV getting stuck in a loop then hanging on Roku

[pmerchant73 3]

I use an .m3u file exported from ChannelsDVR as a LiveTV source in Emby.  All of the channels are TVEverywhere channels through my cable provider.  For seemingly the last few months, I can't rely on Emby for LiveTV on my TCL Roku TV as pretty much any stream ends up getting stuck in a loop and then hanging.  This didn't used to happen even with the same .m3u file. To get out of the hanged state, I need to back out of the channel back to the guide and then go back into the channel and it will restart the stream.  Not ideal when trying to watch TV as this happens repeatedly. 

I just replicated the issue after only a couple minutes of watching "The Fifth Element" on BBC America.    I've attached log files - issue occurred around 11:56pm.  I'm currently on Emby server 4.8.0.66 beta and the Roku Emby app is v4.1 build 1. Happy to provide any other information or files needed.  Thanks for taking a look.

channels-TVE-Comcast_SSO.m3u embyserver.txt ffmpeg-transcode-4f5fee83-7eb3-4ed7-b107-86d2d4a5f3ae_1.txt hardware_detection-63840175823.txt

[speechles 1919]

Spoiler

TranscodeReasons=ContainerBitrateExceedsLimit

23:55:03.754   Stream #0:0[0x102]: Data: timed_id3 (ID3  / 0x20334449)
23:55:03.754   Stream #0:1[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], Closed Captions, Level 40, 29.97 fps, 29.97 tbr, 90k tbn, Start-Time 0.033s
23:55:03.754   Stream #0:2[0x103]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 32000 Hz, stereo, fltp, 192 kb/s, Start-Time 0.018s

...snipped parts not relevant...

23:55:03.755 Stream mapping:
23:55:03.755   Stream #0:1 -> #0:0 (h264 (native) -> h264 (h264_nvenc))
23:55:03.755   Stream #0:2 -> #0:1 (copy)
23:55:03.755 Press [q] to stop, [?] for help
23:55:03.919 Output #0, segment, to 'D:\Emby-Server-extra\programdata\transcoding-temp\transcoding-temp\DB286B\DB286B_%d.ts':
23:55:03.919   Metadata:
23:55:03.919     encoder         : Lavf59.27.100
23:55:03.919   Stream #0:0: Video: h264 (High), cuda(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 9807 kb/s, 29.97 fps, 90k tbn
23:55:03.919     Metadata:
23:55:03.919       encoder         : Lavc59.37.100 h264_nvenc
23:55:03.919     Side data:
23:55:03.919       cpb: bitrate max/min/avg: 9807813/0/9807813 buffer size: 19615626 vbv_delay: N/A
23:55:03.919   Stream #0:1: Audio: aac (LC) ([15][0][0][0] / 0x000F), 32000 Hz, stereo, fltp, 192 kb/s (default)

...snipped parts not relevant...

23:56:10.377 [mpegts @ 0000022d3d37e440] Packet corrupt (stream = 1, dts = 6681690).
23:56:10.377 http://127.0.0.1:8096/LiveTv/LiveStreamFiles/c58b005c7aa54b189413a54bc5870e56/stream.ts: corrupt input packet in stream 1
23:56:10.462 Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scale_0'
23:56:10.463 Error reinitializing filters!
23:56:10.463 Failed to inject frame into filter network: Function not implemented
23:56:10.463 Error while processing the decoded data for stream #0:1
23:56:10.507 Conversion failed!
23:56:10.507 EXIT

It looks like stream 1, the video stream, has corrupt frames and breaks the filter used to overlay the subtitles with NVENC. If you could make it avoid transcoding you might be able to solve this.

Are you using Emby server over a remote connection or locally to play this item? If you are local you can raise the video quality bitrate to the highest available. Use the cog/gear on the homescreen of the Roku app. Inside playback settings at the very top is video quality bitrate.

Once you do this the item should direct play entirely and ffmpeg should only become involved to place the streams into a new container. That should resolve your issues immediately.

Edited January 7 by speechles

[pmerchant73 3]

Thank you for the reply.  I am using this Emby server locally.  I've just changed the video quality bitrate on the Emby app on my Roku TV to the highest available - 2160P 4K(UHD)-110Mbps.  For some reason, it had been set to 720P HD-10Mbps.

I'll test it out with this setting change and report back.

Thanks again.

[pmerchant73 3]

It's working perfectly now.  Thank you so much for your help!