Volunteers to test new DVR build?

SSH in and check the Log:

tail -25 /volume1/@appstore/ChannelsDVR/channels-dvr/data/channels-dvr.log

2017/03/16 20:25:14 [DVR] Commercial detection finished with 8 markers.
2017/03/16 20:30:01 [DVR] Finished job 1489708800-64 Superstore
2017/03/16 20:30:01 [DVR] Waiting 30m58.731872888s until next job 1489712460-110
2017/03/16 20:30:01 [DVR] Processing file-928: TV/Superstore/2017-03-16-2000 Superstore 2017-03-16 S02E17 Integrity Award.mpg
2017/03/16 20:30:03 [DVR] Running commercial detection on file 928 (TV/Superstore/2017-03-16-2000 Superstore 2017-03-16 S02E17 Integrity Award.mpg)
2017/03/16 20:54:13 [DVR] Commercial detection finished with 8 markers.
2017/03/16 20:55:08 [DVR] Job cancelled: 1489708800-ch67.1
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x4c6046]

goroutine 466 [running]:
panic(0xb2a4c0, 0xc42000c070)
/home/vagrant/go/src/runtime/panic.go:500 +0x1a1
time.(*Timer).Reset(0x0, 0x2540be400, 0xa48)
/home/vagrant/go/src/time/sleep.go:106 +0x26
_/home/vagrant/channels-server-x86_64/hdhr.(*Stream).Read(0xc420558be0, 0xc421910000, 0x8000, 0x8000, 0xa48, 0x0, 0x0)
/home/vagrant/channels-server-x86_64/hdhr/device.go:544 +0x3c
io.copyBuffer(0x128c280, 0xc420024ff0, 0x128b1c0, 0xc420558be0, 0xc421910000, 0x8000, 0x8000, 0xc420bfb7a0, 0xc420bfb710, 0xc421d024e0)
/home/vagrant/go/src/io/io.go:390 +0x147
io.Copy(0x128c280, 0xc420024ff0, 0x128b1c0, 0xc420558be0, 0x5e7d7d, 0x180001, 0x0)
/home/vagrant/go/src/io/io.go:360 +0x68
github.com/djherbis/nio.NewReader.func1(0xc420024ff0, 0x128b1c0, 0xc420558be0)
/home/vagrant/channels-server-x86_64/.go/src/github.com/djherbis/nio/nio.go:48 +0x4b
created by github.com/djherbis/nio.NewReader
/home/vagrant/channels-server-x86_64/.go/src/github.com/djherbis/nio/nio.go:50 +0x153

I’m going to have to uninstall this.

Which doesn’t seem to fix this. I am not sure what is going on. This may have started when I cancelled a PBS recording that was currently running. Then the web-ui got all wonky and couldn’t find my HDHRs. Then it crashed. I can still access my HDHomeruns via the channels app. Need to get the DVR running again.

OK. I am now reinstalled and restored from backup. Using 2017.03.13.2338. Something in the new build caused my package to crash and unable to be restarted. I had to restart my DiskStation too.

Good thing you didn’t push this out to everyone as an automatic update!

1 Like

How to install on WD MyCloud EX2? I’ll try it out.

For windows would you do this via powershell?
-Thanks!

I updated the command in the first post with a new version, 2017.03.17.0225. This contains a fix for the bug @djcastaldo ran into.

Just tried and I left an episode playing last night . After stopping it , the update is still waiting to install.

  1. How long before it checks that it’s now idle?
  2. Is there a manual command?

It did finally update. I got a bunch scheduled.

Just so you have another record, here’s what I ran into as well. I also noticed that the service was unresponsive, but I was able to Stop the service, then restart the service.

