'Re: [mythtv-users] How does myth use info in channel table to tune'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: mythtv-users
Subject: Re: [mythtv-users] How does myth use info in channel table to tune
From: Michael Thome <mthome () bbn ! com>
Date: 2007-05-31 13:14:45
Message-ID: 465ECA45.8040907 () bbn ! com
[Download RAW message or body]

[Attachment #2 (text/html)]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Michael Thome wrote:
<blockquote cite="mid:465DE58F.7060808@bbn.com" type="cite">
 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
 <title></title>
... 
I trimmed out WBZ from above as it is pretty much ok as scanned...&nbsp;
WENH, though: 
I looked at the code, and I cannot see anything in the *tuning* area
that should care at all about the various fields - what is critical is
mplexid which gives us real frequency and (qam256) modulation via the
dtv_multiplex table, and then the serviceid, which tells us which
stream - it looks to me like everything else is ignored for tuning
purposes... 
 
But, that just begs the question - I wonder if the grabber doesn't use
the same rules and messes with the channels when the channum is some
other (known) non-hd type. 
</blockquote>
Update - doing the channel mods through mythweb and mysql doesn't
exhibit the broken channel problems I've seen before - The next
possibility is the live-tv channel editor probe function... though at
first glance I don't see anything wrong there, either. 
 
Ah well - haven't broken it again so far... 
 
</body>
</html>

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

[prev in list] [next in list] [prev in thread] [next in thread] 