Recordings listed twice, crashes when deleting

Help and support for HDHomeRun DVR and HDHomeRun software for Windows 10, Mac, Android, XBox, etc.
Post Reply
SpiceWare
Posts: 12
Joined: Thu Nov 16, 2017 5:04 pm

Recordings listed twice, crashes when deleting

Post by SpiceWare » Thu Oct 31, 2019 1:07 pm

I have a Mac mini set up as my DVR. It stores all recordings on a Drobo 8D, over 9 TB worth.

For quite some time when running HDHomeRun on the mini all the recordings get listed twice. If I run HDHomeRun on my Mac Pro or iPad they're all listed just once. The mini's connected to my TV, and is the primary system I use to watch HDHomeRun.

The duplicate listings hasn't been much of an issue, but after the recent update (love the updated progress bar) when I delete a recording on the mini HDHomeRun will sometimes crash. I can delete recordings without crashing on my Mac Pro.

Each recording listed twice on mini:
Image

HDHomeRun sometimes crashes on mini when deleting a recording:
Image

Only one of each episode on the Drobo:
Image

Each recording listed once on the Mac Pro:
Image

Preferences on mini:
Image

Account Info on mini:
Image

I also have a 2nd Connect Quatro, 1071392F, but it stopped working last week - it just shows a flashing red light on the network port. I deleted it from the Account Info screen so it would stop prompting me about it every time I launched HDHomeRun.

jasonl
Silicondust
Posts: 14712
Joined: Sun Oct 28, 2007 9:23 pm

Re: Recordings listed twice, crashes when deleting

Post by jasonl » Thu Oct 31, 2019 2:17 pm

Looks like the app is finding the DVR via two different addresses and isn't recognizing they're the same DVR. I have brought this up to the development team to investigate.

SpiceWare
Posts: 12
Joined: Thu Nov 16, 2017 5:04 pm

Re: Recordings listed twice, crashes when deleting

Post by SpiceWare » Thu Oct 31, 2019 5:34 pm

Good eye - on my Mac Pro and iPad the Account Info screen only shows 1 instance of RECORD.

I just opened/close HDHomeRun on my Pro, then on my mini, log in the code box at end of this reply. In the log I see:
  • IP address of the Pro is 10.1.10.72, which matches the streaming of live channel 2.1
  • IP address of the mini is 10.1.10.223, but the streaming of live channel 26.1 is going to 169.254.103.7
Second code box at end of reply is output of ifconfig command. I see 169.254.103.7 in there under en1. Checked the network preferences and found that it's associated with WiFi, though WiFi is turned off.

Image

Image


HDHomeRun log file

Code: Select all

HDHomeRun RECORD 20190815beta1 OSX B2BBEF73-FD57-3A59-5EB7-062D58C7AEFA
20191101-00:01:05 Status: Resource: nbk=0 dmk=7007
20191101-00:01:06 Recorded: directory /Volumes/DVR/HDHomeRun/ with 37 subdirs and 0 recordings
20191101-00:03:05 Status: Resource: nbk=0 dmk=7007
20191101-00:05:05 Status: Resource: nbk=0 dmk=7007
20191101-00:07:05 Status: Resource: nbk=0 dmk=7007
20191101-00:09:06 Status: Resource: nbk=0 dmk=7007
20191101-00:09:08 Recording: starting new file Live channel 2.1 293e9a5b
20191101-00:09:08 Recording: sending request to 1070F456 at 10.1.10.38 for Live channel 2.1 293e9a5b
20191101-00:09:08 Recording: recording stated Live channel 2.1 293e9a5b
20191101-00:09:08 Playback: Streaming: Live channel 2.1 to 10.1.10.72 starting at 0MB
20191101-00:09:24 Recording: stop Live channel 2.1 293e9a5b (result = 0x0000)
20191101-00:09:24 Recording: early end of Live channel 2.1 293e9a5b
20191101-00:11:06 Recording: starting new file Live channel 26.1 ac7fbd4a
20191101-00:11:06 Recording: sending request to 1070F456 at 10.1.10.38 for Live channel 26.1 ac7fbd4a
20191101-00:11:06 Status: Resource: nbk=1 dmk=7010
20191101-00:11:06 Status: Disk read: MB=9 MB/s=511 worst=1
20191101-00:11:06 Status: Disk write: MB=26 MB/s=120 worst=1
20191101-00:11:06 Status: Streaming: Live channel 26.1 to 169.254.103.7 (0MB)
20191101-00:11:06 Recording: recording stated Live channel 26.1 ac7fbd4a
20191101-00:11:06 Playback: Streaming: Live channel 26.1 to 169.254.103.7 starting at 0MB
20191101-00:11:22 Recording: stop Live channel 26.1 ac7fbd4a (result = 0x0000)
20191101-00:11:22 Recording: early end of Live channel 26.1 ac7fbd4a

