Kodi addon keeps freezing, on playback then dumping back in the recordings list

[sitush]

My latest problem! There doesn't seem to be a pattern but, for example, three times in the last hour or so while watching recorded programmes (2 different ones), the Kodi addon has frozen the playback, the lower part of the screen has pixelated and then I have been dumped back in the recordings list. If I then select the programme for playback again, it gives me the option of resuming or starting from the beginning. The resume point does seem to align with the point of freezing, give or take a few seconds.

Kodi logs at https://paste.kodi.tv/ozudobelir and NPVR logs attached here. The Kodi logs only reflect the latest freeze because I enabled logging after the previous incident.

[mvallevand]

What I do see in the kodi log is calls to the backend during playback which is really not necessary and I even see the web server having troubles and returned a 404 erros, so I would configure Kodi to not update during playback.

One of the new features in v18 is you can use the filesystem to play files, which means you might be able to avoid http lockup using advancesettings.xml

Martin

[sitush]

Ok, thanks. I've changed the setting for update during playback and will report back here. I don't understand your second paragraph but will investigate it further if needed.

[sitush]

Just froze and dumped me again despite the change. I will have to figure out what the xml file does.

[mvallevand]

It works using Kodi's advancedsetttings.xml https://kodi.wiki/view/Advancedsettings.xml. In your case you need to share F:\recordings\ and then substitute in your path

Code:

<advancedsettings>
<pathsubstitution>
<substitute>
<from>F:\recordings\ </from>
<to>smb://ip/share/</to>
</substitute>
</pathsubstitution>
</advancedsettings>

Martin

[sitush]

Seems like a lot of messing about when both the client and the backend have nothing on them other than the standard Win 10 install + Kodi (+ NPVR on the backend). I don't understand why the webserver keeps crashing/returning 404.

Anyway, I'll try it. Not sure what the /share folder should be, although ip is obviously the client ip address.

[mvallevand]

Sub and I would have to look at the new logs when you have the update turned off to see if the web server is still even issuing that 404. The web server crashing was an earlier problem with NShared I didn't see that in yesterday's logs.

You will have to research setting up windows share setup on your own.


Martin

[sitush]

Using the advancedsettings.xml seems to work regarding the buffering/lock up, although I gather from the wiki that it is possibly a fudged solution. OTOH, two other issues have now emerged that may or may not be connected. The first is that live TV seems to lock up when trying to navigate away from a broadcast, and the second is that deleting folders containing > 1 recording causes Kodi to crash and dump me back in Windows, although when restarted the folder no longer appears in the listing.

I'm going to see if I can isolate the issues with another set of logs but that will mean setting some recordings of something that recurs but I do not want, eg: a news programme.

For anyone else who has to adopt this approach, please note that when setting the backend recordings folder to be shared it seems to be necessary to ensure that the default "read only" permission is changed to something more liberal, otherwise Kodi behaves oddly when trying to delete even single recordings.

[mvallevand]

Usin the file system is certainly not a hack or fudged solution I implemented it to reduce load and i/o.

Using filesystem

- Kodi reads file, Kodi plays file, Kodi requests update NextPVR resume position

Using http

- Kodi requests stream, NextPVR reads file, NextPVR writes stream, Kodi reads stream, Kodi plays file, Kodi requests update NextPVR resume position. On top of this NextPVR logs extensively

The file delete issue is a Kodi issue, and I submitted a fix to sub for release quite a while ago. It will be in .14 when sub release it. From a Kodi perspective the client doesn't do any deleting, NextPVR does, so readonly is fine. Any odd behaviour may be a result of the Kodi bug.

For the first tuning issue logs are required and open a new topic. Never worry about the time spent in duplicating scenario's if you don't do it guess who has to?

Martin

[sitush]

I spoke too soon - the freezing and then dumping back into the recordings folder is still happening, although much less frequently. I will turn logging back on until it happens again.