New install: Intermittent Recording Service Not Running, long delays

[GnatGoSplat]

I have a new install on Win10 as server using Kodi client.

First, a minor issue: NextPVR Service doesn't automatically start at boot.  I changed Startup Type from "Automatic (Delayed Start)" to "Automatic", and that seems to start it up at boot.

Recording is intermittent.  Most of the time, it doesn't work.  It worked fine right after the boot when I changed Startup Type to Automatic, but it didn't work after subsequent cold boots.

When recording was working, I was making several test recordings of 5-10 minutes long.  Some of them could play right away, but a couple of them (both of the same channel) would sit at a blank screen with spinning wheel for about 30-40 seconds before it would start playing.  Before I realized it can take that long to cue up, I was going back and trying to get back to live TV or stop the playback and nothing would respond unless I exited Kodi entirely.  Also once the recording did start playback, it would play fine, but if I hit skip ahead for the first time, it would take 30-40 seconds stuck until it would recover.  All subsequent uses of skip ahead worked, however.  It was always just the first time that would be stuck.

Logs attached.

[sub]

Intermittent Recording Service Not Running, long delays

Both of these sound like maybe something is causing your recording service to crash. I had a quick scan through the logs, but couldn't see an obvious reason. It looked like the logs were cut short.

Might be worth temporary stopping the service, and from a command prompt manually running NextPVRServer.exe, so we can see if it dies, and what happening immediately prior to it dying.

[GnatGoSplat]

Tried more recordings, still no-go this boot.
I did stop the service and tried it from command line.  I've attached the output and new logs.

  logs-20211124-1447.zip (Size: 167.05 KB / Downloads: 5)

[sub]

I did stop the service and tried it from command line. 

and what did you try doing, and what happened? (so we know what we're looking at)

[sub]

Ultimately we're best to pick a specific thing and focus on that, rather than jumping back in forth between different issues.

Some of them could play right away, but a couple of them (both of the same channel) would sit at a blank screen with spinning wheel for about 30-40 seconds before it would start playing.

This would be a good thing to focus on. Have you got a specific recording that does this every time? Can you post the longs immediately after attempting to play the file.

[GnatGoSplat]

I did stop the service and tried it from command line. 

and what did you try doing, and what happened? (so we know what we're looking at)

I was trying to record something already in progress, "That 70s Show".

Ultimately we're best to pick a specific thing and focus on that, rather than jumping back in forth between different issues.

Some of them could play right away, but a couple of them (both of the same channel) would sit at a blank screen with spinning wheel for about 30-40 seconds before it would start playing.

This would be a good thing to focus on. Have you got a specific recording that does this every time? Can you post the longs immediately after attempting to play the file.

Unfortunately, I had deleted the working recordings and so far no subsequent reboots have I managed to get recording working again. It was just 1 time did recording just magically work, but not on any boots prior nor subsequent.

[mvallevand]

Does Live TV work in Kodi now?

Martin

[sub]

When you try record, does a file get created in your recording directory? Does it end up with anything in it?

[MaxOne72]

I had the same issue. Gone now that I have change the service to automatic.

[GnatGoSplat]

Does Live TV work in Kodi now?

Martin

Yes, Live TV works and has been working well.

When you try record, does a file get created in your recording directory? Does it end up with anything in it?

Yes, it has been creating files with 0 length.

I had the same issue. Gone now that I have change the service to automatic.

I thought that may have been the issue when it worked the one time after I changed it and rebooted, but it went back to not working after subsequent reboots.