Using R5000-HD with Network Recorder Plugin

[checkbin99]

Yes I agree.  The line in the nbw opendct.sh you created (from r5000.sh), in the line:

opendct=/var/opt/nextpvr/scripts/r5000.py    will call r5000.py.  But based on what I'm seeing, does it not seem that r5000.py is initiating the R5000 to record, which the older opendct.py does.  Does that make sense?

[mvallevand]

No this doesn't make sense. The test of opendct.sh calling r5000.py looks good except the file wasn't growing.

I just did a test here and this worked for my HDHR

python3 /var/opt/nextpvr/scripts/r5000.py START "HDHomeRun HDTC-2US Tuner 10528531-1" 24.1 c:\\temp\\tvo.ts

so

python3 /var/opt/nextpvr/scripts/r5000.py START anyname 190 c:\\temp\\filename.ts

should work if the r5000 server is running.

Martin

[checkbin99]

Hi Martin.  Thank you again.  Yes what you suggested to run is what I was trying to get at but I guess I had the syntax wrong to just test the r5000.py script alone. 

I ran "python3 /var/opt/nextpvr/scripts/r5000.py START anyname 190 c:\\temp\\filename.ts"  - and it records perfectly.  I recorded one 15 minute segment on channel 190 and another 10 min. one using channel 132 and both did not stop and the video looks fine (BTW I also tried /mnt/R5000_Recordings/filename.ts at the end at that worked as well).

So why does it not work when I try to run by calling opendct.sh?  Do I need to do anything with the extra setting now that I have a different script?  I'm sorry I'm so ignorant on how this all fits together and I really appreciate all your help.

One other question.  The Emby NPVR plugin I downloaded is a .dll file.  That was the only one I could find.  I didn't think a .dll file would work on Linux but Emby does seem to see it as a plugin and I could configure the IP and port.  Is this the one I should be using with Emby?

Bill

[mvallevand]

The run of opendct.sh on here https://forums.nextpvr.com/showthread.ph...#pid532675 seemed ok, although I asked you to pump up the seconds to 15.

The dll for Emby is netcore so it is multi-platform.

Martin

[checkbin99]

Hi Martin.  Well here's the thing.  In that post you refer to you, you said the script reports the file isn't growing for 10 seconds, and asked if I saw the command logged on the Windows server? If so I might have to bump up the end time in opendct.py to seconds=15 or more until data starts flowing.  I did not see the command logged on the window server.  The NextCom app appeared it never got a record request and never even tried to star6.  So I didn't even try to bump up the wait time.

However I just noticed something else. I have 3rd channel I have set up is a local channel using my HDHomerun prime rather than the R5000, which I used to make sure my NextPVR setup was correctly before starting to test the R5000.  Now that channel no longer works too.  When I try to tune to it, I see the same thing on the screen as I do for the R5000 channels.  The screen says "Receiving Data. (45450000)" at the bottom but I never get video. Could having put the Emby plugin broke soemthing or did I mess something else up along the way?

[checkbin99]

Disregard my last comment about the 3rd channel.  I restarted the NPVR server and that channel is working now.  So I went back and tested the new scripts you sent me again.   Now the NextCom app is getting the start command but is not recording. I see activity but the file stays at zero.  So where in the r5000.py script do I need to bump up the time you recommended?

[mvallevand]

Is the file growing on the disk? Perhaps the server doesn't support it. I wonder, could you edit r5000.py and change the GET_SIZE to GET_FILE_SIZE and see if that helps.

Martin

[checkbin99]

Really spinning my wheels on this.  I tried changing GET_SIZE to GET_FILE_SIZE in the r5000.py script.  I'm getting the same results with either setting.  The NextCom app tries to record but the file size never goes above zero.

Attached is a screenshot of what the NextCom app looks like and also the latest NextPVR logs.

Weird how running the command "python3 /var/opt/nextpvr/scripts/r5000.py START anyname 190 c:\\temp\\filename.ts"  works perfectly every time but in NextPVR the recording just wont go.

[mvallevand]

There is no point in trying in in NextPVR these are the lines that need to work

https://forums.nextpvr.com/showthread.ph...#pid532674

When you changed GET_SIZE to GET_FILE_SIZE did you do it in the sh file too?

Martin

[checkbin99]

Oh sorry I did not change it in opendct.sh.  I just changed it there.  Now when I try to tune in NPVR, it seems   the NextCom app is not even trying to record at all.