[mythtv] [mythtv-commits] Ticket #743: Fix "program not found in PAT" problem.

[Stuart Auchterlonie]

On Sun, Jan 29, 2006 at 05:19:39PM -0000, MythTV wrote:
> #743: Fix "program not found in PAT" problem.
> ---------------------+------------------------------------------------------
>  Reporter:  stuarta  |        Owner:  danielk 
>      Type:  patch    |       Status:  reopened
>  Priority:  minor    |    Milestone:  0.20    
> Component:  mythtv   |      Version:  head    
>  Severity:  medium   |   Resolution:          
> ---------------------+------------------------------------------------------
> Comment (by oa at iki.fi):
> 
>  Okay, with this patch I've got the message twice in three hours, five
>  minutes apart. The spam is over :)
> 
>  Regarding the message itself - if I interpret it correctly, the program #
>  is referring to a serviceid in a multiplex. The errors I'm seeing are
>  referring to two channels (401 and 353) that do not exist in the broadcast
>  signal on a regular basis. In both cases the PAT dump lists the other
>  channels on the same multiplex, so Myth has tuned to the right multiplex.
>  However, I *never* access the channels in question, so it's a bit
>  surprising that the error messages refer to them, especially using the
>  phrase "desired program not found in PAT".

You might not access them, but the EIT scanner probably does
on your behalf. Set useonairguide=0 for these channels.

This is assuming you use dvb-eit.

> 
>  If I may suggest an improvement, right now there are three "lines" of
>  message: one with the generic "rescan" message, one with the PAT dump, and
>  one with the program ID referred to as "desired". It would be very helpful
>  to a user if these messages were merged to one stating something like:
>  "Program #401 (channel name) not found in PAT on multiplex xx where it
>  used to exist. Multiplex contents may have changed, please rescan your
>  transports.", and this was available through the frontend system
>  information log entries instead of just in the log file.
> 

That would be nice, but currently the area that keeps track of this
is rather low level and has no concept of channels as such.

At some stage a better framework for reporting errors in a sensible
way to our users may come into being, and then we'll work out a way
of integrating this.


Stuart