[mythtv] Channel scanning/validation in trunk (feedback post r14355)

Daniel Kristjansson danielk at cuymedia.net
Fri Aug 31 14:10:56 UTC 2007

On Fri, 2007-08-31 at 08:58 -0500, Willy Boyd wrote:
> On 8/30/07, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> > Anyway, I'm not looking for feedback on the channel scanner anymore
> > than usual. At the moment I'm more interested in whether the channel
> > validation prevents channels from being added to the a Video Source
> > when they should be added, or adds channels when it shouldn't be
> > adding them. If someone is using esoteric recorders like DBOX2 or
> > IPTV, or using a diverse collection of recorder types, feedback is
> > especially appreciated.

> Would this improvement also apply to a HDHomeRun and QAM channels?

Again I'm not asking for any special testing of the scanner. In trunk
the HDHomeRun scanner is much smarter about detecting encrypted channels
than it used to be, but there is a bug where the wrong tuning
information is sometimes used, usually from the transport immediately
before or after the correct one in the scan. I think Jarod might have
backported the fix that let MythTV detect transports which looked
encrypted on first glance, but upon further inspection revealed that
the A/V streams were not actually encrypted. I remember feeling really
nervous when I noticed commits along that line in 0.20-fixes, but as I
said before the 0.20.2 & 0.20-fixes channel scanner is the best yet
in any MythTV release.

> I've recently updated to trunk just after the 0.20.2 tagging, so I'd
> be willing to go through it all again if that helps (and if it means I
> might end up with a cleaned out channel list finally). Maybe taking a
> backup of my channel table would be smart first, just in case.  I'm
> fairly comfortable with SQL.  I do not want reinsert most of those
> xmltvid's again if I can avoid it.

If you do the default scan with "Existing channel treatment" set to
"Minimal Updates" it should not erase xmltvid's for existing channels.
However, there is an out standing ticket on this happening with the
scanner in trunk, but I believe this bug only effects DVB scans not
ATSC scans.

-- Daniel

More information about the mythtv-dev mailing list