racameron is right. Could just be a momentary signal loss due to interference.
Very hard to pinpoint unless you have a good spectrum analyzer, and then it could be the tuner itself, or its power supply, or nearby electronics, even fluorescent lighting interfering.
1 Like
I just replied to a post to them tonight, no response yet.
There are a lot of the "no video data" lines from both tuners.
They make great hardware, but seem to be lacking on selling and supporting it lately.
I have their Prime tuner and love it. Their support, not so much.
That's a lot of log data. If you search for no video data and correlate the timestamps (in UTC time) with your local time, do you see any particular time of day they happen at? There was a post in the SD forum of a guy who found LED lights on a dusk-dawn timer/sensor causing issues at night.
Here they are from your #1
20220819-02:33:40 HTTP: rejecting request from 192.168.1.180 - no video data
20220819-21:45:50 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-01:05:03 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-02:54:13 HTTP: rejecting request from 192.168.1.180 - no video data
20220823-01:48:17 HTTP: rejecting request from 192.168.1.180 - no video data
#2
20220819-02:33:49 HTTP: rejecting request from 192.168.1.180 - no video data
20220819-21:14:19 HTTP: rejecting request from 192.168.1.180 - no video data
20220819-21:45:58 HTTP: rejecting request from 192.168.1.180 - no video data
20220819-23:05:38 HTTP: rejecting request from 192.168.1.52 - no video data
20220822-01:05:11 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-17:00:39 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-17:00:50 HTTP: rejecting request from 192.168.1.180 - no video data
Thanks to my notepad++
If you noticed, there are times when both tuners failed to lock on a channel.
Tuner #1 Tuner #2
20220819-02:33:40 20220819-02:33:49
20220819-21:45:50 20220819-21:45:58
20220822-01:05:03 20220822-01:05:11
So doubt it's just one tuner. May be easier to see here.
Tuner #1 Runer #2
20220819-02:33:34 Tuner: tuner1 tuning 107.1 KETV (atsc3:563MHz-5005) 20220819-02:33:43 Tuner: tuner0 tuning 107.1 KETV (atsc3:563MHz-5005)
20220819-02:33:40 HTTP: rejecting request from 192.168.1.180 - no video data 20220819-02:33:49 HTTP: rejecting request from 192.168.1.180 - no video data
20220819-02:33:40 Tuner: tuner1 http stream ended (requested time reached) 20220819-02:33:49 Tuner: tuner0 http stream ended (requested time reached)
20220819-21:14:13 Tuner: tuner0 tuning 106.1 WOWT (atsc3:563MHz-5004)
20220819-21:14:19 HTTP: rejecting request from 192.168.1.180 - no video data
20220819-21:14:19 Tuner: tuner0 http stream ended (requested time reached)
20220819-21:45:44 Tuner: tuner0 tuning 106.1 WOWT (atsc3:563MHz-5004) 20220819-21:45:52 Tuner: tuner0 tuning 106.1 WOWT (atsc3:563MHz-5004)
20220819-21:45:50 HTTP: rejecting request from 192.168.1.180 - no video data 20220819-21:45:58 HTTP: rejecting request from 192.168.1.180 - no video data
20220819-21:45:50 Tuner: tuner0 http stream ended (requested time reached) 20220819-21:45:58 Tuner: tuner0 http stream ended (requested time reached)
20220819-23:05:32 Tuner: tuner0 tuning 107.1 KETV (atsc3:563MHz-5005)
20220819-23:05:38 HTTP: rejecting request from 192.168.1.52 - no video data
20220819-23:05:38 Tuner: tuner0 http stream ended (requested time reached)
20220822-01:04:57 Tuner: tuner0 tuning 107.1 KETV (atsc3:563MHz-5005) 20220822-01:05:05 Tuner: tuner1 tuning 107.1 KETV (atsc3:563MHz-5005)
20220822-01:05:03 HTTP: rejecting request from 192.168.1.180 - no video data 20220822-01:05:11 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-01:05:03 Tuner: tuner0 http stream ended (requested time reached) 20220822-01:05:11 Tuner: tuner1 http stream ended (requested time reached)
20220822-02:54:07 Tuner: tuner0 tuning 106.1 WOWT (atsc3:563MHz-5004)
20220822-02:54:13 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-02:54:13 Tuner: tuner0 http stream ended (requested time reached)
20220822-17:00:33 Tuner: tuner0 tuning 107.1 KETV (atsc3:563MHz-5005)
20220822-17:00:39 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-17:00:39 Tuner: tuner0 http stream ended (requested time reached)
20220822-17:00:44 Tuner: tuner0 tuning 103.1 KMTV (atsc3:563MHz-5006)
20220822-17:00:50 HTTP: rejecting request from 192.168.1.180 - no video data
20220822-17:00:50 Tuner: tuner0 http stream ended (requested time reached)
20220823-01:48:11 Tuner: tuner1 tuning 106.1 WOWT (atsc3:563MHz-5004)
20220823-01:48:17 HTTP: rejecting request from 192.168.1.180 - no video data
20220823-01:48:17 Tuner: tuner1 http stream ended (requested time reached)
"No Video Data" exactly what I had and Silicon Dust RMA'd the unit and sent me another one for free.
1 Like
I check the "Show Stats" every so often. What exactly do you want me to look for specifically for problems? Here is after 5 minutes or so...
Did the replacement unit(s) fix your issue? Any more "No Video Data" errors?
Yeah. I have 2 other hdhrs on the same 4 way splitter and they had zero issues. The kickstarter one started giving no video data sporadically until it just quit altogether. Funny thing was i bought another hdhr 4k to replace it and then thought, hey i should have just rma'd the old one. So after the replacement arrived, i have 2 hdhr 4k's and two 2 tuner hdhr's for a total of 12 tuners lol.
Took awhile for the forum to respond as I was was editing my post.
The File > Signal line is what Channels uses for the SNR log entries.
But honestly, from all of your previous posts, and then adding in associated anecdotal data from other users over the years, you are probably experiencing crappy reception at random times because of "things". Whether that means certain light fixtures turning on, a microwave being started, or even a neighbor's coffee maker, there might be something outside/external genuinely causing RF interference; such a situation is definitely not unheard of.
Also, regarding SiliconDust themselves: they like to think they're great. Their hardware is quite good, but the firmware for that hardware often has crazy small issues they refuse to acknowledge until a multitude speaks. They can do hardware well, but their software chops are severely lacking. (Have you ever tried to use their own TV client?; an abysmal experience I would only wish upon my own worst enemies. And their constant answer regarding promises from over a half-decade: where is DRM recording?!)
That should be enough tuners to get you by 
Thanks for the info. I opened a ticket with SD, will see where this goes.
I honestly don't think it's a reception issue. About a year ago I figured out that when a certain light switch was on in the house, 1 of my local stations signal dropped about 25-30%. I turn the switch back on and back up the signal went. Dropped from about 90% to 60%. I was pissed and happy at the same time that I figured that out. I immediately replaced the bulbs on that switch and the problem went away. I then tested every single bulb/switch in the house on/off with signal tests and found a couple troublesome lights (not nearly as bad, maybe 5-10% drop) and replaced those too. Lastly I found out that my low voltage lamps outside (oldest LED ones) were a problem, not the transformer, which I figured would cause a problem. I was happy because I didn't like the light they put out (dim and wrong color) so I replaced them all the next day. I don't have any florescent or CFL bulbs.
So to sum it up, I know things cause reception issues and I have replaced every lamp/fixture inside and out of my house to maximize reception quality.
SD replied to my ticket. They requested logs and diagnostics. This was their reply:
The logs don't indicate any kind of hardware issue with either HDHomeRun. All of the tuning issues in the logs have been specific to ATSC 3.0 channels, and it doesn't appear to be a signal issue since they seem to come in perfectly fine when they do work. We suspect that there may be an issue with the timing of some of the metadata coming from the broadcaster. The HDHomeRun will wait 5 seconds for audio and video to come in, which relies on a bunch of lower level things to come in from the broadcaster in time for that to happen. Normally those things repeat often enough that 5 seconds is more than enough to start getting data, but some broadcasters send them at slower rates and that might cause it to require more than 5 seconds depending on where you are in the cycle when you try to access the channel. We'd like to get a sample recording for analysis. Please save the following to a file, then upload to a file storage site like Dropbox, Google Drive, OneDrive, or iCloud, use the Get link function to generate a link, and send us that link.
There was a new release of the HDHomeRun firmware that addresses ASTC 3 problems with some channels. I have it installed and have no problems.
1 Like
Latest firmware is Feb 3rd 2022.
"FirmwareName":"hdhomerun5_atsc3","FirmwareVersion":"20220822","DeviceID":"1080ACCC"
Yah, there always behind on their forum and website.
No changelog yet Re: Changelog - Page 6 - Silicondust
Nothing about firmware Download - 20220822 - Silicondust
You must have seen the update showing on your HDHR tuner web interface.
If there was an update to 822 they have pulled it or are rolling it out in waves. I don’t have an update available on my kickstarter hdhr4k
I always use the Windows Setup release to update the others are always behind.
Did you have a ticket open or complaints with SD regarding ATSC3? How do you know that ATSC3 problems were addressed with some channels? I have 2 HDHR5-4K and neither is prompting for an update.