NextPVR tuner plugin - User testing

[CraziFuzzy]

Gave it a shot this evening. Set Added the above patch, and copied in the plugin, and the updated .db3 file. Npvr runs, and does show the channels in the guide. Checked the devices screen, and the TestRecorder is there, showing 92 recordings. I updated the TestRecording.xml file to point to my R5000's IP and port:

Code:

<?xml version="1.0"?>
<settings>
  <PluginSettings>
    <TestRecorder>
        <FriendlyName>r5000 Tuner 1</FriendlyName>
        <host>192.168.10.10</host>        
        <port>6002</port>
        <delay>1000</delay>
    </TestRecorder>
  </PluginSettings>
</settings>

When I go to the guide, I have no guide data (expected), but when I tell it to record a given timeslot, I get a 'no tuners available for this recording' message, and nothing has been sent to the r5000.

[CraziFuzzy]

Restarted the npvr.exe, and I now get an exception (No Connection could be made because the target machine actively refused it 127.0.0.1:8968. This is not the R-5000 address/port, did you by chance hard code it and not utilize the XML file? I'm also getting a file not found exception when trying to start the nPVR service.

[mvallevand]

Gave it a shot this evening. Set Added the above patch, and copied in the plugin, and the updated .db3 file.

Thanks could you compress and upload the logs from your DataDirectory Logs folder. I think we are close.

Also before sending the logs could you try a watch and a quick record from the TV Guide.

Martin

[mvallevand]

Restarted the npvr.exe, and I now get an exception (No Connection could be made because the target machine actively refused it 127.0.0.1:8968. This is not the R-5000 address/port, did you by chance hard code it and not utilize the XML file? I'm also getting a file not found exception when trying to start the nPVR service.

I saw that in your other logs that I asked sub to comment on. Do you have the recording service turned on?

Martin

[CraziFuzzy]

I saw that in your other logs that I asked sub to comment on. Do you have the recording service turned on?

Martin

No, so i didn't figure the exception mattered at this stage.

Thanks could you compress and upload the logs from your DataDirectory Logs folder. I think we are close.

Also before sending the logs could you try a watch and a quick record from the TV Guide.

Martin

[mvallevand]

You are going to need to enable the recording service. Once you do I need all the logs, but the NRecord logs are the most important.

Martin

[CraziFuzzy]

You are going to need to enable the recording service. Once you do I need all the logs, but the NRecord logs are the most important.

Sure, i can enable the recording service, but the service still won't start. No log is generated from it either, just the exception thrown.

[CraziFuzzy]

Sure, i can enable the recording service, but the service still won't start. No log is generated from it either, just the exception thrown.

Found the problem with the service I think. I had originally installed NPVR on my C drive, then uninstalled and put it on Y instead. The service was never uninstalled and reinstalled to the new location, it was still pointing to C:\Program Files (x86)\NPVR\NRecord.exe. I'll try a reinstall and see if it gets fixed up.

[CraziFuzzy]

Okay, got the service fixed (had to adjust the path in the registry - uninstall should REALLY remove the service as well as the program). Anyways. I ran it, ran NextPVR, and chose a 'watch' on a channel. It was communicating with the R-5000, and attempted to start the recording, but it looks like you are closing the connection, so it is aborting immediately. Looks like the R5000 software expects the TCP connection to stay open during the recording. I've included the R-5000's SageLog as well.

[mvallevand]

Okay, got the service fixed (had to adjust the path in the registry - uninstall should REALLY remove the service as well as the program).

It's been a long time but I think it does uninstall the service but it leaves the NPVR registry entry which you need to modify to point to the new location, before the reinstall.

Anyways. I ran it, ran NextPVR, and chose a 'watch' on a channel. It was communicating with the R-5000, and attempted to start the recording, but it looks like you are closing the connection, so it is aborting immediately. Looks like the R5000 software expects the TCP connection to stay open during the recording. I've included the R-5000's SageLog as well.

Wouldn't you know it, I moved to a stateless socket connection because SageDCT wouldn't work if the socket was left open. I guess that was a change between Version 1 and 2. The joys of using an undocumented interface.

Attached is my last build prior to make that change. Unfortunately I can't easily provide updates because the plugin code is not compatible with 2.1.5 any longer.

Martin