Using R5000-HD with Network Recorder Plugin

[checkbin99]

I am a new user to NextPVR (latest ver. 4) and am trying to set up a Nexcomm R5000-HD usiing the NetworkRecorder plugin.  The R5000-HD is already configured and working with SageTV.  I disabled SageTV and am tring to get the Network Recorder plugin working now.  I can't find very detailed instructions for using the Network Recorder as it relates to the R5000.  I have it configured from the NetworkRecorder wiki.  When I try to tune a channel I see in the R5000 app GUI that it is opens a stream but then then I get an error that says it can't open c:\users\Public\recordings even though that directory exists on the R5000 server.  I have the R5000 on the same server as NextPVR for initial testing.  Spent all weekend trying to get it to work.  Anyone  have any thoughts on what I need to do to make this work? 

BTW, here is my networkrecorder.xml file contents:

<?xml version="1.0"?>
<Settings>
  <PluginSettings>
    <NetworkRecorder>
      <FriendlyName>R5ooo-HD</FriendlyName>
      <host>127.0.0.1</host>
      <port>6969</port>
      <SocketOpen>true</SocketOpen>
      <h264Mode>2</h264Mode>
      <delay>2000</delay>
    </NetworkRecorder>
  </PluginSettings>
</Settings>

[mvallevand]

I am not surprised that there isn't much documentation Fuzzy tested it years ago but I don't think anyone used it. I thought the IP should be a remote IP but I don't know how these devices work. If you have a spare I take donations.

In any case there a few possible issues but you should have uploaded logs.

- the recording drive will have to be relative to the NextPVR server, but right now since they are together that should be ok.
- I see you are running with socket open mode, I know there are a couple of Sage protocols, perhaps you don't need that.
- the nextpvr server does the writing, I'd confirm that the System user has access to the folder.

Martin

[checkbin99]

Thank you for the quick reply.  I will post logs, I was just hoping for a quick how-to somewhere first so I can make sure I'm not missing something simple in the configuration.  I will double check the user permissions but since the folder is in c:\users\public I assume anyone could write to that directory.  I will gather the logs and upload them later today.  Thank you.

[checkbin99]

Log files are attached.  Thank you.

[mvallevand]

I am a bit confused by the logging. There seems to be a file that doesn't belong dmcrypto.dll in with the plugin get rid of that file and restart the sever.

Also make sure that you do all the testing with the NextPVR client the web based live TV in v4 isn't great. Try live tv (which did seem to be recording) and send the logs again.

Martin

[checkbin99]

OK I added a Colossus capture card as another tuner and everything works fine with channels fed into that.  But still having issues with the R5000.  I currently have the R5000 on a different windows box from the NextPVR server.  The Next PVR is on .87 of my network and the R5000 with the NextCom SageTV network encoder software on .16 of the same network.  I have a Windows share between the 2 servers mounted to C:\mnt\R5000_Recordings\NextPVR.  If I start to either watch or record a channel on the R5000, the NextCom network encoder app shows a Ping from the client (NextPVR) and the indicator turns green.  However I see an error saying "Failed to open file for SageTV: LIVE&C:\mnt\R5000_Recordings\NextPVR\live-NATGEO-15064.ts.  Error: The filename, directory name, or volume label syntax is incorrect"

I don't understand why NextPVR is adding LIVE& in front of the recording path?

I've attached the latest logs. 

BTW, I first tried to use a local recording folder in C:\users\public\videos rather than a shared drive.  The colossus recording writes fine there but I get the same error on the R5000.  

Thanks in advance for any thoughts or suggestions.

[mvallevand]

The plugin should strip that off before making the request the logs didn't make it you missed a step.

Martin

[checkbin99]

Adding log files

[mvallevand]

That doesn't look good what is the date of your networkrecorder.dll

Martin

[checkbin99]

mvallavand, the date of my networkrecorder.dll is 10/28/2013. Thanks.