[majortom]

If you move your antenna around a little bit, assuming channel_scan is close, then it shouldn't take too much to get it below 100%, if it's truly close to 0dBmV now. Then u could really compare that one to the number that's based on the percentage.

 

[dheian]

Excellent work guys, thanks.

So this is funny: I'm currently getting WNYO pretty reliably with the reflected signal/HDHR3:

49      77      -13.8   -62.55  53      100     49.1    WNYO-HD         49.2    GetTV

but not the Buffalo-aimed/HDHR4:

49      67      -19.8   -68.55  42      100 (no id info)

Of course today's weather is off, temps over the lake are changing etc.

 

[majortom]

BTW, anyone have an idea why CBLT and CBLFT don't show up in TVFOool? Just noticed that.

dheian, in the tvfool that you linked to above, make sure to click on 'Pending Digital' and you will get what I would consider a more accurate prediction of current Canadian Stations.

 

[majortom]

schmick,
ya wanna see if this looks right to you?
I modified the script again to hopefully account for either device type.
basically test for the length of the dbg= string with an if(), and print the results one way or the other...
also using printf instead of print in the debug output.
I can't test the hdhr4 or the tc, but it looks right on my hdhr3.

http://pastebin.com/GFM4iJ02

 

[905shmick]

Looks good. Thanks for the work.

The changes have been pushed to github.

$ ./channel_scan.sh -D
debug mode

Beginning scan on 105281ED, tuner 0 at 04/11/15 14:09:46

Locking 105281ED, tuner 0 with key 12121212

Unocking 105281ED, tuner 0 with key 12121212

19 channels found
RF	Strngth	dBmV	dBm	Quality	SNR	Symbol	dbg	Calc_dBmV	Calc_dBm
--------------------------------------------------------------------------------------------
9	100	0.0	-48.8	98	32.3	100	-3450	11.1		-37.6
12	59	-24.6	-73.3	42	13.9	100	-6950	-23.6		-72.3
14	92	-4.8	-53.5	89	29.4	100	-5050	-4.7		-53.5
16	51	-29.4	-78.2	41	13.5	100	-7500	-29.0		-77.8
17	55	-27.0	-75.8	41	13.5	100	-7275	-26.8		-75.5
19	100	0.0	-48.8	98	32.3	100	-3900	6.7		-42.1
20	100	0.0	-48.8	100	33.0	100	-3350	12.1		-36.6
25	100	0.0	-48.8	100	33.0	100	-2850	17.1		-31.7
32	100	0.0	-48.8	100	33.0	100	-3250	13.1		-35.7
33	87	-7.8	-56.5	73	24.1	100	-5425	-8.5		-57.2
36	100	0.0	-48.8	68	22.4	100	-4700	-1.3		-50.0
38	100	0.0	-48.8	100	33.0	100	-4300	2.7		-46.1
39	100	0.0	-48.8	98	32.3	100	-4725	-1.5		-50.3
40	100	0.0	-48.8	100	33.0	100	-3250	13.1		-35.7
41	100	0.0	-48.8	98	32.3	100	-2525	20.3		-28.5
43	100	0.0	-48.8	100	33.0	100	-3875	6.9		-41.9
44	100	0.0	-48.8	100	33.0	100	-3100	14.6		-34.2
47	100	0.0	-48.8	98	32.3	100	-3250	13.1		-35.7
49	100	0.0	-48.8	98	32.3	100	-4725	-1.5		-50.3

 

[majortom]

thanks for reviewing and adding it to ur repo shmick

 

[dheian]

Thanks to both shmick and majortom.

Get to experiment with a DB4e soon. Can't wait.

 

[905shmick]

FYI - nickk from the Silicon Dust forum says:

Please do not use dbg numbers for signal strength reporting.

The meaning of the numbers varies between models, between units, and between frequencies.​

When I asked why not provide some insight into the values, the response was:

The problem is the numbers can't be used to report signal levels. The numbers vary between models (different scale/meaning), different units (factory calibration) and between different frequencies.
​

 

[majortom]

yeah I saw ur post over there asking him about it.
It seems close enough for me, regardless.

 

[905shmick]

Yep. Then he or someone else deleted the thread. Seems like an odd thing to do...

 

[majortom]

hmm, ya ur right I don't see it there any more. That IS strange.
Way I see it, one can either believe that every signal indicating SS=100 is exactly -48.8 dBm,
or ya can estimate what they really are. See no harm doing the latter.

 

[905shmick]

The folks at Silicondust have just launched a HDHomeRun DVR Kickstarter

 

[audacity]

I'm pleased to see another company throw their hat into the DVR software ring.

 

[905shmick]

I've backed the project at the $60 level. Hoping it can replace EyeTV for me.

 

[audacity]

EyeTV? Oh. Wow. I'm so sorry.

I'm probably not going to use their software myself, but I may back them just-for-the-heck-of-it.

 

[905shmick]

To be perfectly honest, EyeTV works pretty well for me, but it's got some oddities that I could do without. I've got things running pretty smooth with Remote Buddy handling all of the IR calls and passing them to EyeTV.

 

[ExDilbert]

It will be interesting to see how HDHomeRun DVR compares to existing products. I use NPVR with KODI. It's not 100% but it's pretty good with the latest stable releases. NPVR is very good by itself as well but lacks a few features that KODI adds. The one caveat I have about HDHomeRun DVR is that it has KODI support as a stretch feature. That's pretty much a must have for me. H.264 transcoding would be nice as well. That can currently be handled by a media server such as Plex.

 

[dheian]

I'd like to see hardware folks backing already existing projects like Myth. But competition is always good, even against an open source product.

 

[arrow201]

Synology does support the HDHomeRun if you run Synologys' "Video Station" plugin app. It also has a corresponding app for smart phones/tablets to setup recording schedules and will stream stations live directly without additional apps. What's bad is that "Video Station" doesn't have EPG for North America markets, so, scheduling all has to be typed in manually. From the screen shots, HDHomeRun DVR appears to be much slicker. Hope they bring it to Synology as it's (maybe) stated.

 

[gdkitty]

Not sure if this is the right spot or not for this..
Just saw this in a recent PLEX newsletter.

Looks like HDhomerun is working with plex, to make a channel which will allow programming and playback of the HD homerun from the plex interface.

https://www.kickstarter.com/project...ewsvol11_12&utm_campaign=Newsletter+Volume+11