.36 Failed to record, and other oddness

[Bluethunder]

Now that I've switched in to using NPVR full time, I'm starting to get issues.

I'm getting alot of failed to record (included the nrecord and npvr log files).

The last item on the log is the strangest.

It was supposed to do a recording from 5-6.

I started watching, and noticed that it hadnt stopped recording when the time was up, I think the recording service crashed about 6:30 or so, and the device list was empty until i restarted the recording service.

I have noticed a number of times, device unavailable as reasons for failed recordings.

This log is full of failed to start, error codes, exceptions and the like.

Any ideas?

Thanks

[johnsonx42]

you've got a mess there. your nextpvr.exe isn't seeing a recording service running, so it starts it's own, meanwhile when nrecord tries to start it can't create all it's sockets because something else already has them (like the recording service started by NextPVR). then both are partially running, and the left hand doesn't know what the right hand is doing. I'm surprised ANYTHING works in that condition.

reboot, check the NRecord log to make sure it started successfully without throwing errors. then start NextPVR, make sure it starts successfully AND sees the recording service and therefore does not start it's own copy (ie, you do NOT want to see the lines "[INFO][1] Using local in-process recording service" and "[INFO][1] RecordingService.Startup()" in the NextPVR log - those should ONLY appear in the NRecord log). if that doesn't work, you've probably got a firewall blocking communication between the two - disable and try again.