ifconfig output

Code: Select all

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
VHC128: flags=0<> mtu 0
XHC1: flags=0<> mtu 0
XHC20: flags=0<> mtu 0
XHC0: flags=0<> mtu 0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
	ether f0:18:98:ee:80:9b 
	inet6 fe80::1865:7118:4106:7b43%en0 prefixlen 64 secured scopeid 0x8 
	inet6 2603:300c:1601:cc00:1cba:1a4a:c57b:8954 prefixlen 64 autoconf secured 
	inet6 2603:300c:1601:cc00::e4a4 prefixlen 64 dynamic 
	inet 10.1.10.223 netmask 0xffffff00 broadcast 10.1.10.255
	inet6 2603:300c:1601:cc00:98b8:b4e:4cde:9d35 prefixlen 64 deprecated autoconf temporary 
	inet6 2603:300c:1601:cc00:80af:c317:12c6:c239 prefixlen 64 deprecated autoconf temporary 
	inet6 2603:300c:1601:cc00:2838:2f49:90b9:7023 prefixlen 64 deprecated autoconf temporary 
	inet6 2603:300c:1601:cc00:f4c7:9d7a:bd12:e2d4 prefixlen 64 deprecated autoconf temporary 
	inet6 2603:300c:1601:cc00:f077:e3d2:6d73:f7a9 prefixlen 64 deprecated autoconf temporary 
	inet6 2603:300c:1601:cc00:4d83:5fbf:9377:63a0 prefixlen 64 deprecated autoconf temporary 
	inet6 2603:300c:1601:cc00:51ee:abb1:f4a8:97f0 prefixlen 64 autoconf temporary 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (1000baseT <full-duplex,flow-control>)
	status: active
en6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether ac:de:48:00:11:22 
	inet6 fe80::aede:48ff:fe00:1122%en6 prefixlen 64 scopeid 0x9 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex>)
	status: active
ap1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
	ether 3a:f9:d3:17:a4:19 
	media: autoselect
	status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 38:f9:d3:17:a4:19 
	inet6 fe80::c84:3f6a:3ae5:1f56%en1 prefixlen 64 secured scopeid 0xb 
	inet 169.254.103.7 netmask 0xffff0000 broadcast 169.254.255.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (<unknown type>)
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
	ether 0a:f9:d3:17:a4:19 
	media: autoselect
	status: inactive
awdl0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1484
	ether ea:b4:c0:41:9a:23 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether be:00:e8:c0:af:01 
	media: autoselect <full-duplex>
	status: inactive
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether be:00:e8:c0:af:00 
	media: autoselect <full-duplex>
	status: inactive
en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether be:00:e8:c0:af:05 
	media: autoselect <full-duplex>
	status: inactive
en5: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether be:00:e8:c0:af:04 
	media: autoselect <full-duplex>
	status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether be:00:e8:c0:af:01 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x2
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 14 priority 0 path cost 0
	member: en3 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 15 priority 0 path cost 0
	member: en4 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 16 priority 0 path cost 0
	member: en5 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 17 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::f89a:c792:7e9f:196b%utun0 prefixlen 64 scopeid 0x13 
	nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::e171:ff9c:c1dd:f89%utun1 prefixlen 64 scopeid 0x14 
	nd6 options=201<PERFORMNUD,DAD>

SpiceWare
Posts: 12
Joined: Thu Nov 16, 2017 5:04 pm

Re: Recordings listed twice, crashes when deleting

Post by SpiceWare » Thu Oct 31, 2019 7:02 pm

Problem solved!

Was talking with a friend who works IT at a law firm with a bunch of Mac equipment - he's actually why I own Macs, he gave me a PowerMac G3 back in 2003 so I could try OS X when I was deciding what to use after having run OS/2 for almost a decade.

Anyway, he asked "Can you work around it by deleting the WiFi item in the Network system preference?"

I didn't realize that was possible. Just select Wi-Fi in the panel on the left, then click on the minus at the bottom to delete it, finally click on Apply. Once done, I launched the HDHomeRun client on the mini and it showed just one HDHomeRun RECORD, and I was able to delete a number of recordings without the client crashing.

Image

Post Reply