Volunteers to test new DVR build?

done on Mac mini running 10.11.6

I’ll update this evening to test (on the ancient mini) before recordings start.

@tmm1 I installed this update at 14:51. Newshour, which starts at 15:00 hours DID NOT record; rather, the second airing at 18:00 is queued. This is not normal (but not an issue for me as it is going to record the second airing).

2017/03/16 14:51:44 [DVR] Recording engine stopped.
2017/03/16 14:51:46 [SYS] Starting Channels DVR v2017.03.16.1820 (linux-x86_64) in /share/CACHEDEV1_DATA/.qpkg/ChannelsDVR/channels-dvr/data
2017/03/16 14:51:47 [HDR] Found 3 devices
2017/03/16 14:51:48 [SYS] Started HTTP Server
2017/03/16 14:51:50 [DVR] Recording engine started in /share/CACHEDEV1_DATA/Public/ChannelsDvrRecordings
2017/03/16 14:51:50 [SYS] Bonjour service running for dvr-momster.local. [192.168.168.193]
2017/03/16 14:51:50 [SYS] Removing old update 2017.03.01.2225
2017/03/16 14:51:50 [SYS] Created database snapshot: backup-20170316.145150
2017/03/16 14:51:50 [SYS] Removing old backup backup-20170308.165131
2017/03/16 14:52:01 [IDX] Pruned 626 expired airings from USA-OTA94303 in 1.218130949s.

Hmm… I’m surprised it didn’t say “Waiting for next job…” on boot.

What does the DVR schedule tab say? Does it list the 15:00 job still? Is there a job listed at 18:00?

Installed on WD PR2100…Will report anything out of the ordinary.

The DVR schedule tab does not list the 15:00 job. It does list the 18:00 job.

It may just be skipping the next job. If so, you’ll be hearing from others. The 18:00 Newshour airing gets recorded if I delete the 15:00 recording before it finishes, so I would see this behavior if the install skipped the next job.

I found one bug in this version… if you use web player to watch a live tv channel, the tuner is not released until 10s after you stop watching. Pretty minor bug. Everything else seems fine so far.

Ancient mac mini is chugging along as expected. Queued recording started on time, additiional new recordings started fine. Transcoder working as before.

Gee, and I was really wishing that the mac fairy would descend and convert mine to an i-7, didnt happen. Oh well.

This is failing on my Synology. I can’t get it to run correctly.

Huh? What’s not running? What’s happening?

It stopped running, and I can’t get the package to start anymore. It just fails.

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?