Using R5000-HD with Network Recorder Plugin
|
2019-12-10, 03:08 AM
I cant help with fixing the file permission issue for you but after you get that you should be there. That's why I wanted it working as one of the first steps.
To bad it has the old protocol with opendct we could directly stream. Martin
2019-12-10, 02:55 PM
Understood. Just to confirm, I believe the permissions issue is with NextPVR not being able to read the video file, not that the R5000 server has permissions issues. Is that what you see? It seems the file is being written now but the script is unable to read it to open the ffmpeg stream, correct? I'm seeing the written file is being seen from the Linux box as being owned by "nobody", since its on an NFS share and I suspect that's why the script can't read it. NextPVR and its scripts will all run as the user "nextpvr", correct?
2019-12-10, 03:05 PM
At this point the permission error would be on the user acount you are using to test the script which I assume to be bill.
Can your see files in /mnt/R5000_Recordings/ from the shell and read them? Martin
2019-12-10, 03:08 PM
I'm away from my system now and will have to check when I get home. From what I remember, the file is being written fine by the R5000 but on the Linux box, it was owned by nobody:nogroup with permissions of 550. Which would explain why user bill can't read it. Just have to figure out how to make the NFS mount not grab everything as user "nobody".
2019-12-10, 03:12 PM
The share is on a QNAP NAS. I suspect I need to play with the NFS export "all_squash" and other export options.
2019-12-10, 03:24 PM
(This post was last modified: 2019-12-10, 03:24 PM by mvallevand.)
nobody is typically good. I set my shares to nobody so my account and nextpvr can use it and get universal access from Windows and Linux boxes
You may need to add nextpvr and bill to group nogroup on your Mint box Martin
2019-12-10, 03:30 PM
Yeah I was thinking of adding those users to nogroup. Just wanted sure if that was the best solution or if there's a better answer. I'll let you know what I find out. Thank you again Martin.
2019-12-18, 01:17 AM
mallevand,
I believe I have the permissions issue resolved. But I seem to be having an issue with the recording path, so recording doesn't actually start. When I issue the last command you gave me (/var/opt/nextpvr/scripts/opendct.sh 190 R5ooo-HD | ffmpeg -i pipe: -f mpegts -y /dev/null) (or even just /var/opt/nextpvr/scripts/opendct.sh 190 R5ooo-HD) the R5000 NextCom app shows like it is trying to record, in that the Program Lenjth and File size indicate in the app that they are growing. But it is trying to record to a path that doesn't have the slashes (/) in the path. "In the NextCom app "Save As" window, it is trying to save to C:mntR5000_Recordings$2.ts Here are the curent setting s in opendct.sh: nextname=/mnt/R5000_Recordings/$2.ts openname=C:\mnt\R5000_Recordings\$2.ts Any ideas?
2019-12-18, 01:36 AM
For the openname what if you use all slashes and not backslashes? Windows should accept them.
Martin
2019-12-18, 01:42 AM
I changed opename per your suggestion. Now there is no recording started:
Failed to open file for SageTV C:/mnt/R5000_Recordings/R5ooo-HD.ts. error: The system cannot find the path specified. |
|
|