2017/03/16 17:00:56 [SYS] Downloading new version v2017.03.16.1820
2017/03/16 17:01:18 [SYS] Update downloaded and verified successfully.
2017/03/16 17:01:18 [SYS] Shutting down for upgrade from v2017.03.13.2338 to v2017.03.16.1820
2017/03/16 17:01:18 [DVR] Recording engine stopped.
2017/03/16 17:01:19 [SYS] Starting Channels DVR v2017.03.16.1820 (linux-x86_64) in /share/CACHEDEV1_DATA/.qpkg/ChannelsDVR/channels-dvr/data
2017/03/16 17:01:20 [HDR] Found 3 devices
2017/03/16 17:01:26 [SYS] Started HTTP Server
2017/03/16 17:01:29 [DVR] Recording engine started in /share/CACHEDEV9_DATA/ChannelsDVR
2017/03/16 17:01:29 [DVR] Waiting 2h57m30.020695733s until next job 1489708740-4
2017/03/16 17:01:29 [ERR] bonjour: no suitable IPv6 interface: listen udp6 [ff02::]:5353: socket: address family not supported by protocol
2017/03/16 17:01:29 [SYS] Bonjour service running for dvr-core-nas.local. [192.168.25.154]
2017/03/16 17:01:29 [SYS] Removing old update 2017.03.01.2225
2017/03/16 17:01:30 [SYS] Created database snapshot: backup-20170316.170129
2017/03/16 17:01:30 [SYS] Removing old backup backup-20170303.200435
2017/03/16 17:01:40 [IDX] Pruned 313 expired airings from USA-OTA23072 in 694.740235ms.
2017/03/16 17:06:22 [HLS] Starting transcoder for file-83 at 0s (encoder=h264_vaapi, resolution=, deinterlacer=blend, bitrate=10000)
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: va_openDriver() returns 0
[mpegts @ 0x2863bc0] Dropped corrupted packet (stream = 1)
[mpegts @ 0x2863bc0] Dropped corrupted packet (stream = 2)
Unrepairable overflow!
2017/03/16 17:09:01 [HLS] Stopping transcoder session file-83 @ 3m46.292744s
2017/03/16 17:48:34 [DVR] Deleting /share/CACHEDEV9_DATA/ChannelsDVR/TV/The Voice/2017-03-14-1959 The Voice 2017-03-14 S12E07 Blind Auditions Part 7.mpg
2017/03/16 19:23:11 [DVR] Deleting /share/CACHEDEV9_DATA/ChannelsDVR/TV/The Voice/2017-03-15-1959 The Voice 2017-03-15 S12E08 Best of the Blind Auditions.mpg
2017/03/16 19:59:00 [DVR] Starting job 1489708740-4 Grey's Anatomy on ch=[13.1]
2017/03/16 19:59:00 [DVR] Waiting 59m59.990385149s until next job 1489712340-2
2017/03/16 19:59:00 [DVR] Recording for job 1489708740-4 from 10485F68 ch13.1 into "TV/Grey's Anatomy/2017-03-16-1959 Grey's Anatomy 2017-03-16 S13E16 Who Is He And What Is He to You.mpg" for 1h6m59.990074181s
2017/03/16 20:07:21 [DVR] Deleting /share/CACHEDEV9_DATA/ChannelsDVR/TV/NCIS/2017-03-14-1959 NCIS 2017-03-14 S14E18 MIA.mpg
2017/03/16 20:59:00 [DVR] Starting job 1489712340-2 Chicago Med on ch=[10.1]
2017/03/16 20:59:00 [DVR] Waiting 59m59.993947758s until next job 1489715940-17
2017/03/16 20:59:00 [DVR] Recording for job 1489712340-2 from 10485F68 ch10.1 into "TV/Chicago Med/2017-03-16-2059 Chicago Med 2017-03-16 S02E17 Monday Mourning.mpg" for 1h5m59.993664414s
2017/03/16 21:04:28 [DVR] Job cancelled: 1489708740-4
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x4c6046]

goroutine 445 [running]:
panic(0xb2a4c0, 0xc42000c0a0)
	/home/vagrant/go/src/runtime/panic.go:500 +0x1a1
time.(*Timer).Reset(0x0, 0x2540be400, 0x524)
	/home/vagrant/go/src/time/sleep.go:106 +0x26
_/home/vagrant/channels-server-x86_64/hdhr.(*Stream).Read(0xc420498000, 0xc42069a000, 0x8000, 0x8000, 0x524, 0x0, 0x0)
	/home/vagrant/channels-server-x86_64/hdhr/device.go:544 +0x3c
io.copyBuffer(0x128c280, 0xc421820020, 0x128b1c0, 0xc420498000, 0xc42069a000, 0x8000, 0x8000, 0xc420593fa0, 0xc420593f10, 0xc4217dbce0)
	/home/vagrant/go/src/io/io.go:390 +0x147
