Do I ultimately need this package or the installation via the tool?
Can I also use the DTV recording function of the Synology Video Station? (if the functionality is good enough for me)
Synology SPK for DVR Record Engine
Re: Synology SPK for DVR Record Engine
That was my suspicion too - and confirmed
So something has changed with SPK package and process.
Once 7.0 is fully released I'll look in to it.
You don't need this package.
It's just a method to get the binary for the record engine from silicondust, setup the environment and provide scripts for autorestart, etc.
Without the SPK you can try the silicondust installers, or a manual install - see https://info.hdhomerun.com/info/dvr:sto ... vr_storage
unless something has changed in Video Station for 7.0 I don't think it will work for you - it only manages files on the NAS, no plugin AFAIR for tuners, guides, etc.
Re: Synology SPK for DVR Record Engine
The Video Stations DTV recognizes the HDHomeRun and I could do channel scan. The channel scan asks for location and connection type (cable or antenna).demonrik wrote: You don't need this package.
It's just a method to get the binary for the record engine from silicondust, setup the environment and provide scripts for autorestart, etc.
Without the SPK you can try the silicondust installers, or a manual install - see https://info.hdhomerun.com/info/dvr:sto ... vr_storage
unless something has changed in Video Station for 7.0 I don't think it will work for you - it only manages files on the NAS, no plugin AFAIR for tuners, guides, etc.
I am getting the program guide and I can schedule recodings - all fine.
But the recorded videos (ts format) are damaged, sometimes more sometimes less, somtimes after 10 sec. or only after 20 min.
Does the HDHomeRun box have an issue?
Re: Synology SPK for DVR Record Engine
cool to know they're adding the capability.joerg wrote: ↑Fri Mar 19, 2021 11:46 pm The Video Stations DTV recognizes the HDHomeRun and I could do channel scan. The channel scan asks for location and connection type (cable or antenna).
I am getting the program guide and I can schedule recodings - all fine.
But the recorded videos (ts format) are damaged, sometimes more sometimes less, somtimes after 10 sec. or only after 20 min.
Does the HDHomeRun box have an issue?
most likely is the synology app though and not the HDHomerun.
You could always do manual install of the DVR engine on the NAS.. if you can record properly with that, then it's the synology app.
Re: Synology SPK for DVR Record Engine
I have something odd going on. I decided to come back to your package after using the SD version for a while.
I deleted all of my HDHomeRun shares and freshly installed 1.0.2. When I access the gui I get "unable to discover DVR version". I also get "Error: recoding path is invalid" under Record Engine Logs. At the bottom of the gui I see "Unable to discover DVR status"
However, with that being said, I'm currently recording a show and my log doesn't appear to show any errors. So I guess everything is working but the gui is just wonky?
I recreated the share in DSM following your steps. I also chown'd the folder volume1/HDHomeRunDVR as hdhomerundvr:http
Here's my most recent snipped of my log file after a restart:
I deleted all of my HDHomeRun shares and freshly installed 1.0.2. When I access the gui I get "unable to discover DVR version". I also get "Error: recoding path is invalid" under Record Engine Logs. At the bottom of the gui I see "Unable to discover DVR status"
However, with that being said, I'm currently recording a show and my log doesn't appear to show any errors. So I guess everything is working but the gui is just wonky?
I recreated the share in DSM following your steps. I also chown'd the folder volume1/HDHomeRunDVR as hdhomerundvr:http
Here's my most recent snipped of my log file after a restart:
HDHomeRun RECORD 20210301 Linux AE85F93D-4DD8-5994-27FA-0E6311D1C1EF
20210410-02:12:30 System: file limit = 4096
20210410-02:12:30 Recording: RecordPath[0] = '/volume1/HDHomeRunDVR/'
20210410-02:12:30 Recording: RecordPath /volume1/HDHomeRunDVR/ = ext
20210410-02:12:30 System: LocalIP: 192.168.1.87 255.255.255.0
20210410-02:12:30 System: website port = 59090
20210410-02:12:30 Recorded: RecordPath '/volume1/HDHomeRunDVR/' (ext)
20210410-02:12:30 Status: Resource: nbk=0 dmk=217
20210410-02:12:30 Status: ticks = 44779078
20210410-02:12:30 Recorded: directory /volume1/HDHomeRunDVR/ with 0 subdirs and 0 recordings
20210410-02:12:30 Recording: sending discover using local ip 192.168.1.87
20210410-02:12:30 Recording: sending discover using local ip 192.168.1.87
20210410-02:12:30 Recording: discover response from AE85F93D-4DD8-5994-27FA-0E6311D1C1EF http://192.168.1.87:59090
20210410-02:12:30 Recording: discover response from 106337BB http://192.168.1.66:80
20210410-02:12:30 Recorded: recorded sync to record-api.hdhomerun.com
20210410-02:12:30 Recording: event download from record-api.hdhomerun.com
20210410-02:12:30 Recording: 106337BB lineup request success (found 40 channels)
20210410-02:12:31 System: server time = Sat Apr 10 02:12:31 2021 (correction of 0s)
20210410-02:12:31 Recorded: recorded sync success
20210410-02:12:31 System: server time = Sat Apr 10 02:12:31 2021 (correction of 0s)
20210410-02:12:31 Recording: event download success
20210410-02:12:31 Recording: disk space available = 724GB
20210410-02:12:31 Recording: current time = Sat Apr 10 02:12:31 2021 (correction of 0s)
20210410-02:12:31 Recording: no timer events planned
20210410-02:14:30 Status: Resource: nbk=0 dmk=221
20210410-02:16:30 Status: Resource: nbk=0 dmk=221
20210410-02:17:46 Recording: starting new file Live channel 23.3 9873f0bf
20210410-02:17:46 Recording: sending request to 106337BB at 192.168.1.66 for Live channel 23.3 9873f0bf
20210410-02:17:47 Recording: recording stated Live channel 23.3 9873f0bf
20210410-02:17:47 Playback: Streaming: Live channel 23.3 to 192.168.1.67 starting at 0MB
20210410-02:17:48 Recorded: directory /volume1/HDHomeRunDVR/ with 0 subdirs and 0 recordings
20210410-02:18:00 Recording: stop Live channel 23.3 9873f0bf (result = 0x0000)
20210410-02:18:00 Recording: early end of Live channel 23.3 9873f0bf
20210410-02:18:00 Recording: starting new file Live channel 8.3 32822d74
20210410-02:18:00 Recording: sending request to 106337BB at 192.168.1.66 for Live channel 8.3 32822d74
20210410-02:18:00 Recording: recording stated Live channel 8.3 32822d74
20210410-02:18:00 Playback: Streaming: Live channel 8.3 to 192.168.1.67 starting at 0MB
20210410-02:18:04 Recording: sending discover using local ip 192.168.1.87
20210410-02:18:04 Recording: sending discover using local ip 192.168.1.87
20210410-02:18:04 Recording: discover response from AE85F93D-4DD8-5994-27FA-0E6311D1C1EF http://192.168.1.87:59090
20210410-02:18:04 Recording: discover response from 106337BB http://192.168.1.66:80
20210410-02:18:04 Recorded: recorded sync to record-api.hdhomerun.com
20210410-02:18:04 Recording: event download from record-api.hdhomerun.com
20210410-02:18:04 Recording: 106337BB lineup request success (found 40 channels)
20210410-02:18:04 System: server time = Sat Apr 10 02:18:04 2021 (correction of -1s)
20210410-02:18:04 Recorded: recorded sync success
20210410-02:18:05 System: server time = Sat Apr 10 02:18:05 2021 (correction of 0s)
20210410-02:18:05 Recording: record Killer Cases S01E02 20201210 [20210410-0200] on 8.3 (1000000 3)
20210410-02:18:05 Recording: event download success
20210410-02:18:05 Recording: disk space available = 724GB
20210410-02:18:05 Recording: current time = Sat Apr 10 02:18:05 2021 (correction of 0s)
20210410-02:18:05 Recording: event Killer Cases S01E02 20201210 [20210410-0200] creating new worker
20210410-02:18:05 Recording: overlapping recordings Live channel 8.3 32822d74 Killer Cases S01E02 20201210 [20210410-0200]
20210410-02:18:05 Recording: next timer event in 0h42m25s
20210410-02:18:05 Recording: late start of Killer Cases S01E02 20201210 [20210410-0200]
20210410-02:18:05 Recording: recording stated Killer Cases S01E02 20201210 [20210410-0200]
20210410-02:18:06 Recorded: directory /volume1/HDHomeRunDVR/ with 1 subdirs and 0 recordings
20210410-02:18:06 Recorded: directory /volume1/HDHomeRunDVR/Killer Cases/ with 0 subdirs and 1 recordings
20210410-02:18:30 Status: Resource: nbk=1 dmk=231
20210410-02:18:30 Status: Disk read: MB=10 MB/s=39 worst=35
20210410-02:18:30 Status: Disk write: MB=19 MB/s=21 worst=41 queue=0MB/0/0 peak=0MB/25/2
20210410-02:18:30 Status: Recording: Killer Cases S01E02 20201210 [20210410-0200] from 106337BB (8MB)
20210410-02:18:30 Status: Recording: Live channel 8.3 32822d74 from 106337BB (9MB)
20210410-02:18:30 Status: Streaming: Live channel 8.3 to 192.168.1.67
20210410-02:20:30 Status: Resource: nbk=1 dmk=231
20210410-02:20:30 Status: Disk read: MB=30 MB/s=47 worst=103
20210410-02:20:30 Status: Disk write: MB=60 MB/s=16 worst=114 queue=0MB/0/0 peak=0MB/27/2
20210410-02:20:30 Status: Recording: Killer Cases S01E02 20201210 [20210410-0200] from 106337BB (38MB)
20210410-02:20:30 Status: Recording: Live channel 8.3 32822d74 from 106337BB (39MB)
20210410-02:20:30 Status: Streaming: Live channel 8.3 to 192.168.1.67
20210410-02:20:46 System: server time = Sat Apr 10 02:20:46 2021 (correction of 0s)
20210410-02:20:46 Recording: Live channel 8.3 32822d74: guide metadata retrieved, end time = Sat Apr 10 03:00:00 2021
20210410-02:22:30 Status: Resource: nbk=1 dmk=232
20210410-02:22:30 Status: Disk read: MB=32 MB/s=67 worst=15
20210410-02:22:30 Status: Disk write: MB=65 MB/s=16 worst=133 queue=0MB/0/0 peak=0MB/56/2
20210410-02:22:30 Status: Recording: Killer Cases S01E02 20201210 [20210410-0200] from 106337BB (70MB)
20210410-02:22:30 Status: Recording: Live channel 8.3 32822d74 from 106337BB (71MB)
20210410-02:22:30 Status: Streaming: Live channel 8.3 to 192.168.1.67
20210410-02:24:08 Recorded: recorded sync to record-api.hdhomerun.com
20210410-02:24:08 System: server time = Sat Apr 10 02:24:08 2021 (correction of 0s)
20210410-02:24:08 Recorded: recorded sync success
20210410-02:24:30 Status: Resource: nbk=1 dmk=233
20210410-02:24:30 Status: Disk read: MB=37 MB/s=68 worst=1
20210410-02:24:30 Status: Disk write: MB=74 MB/s=17 worst=99 queue=0MB/0/0 peak=0MB/44/2
20210410-02:24:30 Status: Recording: Killer Cases S01E02 20201210 [20210410-0200] from 106337BB (107MB)
20210410-02:24:30 Status: Recording: Live channel 8.3 32822d74 from 106337BB (108MB)
20210410-02:24:30 Status: Streaming: Live channel 8.3 to 192.168.1.67
20210410-02:26:30 Status: Resource: nbk=1 dmk=233
20210410-02:26:30 Status: Disk read: MB=34 MB/s=63 worst=17
20210410-02:26:30 Status: Disk write: MB=69 MB/s=16 worst=120 queue=0MB/0/0 peak=0MB/39/2
20210410-02:26:30 Status: Recording: Killer Cases S01E02 20201210 [20210410-0200] from 106337BB (141MB)
20210410-02:26:30 Status: Recording: Live channel 8.3 32822d74 from 106337BB (142MB)
20210410-02:26:30 Status: Streaming: Live channel 8.3 to 192.168.1.67
Re: Synology SPK for DVR Record Engine
'Unable to discover DVR status' or 'Unable to discover DVR version' are typically when the web interface can't execute the hdhomerun_record binary due to permissionsjayleekay wrote: ↑Fri Apr 09, 2021 7:32 pm I have something odd going on. I decided to come back to your package after using the SD version for a while.
I deleted all of my HDHomeRun shares and freshly installed 1.0.2. When I access the gui I get "unable to discover DVR version". I also get "Error: recoding path is invalid" under Record Engine Logs. At the bottom of the gui I see "Unable to discover DVR status"
However, with that being said, I'm currently recording a show and my log doesn't appear to show any errors. So I guess everything is working but the gui is just wonky?
I recreated the share in DSM following your steps. I also chown'd the folder volume1/HDHomeRunDVR as hdhomerundvr:http
The error on recording path is invalid typically means the web app can't read the conf file
Either an older version is running from /tmp or something is up with permissions.
Could be open_basedir in php.ini has been set to something (needs to be either blank or folders added for the conf and recordpath)
Re: Synology SPK for DVR Record Engine
Finally got around to do some testing and can confirm it fully worked for me when previously installed on DSM 6.x and did an upgrade to DSM 7 on two different model diskstations.
I was making some changes today and removed your hdhomerun package and when reinstalling, it said invalid format for the package spk.
So... I can confirm it worked on two different model diskstations, but it had to be installed prior to updating to DSM 7.
Unfortunately now I can't reinstall install it since I am on DSM beta on both diskstations. Any ideas on the new package requirements to get this to install?
Thanks!
I was making some changes today and removed your hdhomerun package and when reinstalling, it said invalid format for the package spk.
So... I can confirm it worked on two different model diskstations, but it had to be installed prior to updating to DSM 7.
Unfortunately now I can't reinstall install it since I am on DSM beta on both diskstations. Any ideas on the new package requirements to get this to install?
Thanks!
Re: Synology SPK for DVR Record Engine
no idea - sorry.. been avoiding going near the DSM7 beta for this exact reason.MNOiSY wrote: ↑Sun Apr 25, 2021 1:01 pm Finally got around to do some testing and can confirm it fully worked for me when previously installed on DSM 6.x and did an upgrade to DSM 7 on two different model diskstations.
I was making some changes today and removed your hdhomerun package and when reinstalling, it said invalid format for the package spk.
So... I can confirm it worked on two different model diskstations, but it had to be installed prior to updating to DSM 7.
Unfortunately now I can't reinstall install it since I am on DSM beta on both diskstations. Any ideas on the new package requirements to get this to install?
Thanks!
You will need to either manually install or maybe SDs installer works?
Re: Synology SPK for DVR Record Engine
The normal hdhomerun installer works without issues....so far.
Re: Synology SPK for DVR Record Engine
Wow. I swear I emptied the open_basedir field but I guess in my troubleshooting I left some items in there based on another suggestion. Once I removed everything, stopped and restarted the package everything works again. Thanks!demonrik wrote: ↑Sat Apr 17, 2021 1:54 pm'Unable to discover DVR status' or 'Unable to discover DVR version' are typically when the web interface can't execute the hdhomerun_record binary due to permissionsjayleekay wrote: ↑Fri Apr 09, 2021 7:32 pm I have something odd going on. I decided to come back to your package after using the SD version for a while.
I deleted all of my HDHomeRun shares and freshly installed 1.0.2. When I access the gui I get "unable to discover DVR version". I also get "Error: recoding path is invalid" under Record Engine Logs. At the bottom of the gui I see "Unable to discover DVR status"
However, with that being said, I'm currently recording a show and my log doesn't appear to show any errors. So I guess everything is working but the gui is just wonky?
I recreated the share in DSM following your steps. I also chown'd the folder volume1/HDHomeRunDVR as hdhomerundvr:http
The error on recording path is invalid typically means the web app can't read the conf file
Either an older version is running from /tmp or something is up with permissions.
Could be open_basedir in php.ini has been set to something (needs to be either blank or folders added for the conf and recordpath)
Re: Synology SPK for DVR Record Engine
Still working on dsm 7 with hdhomerun software. At least thats a good starting point!
It looks like only the package installer will have to be updated since it ran fine as long as it was installed prior to a dsm 7 upgrade.
Thanks again for all of your hard work!
Re: Synology SPK for DVR Record Engine
Am hoping it's something minor and thus easy to fixMNOiSY wrote: ↑Wed Apr 28, 2021 7:35 pmStill working on dsm 7 with hdhomerun software. At least thats a good starting point!
It looks like only the package installer will have to be updated since it ran fine as long as it was installed prior to a dsm 7 upgrade.
Thanks again for all of your hard work!
Hoping now docker is getting more and more arm support for M1 we'll see synology and qnap update their container solutions for arm CPUs and maybe we can all move to the container version instead ..
-
- Posts: 4
- Joined: Tue Jun 01, 2021 2:51 pm
Re: Synology SPK for DVR Record Engine
forgive the ignorance here, but I have this successfully installed on my synology drive but no clue what to do next. I am trying to configure Plex, which is also on my drive to record onto the DVR manager I just installed using your instructions. I must be missing something here.
Re: Synology SPK for DVR Record Engine
Firstly,scottywatty wrote: ↑Tue Jun 01, 2021 2:58 pm forgive the ignorance here, but I have this successfully installed on my synology drive but no clue what to do next. I am trying to configure Plex, which is also on my drive to record onto the DVR manager I just installed using your instructions. I must be missing something here.
You don't need to install the SD DVR if you plan to use Plex as your DVR manager - is a completely different installation.
If you need help using Plex as DVR - suggest you post in the 3rd party forum
Once you install the DVR - there isn't really much you should need to do other than open up the SD app and start selecting things to record.
You can use the UI on the NAS to configure some basic things around the DVR - but only really needed should you experience issues, or want to do some more advanced config things.
Re: Synology SPK for DVR Record Engine
DSM 7 has now published a Release Candidate. You may consider to start now porting the package to the new version.demonrik wrote: ↑Wed Apr 28, 2021 9:21 pmAm hoping it's something minor and thus easy to fixMNOiSY wrote: ↑Wed Apr 28, 2021 7:35 pmStill working on dsm 7 with hdhomerun software. At least thats a good starting point!
It looks like only the package installer will have to be updated since it ran fine as long as it was installed prior to a dsm 7 upgrade.
Thanks again for all of your hard work!
Hoping now docker is getting more and more arm support for M1 we'll see synology and qnap update their container solutions for arm CPUs and maybe we can all move to the container version instead ..