[mythtv-users] HDHR working but channel mapping is incorrect

f-myth-users at media.mit.edu f-myth-users at media.mit.edu
Thu Apr 16 02:36:00 UTC 2009

    > Date: Wed, 15 Apr 2009 10:47:06 +0100
    > From: Mike Perkins <mikep at randomtraveller.org.uk>

    > be in a consistent format for SD to use. Got to be a winner, although as someone 
    > pointed out, would involve dev time.

Doesn't necessarily have to be dev time, since at least a prototype
doesn't even have to be hosted at SD.  Someone who wanted to try this
could whip up a patch that used some server of theirs & collected the
data, and presumably such a patch might be committed by the devs
without any guarantees of performance (since they're not running
the server).  Once it's proven itself, the code could be moved to
SD and the patch revised to use that server instead (or it could
just use a domain name that itself gets its A record changed, etc).

Since this is just a list of available channels vs some region,
the privacy issues seems approachable, even if it's on a third-party
server.  One wrinkle might be that (according to other traffic in this
thread) some of the regions with constant lineups could be quite
small, so street addresses or ZIP+4 locations or something with that
granularity might be necessary, which might itself require trying to
be careful with that data so it doesn't leak or get compromised at the

The hardest part of the design is probably having some way of making
sure that good data doesn't get polluted by bad outlyers, while still
allowing it to actually get -changed- when the lineup actually
changes.  (Hence, you can neither just believe every update, nor
can you do majority-vote or a lineup change will never hit critical
mass to flip the vote.)  But all of this sort of thing can be
discussed and designed under the covers, perhaps even off-list,
without necessarily consuming Myth devo time.

More information about the mythtv-users mailing list