io.Copy(0x128c280, 0xc421820020, 0x128b1c0, 0xc420498000, 0x5e7d7d, 0x180001, 0x0)
	/home/vagrant/go/src/io/io.go:360 +0x68
github.com/djherbis/nio.NewReader.func1(0xc421820020, 0x128b1c0, 0xc420498000)
	/home/vagrant/channels-server-x86_64/.go/src/github.com/djherbis/nio/nio.go:48 +0x4b
created by github.com/djherbis/nio.NewReader
	/home/vagrant/channels-server-x86_64/.go/src/github.com/djherbis/nio/nio.go:50 +0x153
2017/03/17 19:26:54 [SYS] Starting Channels DVR v2017.03.16.1820 (linux-x86_64) in /share/CACHEDEV1_DATA/.qpkg/ChannelsDVR/channels-dvr/data
2017/03/17 19:26:55 [HDR] Found 3 devices
2017/03/17 19:27:00 [SYS] Started HTTP Server
2017/03/17 19:27:03 [DVR] Recording engine started in /share/CACHEDEV9_DATA/ChannelsDVR
2017/03/17 19:27:03 [ERR] bonjour: no suitable IPv6 interface: listen udp6 [ff02::]:5353: socket: address family not supported by protocol
2017/03/17 19:27:03 [SYS] Bonjour service running for dvr-core-nas.local. [192.168.25.154]
2017/03/17 19:27:03 [DVR] Processing file-84: TV/Grey's Anatomy/2017-03-16-1959 Grey's Anatomy 2017-03-16 S13E16 Who Is He And What Is He to You.mpg
2017/03/17 19:27:03 [DVR] Deleting expired job 1489712340-2
2017/03/17 19:27:03 [DVR] Deleting expired job 1489715940-17
2017/03/17 19:27:04 [DVR] Running commercial detection on file 84 (TV/Grey's Anatomy/2017-03-16-1959 Grey's Anatomy 2017-03-16 S13E16 Who Is He And What Is He to You.mpg)
2017/03/17 19:27:15 [IDX] Pruned 1079 expired airings from USA-OTA23072 in 2.451636137s.
1 Like

Since the big changes in the last build are working pretty well, I was able to start implementing some cool new stuff.

In this new build, the DVR has basic tuner sharing capability. This means if you have two back-to-back shows on the same channel set to record, and they both have padding so they overlap, only one tuner is used instead of two!

Upgrade by running this command:

windows (in powershell)

Invoke-WebRequest -Method Put http://127.0.0.1:8089/updater/check/2017.03.18.0237

mac/linux

curl -XPUT http://127.0.0.1:8089/updater/check/2017.03.18.0237

3 Likes

This is very cool, one of the features I’ve missed. I have updated this morning. It looks like I have 2 recordings scheduled to record tomorrow night back to back on the same channel, but I will do some testing today to see how things are working.

As always, thank you and your team for all of the hard work.

I was able to successfully record 6 1/2 hr shows and 1 1-hr show on my 4 tuners. My default padding is 30s on the front and none on the back.

Obviously haven’t viewed all the content yet, but the front end on all started fine.

Saw 503s in the log. But the shows recorded. Thought they wouldn’t exist after this patch.

Tested 3 shows wiith another 3 back to back. Used 3,5,15 minutes. All recorded perfectly with applicable overlaps. Even watched Live TV on one channel simultaneously while recording.

Very useful feature, thank you.

The broadcast channels that I record all start and end in accordance with the guide data. So I haven’t tested any of the new padding features. I can say that the DVR hasn’t hung and my recordings appear normal since installed yesterday night.

I had a couple sets of back to back recordings tonight. They ran perfectly without switching tuners. My latest signal setup uses two HDHRs that are connected to different antennas and prefer different channels (favorites are not the same on both). This new recording system is superior for this type of setup since the subsequent show no longer looks for a new tuner; It stays on the same tuner, same HDHR, without skipping a beat. This ensures that the preferred HDHR will continue to be used, regardless of other simultaneous programming. Wonderful.

3 Likes

Is this feature in the main build yet?

Yes, this feature is now in the normal build which was released this morning. See Release Notes

I just noticed this, as my system didn’t complain at 5 simultaneous recordings. Nice addition. Thanks!

1 Like