[mythtv-users] Problem with program guide

[Josh White]

Mike,

I tried what you suggested and it seems to work now.  Thanks for all the
help.

On 10/10/07, Josh White <jaw1959 at gmail.com> wrote:
>
> Mike,
>
>  Sweet, it sounds like I finally found someone with a solid idea.  Thanks,
> I'll give that a try later on. So it sounds like I messed up my database by
> populating it twice.  I'll use the fetch method and see what happens.
>
> On 10/10/07, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> >
> > BTW, bottom- or inline-posting is preferred here (
> > http://www.mythtv.org/wiki/index.php/Mailing_List_etiquette ).  And
> > regardless, trimming long posts is very much appreciated.
> >
> > On 10/10/2007 10:28 AM, Josh White wrote:
> > > Thanks.  I thought the same thing, but when I tried hitting "fetch..."
> > > it didn't seem to do anything.
> >
> > That's because you had already created the channels using scan.  Scan
> > for channels is really for digital capture cards and for analog users
> > who don't have access to a great listings provider like Schedules
> > Direct.  If you have SD support, using Fetch channels from listings
> > provider is /much/ more functional.
> >
> > If you've done a scan for channels /and/ Fetch channels from listings
> > provider, chances are you have duplicate channels in your DB, which
> > will--eventually--cause problems ( i.e. missed recordings or worse).  I
> > /highly/ recommend
> > http://www.gossamer-threads.com/lists/mythtv/users/264034#264034 (only
> > the "Delete all video sources" part--don't worry about deleting capture
> > cards).  This won't harm any of your recording rules or recordings or
> > ...
> >
> > > Scan for channels seems to sequentially work its way through the
> > > channels available to the tuner.  Somehow, those channels are then
> > > linked with the listing data from Schedulesdirect.org
> > > <http://Schedulesdirect.org> (which seems to work, mostly for the
> > > specific show information) in the mysql database so I know that Modern
> > > Marvels "The Colosseum" is on at 8:00pm on Wednesday night.  So how
> > > does that part work, but adding the callsign ( i.e. "HISTORY" to
> > > channel 42, the History channel) does not?  Are these two pieces of
> > > information handled in two different places?  That seems strange to
> > > me.  I've tried looking for more information on how this works in
> > > Myth, but I haven't had much luck.  Does anyone know where I can find
> > > more information on this?  I'm not programmer, so I doubt I'd be able
> > > to read the source code, but this seems to be one of the key features
> > > of MythTV (or at least, a critical function that the rest of the key
> > > features are based on), and I would hope it would be documented
> > > someplace.
> >
> > I'm not sure I understand the question, but if you're asking how the
> > channels are linked to the listings data by mythfilldatabase, it's using
> > the xmltvid--not the callsign.  Callsign is a user-editable field that
> > provides a way of telling Myth that 2 channels are "substantially
> > identical" (i.e. if received from 2 different sources, such as a digital
> > capture card and an analog capture card).
> >
> > Also, if (North American) analog channels are populated "correctly"
> > (i.e. using SD/Fetch channels from listings provider), the xmltvid will
> > be automatically put in place.  So, cleaning up the existing and redoing
> > it as described in the post above will fix the issues.
> >
> > > So again, I can narrow it down to either a database problem, or a
> > > problem with the source data.
> >
> > Make sure you run the optimize_mythdb.pl script to check and/or fix your
> > database before you do the Delete all...
> >
> > Mike
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20071010/1795f32a/attachment-0001.htm