Kodi Freezes During Live TV

[jmooremcc]

I'm running Kodi 17.6 on a Raspberry Pi with the NextPVR server running on a Windows 10 desktop computer.
I've been having problems with live TV programs sporadically freezing on the RPi.

The Kodi Log indicates the following:

Code:

18:20:20.130 T:1323352992  NOTICE: CVideoPlayerAudio::Process - stream stalled
18:20:20.911 T:1331741600    INFO: CVideoPlayerVideo - Stillframe detected, switching to forced 29.970030 fps
18:20:20.912 T:1331741600   DEBUG: CPullupCorrection: pattern lost on diff 166833.333344, number of losses 4
18:20:22.755 T:1331741600    INFO: CVideoPlayerVideo - Stillframe left, switching to normal playback
18:20:22.757 T:1722024864   DEBUG: Stream stalled, start buffering. Audio: 0 - Video: 0

Please note that both the audio and video streams are frozen (paused).

I immediately saved the NextPVR logs using the zip file logs function and the Kodi log for your inspection.

I hope someone can be figure out what's causing this problem and come up with a solution.

Thanks to everyone in advance.

[mvallevand]

It looks like your PC was blocked for a few seconds at that time and there was not enough buffered in the RPi to handle that short delay

Code:

2018-12-18 18:20:18.196    [DEBUG][19]    Got request: Range: bytes=16384065536-16384098304-500002    
2018-12-18 18:20:18.297    [DEBUG][19]    LiveShift response: 16384065536:32768 16384234592 500002
<--
2018-12-18 18:20:22.616    [DEBUG][19]    About to send 32768 bytes

Nothing in the logs explains it, maybe check the Windows event viewer.

Note that at the time you send the logs that tuner was still in use and recording by that aborted play, and it would stay like that until you kill that Kodi session.

I know with v18 the buffer for live tv is quite large, certainly much more than this blip.

Martin

[jmooremcc]

I'm running Kodi 17.6 on a Raspberry Pi with the NextPVR server running on a Windows 10 desktop computer.
I've been having problems with live TV programs sporadically freezing on the RPi when I programatically change the channel (JSON RPC)

An excerpt from the Kodi Log indicates the following:

Code:

19:59:54.177 T:1722233760   DEBUG: PVRManager - PerformChannelSwitch - switching to channel 'H & I'
19:59:54.177 T:1722233760   DEBUG: AddOnLog: NextPVR PVR Client: SwitchChannel(10:H & I)
19:59:54.177 T:1722233760   DEBUG: AddOnLog: NextPVR PVR Client: OpenLiveStream(10:H & I) (oid=7894)
19:59:54.177 T:1722233760   DEBUG: AddOnLog: NextPVR PVR Client: OpenLiveStream() informing NextPVR of existing channel stream closing
...
19:59:54.291 T:1243607968    INFO: CFileCache::Process - Source read didn't return any data! Hit eof(?)
...
19:59:57.270 T:1722233760  NOTICE: PVRManager - PerformChannelSwitch - switched to channel 'H & I'

I've attached all pertinent logs for your review and made sure that tuner was not in use when I saved the log files.
Also I checked the Windows logs and saw no errors around the time of the event.

I thank you in advance for your help.

[mvallevand]

I don't know what you are expecting on v17.6 now that v18 is almost out but the reader thread does seem to stall much like on a recent thread https://forums.nextpvr.com/showthread.ph...Lost/page3

Code:

2018-12-19 20:00:04.027    [DEBUG][3]    LiveShift response: 3112960:32768 3186224 95
2018-12-19 20:00:04.027    [DEBUG][3]    About to send 32768 bytes
2018-12-19 20:00:04.027    [DEBUG][3]    Sent 32768 bytes
2018-12-19 20:00:07.205    [DEBUG][3]    Checking for close notifications for sid: default
2018-12-19 20:00:07.205    [DEBUG][3]    Renewed lease. (14007D)@2...

Martin

[jmooremcc]

I'm not getting freezing on my other RPi systems like this one.
I didn't get this kind of behavior under V16 on the same hardware. I know it's not the hardware because I have a second RPi2 and have experienced the same problem. Something is the cause of the problem and I'd like to fix it if I can.

V18 is still in alpha testing from LibreElec so I won't be transitioning to that version until it's more stable.

[mvallevand]

My point was if this is in the client you won't be getting a fix. Also remember that in v17 timeshifting was not officially supported by Kodi so perhaps you need to go back to v16 while you wait.

Martin