Quote:
Originally Posted by Calaveras 
I don't own an HDHR but I found this post at the TVFool forum:
http://forum.tvfool.com/showpost.php?p=8290&postcount=13
It appears to be the same as the error count on my Sony. You'd want that to be 100%, i.e. no errors after correction. Maybe you've captured the problem KGO is having with the translator since I don't see any signal strength or SNR problems in your graph.

I don't own an HDHR but I found this post at the TVFool forum:
http://forum.tvfool.com/showpost.php?p=8290&postcount=13
It appears to be the same as the error count on my Sony. You'd want that to be 100%, i.e. no errors after correction. Maybe you've captured the problem KGO is having with the translator since I don't see any signal strength or SNR problems in your graph.
Thanks... I also added graphing for transport errors (and some other errors, which seem mostly pretty low, and I started collecting data from other Mt. Allison stations; rf 42 (KAXT 1) http://ruka.org/~toast/atscdata/chart.php?c=42 rf 49 (KTST 48) http://ruka.org/~toast/atscdata/chart.php?c=49 and rf 51 (KDTV 14) http://ruka.org/~toast/atscdata/chart.php?c=51
There are only a couple data points on those last three right now, but if you view it in the morning it will have an overnight. Next up, time filters and/or comparisons between channels.


























It would seem to me that a ridge is a ridge.




I had to suppress my wanting to contact the station and complain (which I've never done for any TV station). However, I was certain I was going to do so after finishing watching my DVR timeshift of this 3 hour event. I called and left a VM for the station manager (I know that it will probably not get past an underling), and also left an "email" at their site, which went thus: