Using R5000-HD with Network Recorder Plugin

[checkbin99]

I think the last line, rm "$nextname"  might be causing recording to stop.

[mvallevand]

Your r5000.sh is calling openddct.py not r5000.py like opendct.sh is so the files aren't the same.

I do notice that these sh files both call GET_SIZE not GET_FILE_SIZE which is now returning a size in the output from opendct.sh

Martin

[mvallevand]

I think the last line, rm "$nextname"  might be causing recording to stop.

There is a STOP command issued before the remove which should be causing the recording to stop.

Martin

[checkbin99]

Sorry about the mixup in the r5000.sh script.  I was switching the opendct call back and forth and didn't realize it was still calling opendct.py. I think I'm getting bleary eyed looking at these scripts.   I don't know how you do it.  :-)

Yes I changed back to GET_SIZE as it seemed it was not working at all with GET_FILE_SIZE.

So with the call to r5000.py, both scripts continue to record now.  So where are we at now?  Is there still hope?

[mvallevand]

If GET_SIZE is returning a size then use it however I would change r5000.py back to GET_SIZE to match. The reason I changed is the Windows program was using GET_FILE_SIZE and I saw it returning a value with your windows logs way back in this thread. This should allow you to remove the sleep 15 you added in the sh file.

If the testing those work then you should be able to use opendct.sh from the extra by reversing the ffmpeg lines.

Martin

[checkbin99]

Sounds good. Can you explain what you mean by reversing the ffmpeg lines?

[mvallevand]

You commented out the good line with -v panic and added a new line that won't send any date to the pipe.

Martin

[checkbin99]

Ah yes, of course.  Thank you.

Well mostly good news.  I can tune either of the R5000 channels!  Yaay!

However I had to keep the sleep in with a delay of at least 9.  With the sleep line removed or if it was less than 9, recording would not start, or im most cases it stayed on the previous channel.

With sleep set to 9, I can change back and forth between channels fine.  However,, from the time I select the channel in the NPVR Guide, it takes approx. 18 seconds before the picture shows up.


Still great progress.  Thank you so much Martin!  Is there any way now to reduce that 18 second delay and still get the R5000 to start recording? Latest logs attached.

[checkbin99]

BTW, even more good news. Emby works now too with the NPVR plugin. Delay to tune is the same there... 17 to 18 seconds. Hey but at least it works!!

[mvallevand]

Did your test with script indicate the file was growing with GET_SIZE and did you edit r5000.py to use GET_SIZE.

Also remember you aren't using a real client so part of that delay is transcoding.

2020-01-12 12:30:08.334 [DEBUG][139] Running: bash -c "/var/opt/nextpvr/scripts/opendct.sh 190 R5ooo-HD"
2020-01-12 12:30:17.256 [DEBUG][122] {"status": "Receiving Data. (50000)","final": false,"speed": 0,"duration": 0,"percentage": 0}
2020-01-12 12:30:21.758 [DEBUG][124] {"status": "Transcoding.... (100% speed: 7.07x)","final": true,"speed": 7.07,"duration": 0,"percentage": 100}

Martin