Terry, Thanks for the response / ideas.
Originally Posted by TPeterson
Are you using the 18.104.22.168 driver update?
I'm not using the driver for the CW_EPG, since I don't use the EPG. I think it's the latest standard release. I think the log has the compile date, but I'm not sure how that relates to the version number. If more is required, I can be more precise.
In any case, the log clearly shows that MyHD is having some sort of reception problem with that station and based on my own experience I'd suspect multipath as the culprit. Does it come from a very different direction than your other stations?
True, it's not a stellar station, but for a long time there was complete bewilderment over why zero byte files were happening. As I recall, we uncovered some obvious reasons (not enough disk, station not broadcasting), but those never explained all of the zeros.
The station from one example comes from the main group of towers. The station from another example is off by itself. But the kicker is that when I watch either of those stations, it's perfect to the eye, despite quite a bit of chatter sometimes in the log. That makes me think that the idea that station was completely whacked through the entire 1/2 hour is not very likely. I think MyHD gets it's panties in a wad if there's no lock at that critical time. The recovery when you're sitting there is just to stop and restart the app. But if you're not there, it's a ZBF. It happens very infrequetly, so it's not really a big deal to me, but I thought if MIT got this clue, it might not be a difficult one to nail.