Kodi Client Time Shift functionality stops working after 35-40 minutes

[jmooremcc]

I need you help diagnosing my problem.

I have a backend V5 nextPVR server running under Windows 10 and a Kodi Leah client with the nextPVR addon running on a Raspberry Pi 4. The V5 backend server's Live TV buffer is set for 120 minutes and the TimeShift mode is set to TimeBased.

Whenever I start streaming a channel, the ability to time shift is only active for the first 35 - 40 minutes. After that time, Time Shifting is disabled. On one occasion, I had time shifted back a good ten minutes but when the 35-40 minutes of active time expired, time shifting became disabled and I was unable to go back to real time. Once I changed the channel, the clock for the availability of time shifting was reset and was again available.

In the for what it's worth department, I get similar behavior when I run the V4 nextPVR server on the same backend computer with the same RPi4 client  running Kodi Leah.

I am attaching logs (logs-20210429-1439.zip) from the V5 backend server and the log (kodi (2).zip) from my RPi4 Kodi client for you inspection.

My goal is to get Kodi Leah and V5 backend working better than my current system that utilizes the V4 backend server and Kodi Krypton client. So far, except for time shifting accuracy, the older system has been more reliable than the new one.

Please let me know if you need any additional information.

[mvallevand]

Sorry I don't support Leia anymore because changes are not being accepted by Kodi. If you can duplicate the issue with Matrix I can have a look.

This should have been posted in the Kodi sub-forum to help other users.

Martin

[mvallevand]

Overnight I remembered this 32 bit recording fix in https://forums.nextpvr.com/showthread.ph...#pid552743 and V5 timeshift inherits that recording class so it shouldn't be an issue in Matrix.

If you note my comments further on in that thread I did mention that it would be problem in Leia.

Martin

[jmooremcc]

Overnight I remembered this 32 bit recording fix in https://forums.nextpvr.com/showthread.ph...#pid552743  and V5 timeshift inherits that recording class so it shouldn't be an issue in Matrix.

If you note my comments further on in that thread I did mention that it would be problem in Leia. 

Martin

That was very interesting.
However, out of curiosity, why didn't Krypton suffer from the same malady? That's what really has me puzzled.

I'm currently testing Matrix with both V4 and V5 backends and will post my findings in the Kodi sub-forum if I run into the same problem.

Again, thanks for your feedback.

[mvallevand]

It is a bit confusing. Krypton and Leia/Matrix use completely different API's for timeshifting in Kodi. V4 and V5 also use different NextPVR timeshifting API's. Of note the person who submitted the V4 timeshift fix for Leia left before fixing a few problems and it will crash, even sub's original timeshift was a bit broken after some Krypton changes. V5 with Matrix timeshifting is by far the most stable.

Martin