Using R5000-HD with Network Recorder Plugin

[mvallevand]

Ok the stop command should stop that. I will makes some changes for v2 protocol to avoid that. 12345678 makes sense.

Are you running sagetv on that box? It also uses 7818? After a bit of additional research it looks like the error is because I was binding to wrong server but since it isn't going to work no point in going further on that.

The bottom line is this will work with v5 of NextPVR. Since your main use was with Emby I strongly suggest you upgrade the API is faster and the plugin fixes a few issues.

You might even be able to attach to that stv server on .15 with this if you want to play around.

Thanks for testing this out. I can help out with v5 whenever you want.

Martin

[checkbin99]

mvallavend,

Can you explain your last comment about "You might even be able to attach to that stv server on .15 with this if you want to play around."?  Is it possible to use your script to access the R5000 without using the NextCom app?  That app only runs on Windows and I'd love to be able to use the R5000 on Linux and do away with my Windows server I'm running the R5000 software on.

[mvallevand]

Sorry for the confusion I meant SageTV since it was available via the discovery method. Since MythTV can talk to it there probably is a way to make a Network Recorder for it but it is not something I am interested in working on.

Martin

[checkbin99]

I understand.  I didn't think it would do that, but I was hoping.  :-)

[checkbin99]

I am planning to try NextPVR 5 on Linux in the next few days and if all goes well, test the R5000 on Emby too with the NPVR5 Network Recorder plugin.

[mvallevand]

v5 doesn't support the tuner plugin, we will need to do this with an "extra" but that will be very easy based on your python testing. Let me know when you have v5 installed and a common shared folder for storing the intermediate file ready.

Martin.

[checkbin99]

Hi mallevand. I've just installed NextPVR 5 on my Linux box. I have a shared file for recordings, accessible from both my R500 server and the NextPVR box. I added one channel with an HDHomerun tuner just to make sure the ver. 5. is working and all is good. I also tested the python script you had provided to make sure the R5000 could see the share and record to it. All seems good. Can you tell me what I need to do next to get my R5000 integrated into my NextPVR 5 setup. Thank you.

checkbin

[mvallevand]

Now it should be easy

1 Create this xml file as extras-r5000.xml

Code:

<extras>
  <channel name="{channel-name}">
    <command>bash</command>
    <args>-c "/var/opt/nextpvr/scripts/opendct.sh {channel} R5ooo-HD"</args>
  </channel>
</extras>

2.In /var/opt/nextpvr/scripts create the file opendct.sh

Code:

nextname=/home/martin/recordings/$2.ts
openname=$nextname

#example translations
#nextname=/media/recordings/$2.ts
#openname=\\172.16.3.105\Recordings\$2.ts
#openname=K:\$2.ts

opendct=/var/opt/nextpvr/scripts/opendct.py

python3 $opendct STOP "$2"
python3 $opendct START "$2" $1 "$openname"
python3 $opendct GET_SIZE "$2"
ffmpeg -re -i "$nextname" -f mpegts -codec copy -v panic -
python3 $opendct STOP "$2"

Set the path of openname to the filename as unknown to your r5000 server and nextname to the name you will path know it in nextpvr. The file will always be called the same thing so the instructions for multiple r5000's would be different.

3. Run

sudo chmod +x /var/opt/nextpvr/scripts/opendct.sh

4. Copy the python script to /var/opt/nextpvr/scripts

5. In NextPVR Settings Devices click rescan and you should see an Extras device called extras-r5000 If you don't restart the nextpvr server.

6. Open the device and choose the xmltv file or hopefully Schedules Direct lineup that you will use for channel numbers for the control the r5000.

7. Remove the stations you don't want and click save.

8. Update the EPG if you want (if you added lots you can do that latter)

9. Try live tv from the guide. If that doesn't work restart the server

Let me know how it goes and which points need more work for the wiki. Note it is called OpenDCT because I think the prime users of this interface will be Ceton device owner via OpenDCT

Martin

[checkbin99]

Thanks for the quick reply mvalleved. I'm a bit confused (not hard to do) when you say Set the path of openname to the filename as unknown to your r5000 server and nextname to the name you will path know it in nextpvr. The examples   I have these entries in mine based on the first 2 line sin your script,  but the examples seem to be different:

nextname=/mnt/R5000_Recordings/$2.ts  (My shraed recording directory is /mnt/R5000_Recordings on a NAS)
openname=$nextname

I don't understand what should be in the second line if not what I have above?

-Bill

[mvallevand]

Sorry the xml files goes in /var/opt/nextpvr

openname will be the path on the r5000 server with $2.ts as the filename

The example is when opendct and NextPVR are on the same pc

Martin