Jump to content

Streams stop without interaction


CharlieMurphy

Recommended Posts

CharlieMurphy

IPTV through xTeVe, set to use ffmpeg with 1mb buffer.

xTeve log says:  2020-10-14 18:52:43 [xTeVe] Streaming Status:      Client has terminated the connection

I've attached the Emby logs from the time where I think things went off the rails a few seconds before this. It looks almost like the Emby client on the Android TV quit the stream, but then there's an error report that I can't interpret. There was no interaction with the client to cancel the stream, sometimes streams are lasting 6 hours but this one only made it about 20 minutes.

Thanks!

EDIT: Just to add detail, the IPTV portion of my setup is new. I use Docker. This issue is on Roku and Android TV for me, I'm letting the Roku again play until it fails so I can see if the logs looks the same.

redactedlog.txt

Edited by CharlieMurphy
Link to post
Share on other sites
CharlieMurphy

Just to update, I don't think I needed to be running it through ffmpeg in xTeVe anyway. Seems better without.

Link to post
Share on other sites
ebr

Hi. Is the TV unattended when this happens?  Is the option for the "Still watching prompt" enabled?

Link to post
Share on other sites
CharlieMurphy

Yesterday I had turned off "Still watching prompt" on both Roku and the new Chromecast (AndroidTV/GoogleTV) to rule that out. It freezes on a frame or just stops, unattended or attended.

Last night to try to rule out my provider, I left a stream up in VLC on a PC and on the Roku through Emby, which was direct streaming. Started them around 3:00am and VLC was still going around noon while Roku was asleep again. It does seem almost like an inactivity time-out but the length of time before they fail/quit is all over the place. Roku made it until 7:20am which is longer than usual. I was having similar reliability issues with Jellyfin so I can't rule out xTeVe as being the issue.

Transcode log:

07:20:50.219 [segment @ 0x1c8c600] Opening '/mnt/transcode/transcoding-temp/ED0502_173.ts.tmp' for writing
07:20:51.118 frame=31164 fps= 62 q=-1.0 size=  314201kB time=00:08:39.88 bitrate=5023.2kbits/s throttle=off speed=1.02x    
07:20:51.921

[q] command received. Exiting.


07:20:51.921 07:20:51.921 [segment @ 0x1c8c600] Opening '/mnt/transcode/transcoding-temp/ED0502.m3u8.tmp' for writing
07:20:51.921 SegmentComplete=video:0 Index=173 Start=519.830711 End=521.081956 Duration=1.251244 offset_pts=0 start_pts=519830711 Frames=75 filename=hls/ED0502/ED0502_173.ts
07:20:51.922 frame=31233 fps= 62 q=-1.0 Lsize=  315190kB time=00:08:41.03 bitrate=5027.7kbits/s throttle=off speed=1.02x    
07:20:51.922 video:309084kB audio:6106kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
    Last message repeated 1 times
07:20:51.922 EXIT
07:20:51.922

Emby log attached

 

Thanks for helping me out. I'm liking the navigation better as I get the hang of it, I just need to get it stabilized.

 

redactedlog2.txt

Link to post
Share on other sites
CharlieMurphy

In case this comes up in a search or something, I want to leave my steps to getting this one working.

I realized that Emby's log was in the wrong timezone. I made my Emby container years ago and didn't set it so I assume it was GMT. While setting timezone I also decided to try out the Linuxserver.io container instead of the official from Emby, just because I've liked theirs for other applications. After these two changes it was definitely more stable but now I was getting an Error 401 followed by Error 403 in my xTeVe logs after several hours of play. I found discussions through searching and someone suggested the user-agent could be the issue. xTeVe has a field for it so I changed it to match what Emby was using by default, which is "VLC/3.0.1", it was originally set to "xTeVe". 

An unusual detail is that the 401 error followed by continued 403's were coming after hours of being active. I would have thought the user-agent would be rejected immediately or not at all.

Thanks Emby team.

Edited by CharlieMurphy
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...