I'm about to throw anything SilconDust in the trash compactor.
Seems they have a bias or strong hate (on their support forms at least) for users of Channels DVR, TVE, and especially Locast.
Ever since Channels DVR added this feature, it made me discover a recent issue I never realized i had.
I have posted over a week ago, to the S.D forms, for help and to look as the tuner diags i sent to them form my HDHR, as others do, to see if there is a fault or something i can do.....no response other than typical "anything can cause interference ..."
I have been unable to log into their form for well over a year now, keeps saying max attempts reached, password reset email takes days to get, reset pass, still 1st attempt, locks out. Maybe since i have dynamic ip my ip is banned? I have gotten zero responses to my emails to their moderator or company in the years time. but, i created a new account and logged in fine, to post my question. and that works fine.
I see that any chat on Locast, is either deleted or the words are *****....like they are blocking it. My old account posts when i was first discovering Channels DVR and got the OTA HDHR are also removed. Which is odd, cause, yes their own rules state no chat on things that do not use HDHR tuners, which, Channels does and I am. so, i'm confused.
Anyway, sorry if this is off topic a bit, but i feel it is related, and users should be aware of such issues trying to get support from the HDHomeRun's manufacture to help advise them with signal issues and general product support.
Meanwhile, I am having to supplement my Antenna OTA with Locast. Since I have no control over why my neighbors turn on and when. But, its very hard on my eyes to watch, so poor quality and at least on some channels, like CBS, near impossible to watch my recording of Swat from last night from it, due to its interlacing/ghosting like effect and lower framerate? not sure what they do to the feed, but it is just...not great.
This OP specific comment was moved from a different thread.
Here is my first posts on the issue in another thread.