<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16441" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=124383321-30052007><FONT face=Arial
color=#0000ff size=2>I'm working on a bash script to merge XMLTV data
(downloaded from mythfilldatabase) with channel data (from myth scans) - since I
had a somewhat similar problem of data not matching up.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=124383321-30052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=124383321-30052007><FONT face=Arial
color=#0000ff size=2>If you want to give it a try just email
me.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=124383321-30052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=124383321-30052007><FONT face=Arial
color=#0000ff size=2>-MD-</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mythtv-users-bounces@mythtv.org
[mailto:mythtv-users-bounces@mythtv.org] <B>On Behalf Of </B>Michael
Thome<BR><B>Sent:</B> Wednesday, May 30, 2007 4:59 PM<BR><B>To:</B> Discussion
about mythtv<BR><B>Subject:</B> Re: [mythtv-users] How does myth use info in
channel table to tune QAM channels?<BR></FONT><BR></DIV>
<DIV></DIV>Brian Walter wrote:
<BLOCKQUOTE cite=mid:465DA75A.4090200@gmail.com type="cite"><PRE wrap="">Michael Thome wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">Which database fields does myth use to tune QAM channels? How do these
rules interact with zap2it lineups?
Example: here is an extract of what the channel table looks like after a
successful scan:
mysql> SELECT
chanid,channum,freqid,callsign,xmltvid,tvformat,mplexid,serviceid,atsc_major_chan,atsc_minor_chan
FROM `channel` WHERE `sourceid` = '5';
| chanid | channum | freqid | callsign | xmltvid | tvformat |
mplexid | serviceid | atsc_major_chan | atsc_minor_chan |
| 5740 | 74#0 | 74 | UNKNOWN74#0 | | Default |
120 | 65 | 0 | 0 |
for 5740, by watching the stream I can see it is WENH (xmlid 11418). I
assume I can add the xmltvid and scheduling will work, but I'd also like
to fix the channum for the on-screen schedule (74#0 isn't mnemonic) -
can I change channum to "11"? callsign to "WENH"? What is mplexid? Why
is tvformat entered as "Default" and not "ATSC"? Shouldn't it be ATSC
with atsc_major/minor_chan set to something useful? As an aside, how'd
we get from 74.65 (what an hdhomerun_config scan reports) to 74#0?
</PRE></BLOCKQUOTE><PRE wrap=""><!---->
Looks like your in New England too :)
I have the same cable setup (comcast - Southern NH). After scanning, I
changed two fields (via mythweb) - the xmltvid and the frequency - in
the sample you have above I believe BZ is 804 (from zap2it). Use the
'channel number' from zap2it for the freqid in the table.
After that, everything worked great.
Depending on the rest of your tuner options (I have a pvr500 for
standard cable) the 74#0 type of channels are digital broadcast of
analog (no hd stuff). I found them to be 'noisy' and not very reliable
and ended up deleting them.</PRE></BLOCKQUOTE>Yep - north-shore MA.<BR>I trimmed
out WBZ from above as it is pretty much ok as scanned... WENH,
though:<BR>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...<BR><BR>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.<BR><BR>Hmmm -
maybe I'll see what happens when I bash HSN...<BR></BODY></HTML>