So it makes more sense to have zero days than three days (or two, or even 24 hours)? Do I have that right? Can you explain that argument to me?...
A two-day guide would work well for non-DVR receivers, since that is as far out as the Dish-delivered guide data goes anyway. So, it would be seamless to the user, who would not care what the source of the guide data was. When you get to DVR receivers with extended guides though (by the way, which model(s) have a two-week guide, since my Dish guide only goes out
one week?) then Dish would likely get a lot of complaints about those channels with PSIP data, since the guide would not go out all the way. Since this is a problem that Dish could do absolutely
nothing to solve (but they would get the complaint calls anyway) they probably feel that it is better not to provide the guide data in the first place. At least that way, it is consistent: either full guide data, or no guide data, for each channel.
It's been a long time since I took a computer programming class, but a simple IF/ELSE statement should suffice...
IF there is Dish guide data, use that.
ELSE use PSIP. ...
That still would not solve the problem where Dish is mapping the
wrong guide data to certain OTA channels though. Perhaps if it were a user-selectable choice which guide data source to use, and if you could switch back and forth between them, then that might be a workable solution. Of course, they would have to somehow make sure that timers set while using one set of guide data would continue to record, even after the user chooses to display the other set of guide data. This is assuming the guide data source choice would apply to all OTA channels. If the user could manually customize which guide data source to use for each individual channel, then that would be even better.
I still like my suggestion of an app, though. This way, all available OTA channels could be listed in the app's guide, even if you have not scanned them in. So, if a new subchannel appears in the app, and you cannot actually tune to it, then that would alert you that you need to re-scan your OTA channels. If an entire station (not just an individual subchannel) appears in the app's guide, that you cannot receive, then that would let you know that you need to do one of the following in order to receive it:
- Re-scan your OTA channels
- Re-aim your antenna, and/or raise it higher to get better reception
- Get a better antenna
- Add a second antenna aimed toward that station
Even better, this would provide full guide data, and allow you to set timers (for the channels that you actually have scanned in) directly from the app.
...
I'm willing to wager there are MANY more diginet channels than those Dish carries. I'm pretty sure Dish only carries one subchannel in my market. I think there are over a dozen available OTA.
I think dweber meant mapping down the guide data from the
national feeds that Dish carries, to appear in the guide on the local subchannels. Even if there are slight variations on the local affiliates, where they do not carry that network's full schedule (for instance, to insert some locally-produced program once per week)
any guide data would be better than none, as I am sure you would agree.
