I can't comment about his particular tuner, but in my case yes. It goes like this:NedS wrote: ↑Mon Apr 01, 2019 10:24 pmAnd these are channels that were previously discovered and hidden, but became unhidden?dinki wrote: ↑Mon Apr 01, 2019 12:14 pm@neds Please do hurry. I just had more channels found. One tuner detected three new channels and the other tuner found three different new channels than the first. Annoying to say the least.
I'll continue to post when this happens to illustrate how the ability to turn off auto discovery really is necessary and not just a petty request.
- Channel scan
- Disable undesired channels
- During one of the Prime's background scans (usually about a month later) the channel is present again, and active
I know this is mostly a cosmetic issue, as the channels that are "removed" from the lineup can be manually tuned. However, for applications that use the "new" HTTP API and the tuner's lineup (rather than maintaining their own), this means that channels that should be viewable and now marked as unavailable. (Well, worse than "unavailable" as they are not even present.) This doesn't cause too much grief because I have multiple tuners, so missing channels can be tuned on one of the other tuners, giving me time to do a hard reset on the misbehaving TA and force a complete rescan on the tuner with missing channels. But for a user with only a single tuner, I can see how this would become quite problematic.
(It should also be noted: this has been an issue ever since background scans were introduced. I know I first mentioned it as a problem over a year ago, but I was told nothing was wrong. This has only become more of an issue for me personally as my DVR software is now using the tuners' lineups, rather than maintaining its own lineup and guide mapping.)