[mythtv] Ticket #11399: EIT scanner causes unnecessary reschedules and prevents idle shutdown

[Roger James]

The schedule table ids are used in ascending order for events that are further into the future. So as far as I know if  you look at the bottom nibble of the schedule tableid an event should first appear in 0x0f  or whatever the  last_table_id field in the header is set to, and then migrate down into lower numbers over time. Currently my patch does not handle the  change of version id when an event migrates into a lower tableid very well.

Roger

MythTV <noreply at mythtv.org> wrote:

>#11399: EIT scanner causes unnecessary reschedules and prevents idle shutdown
>-----------------------------------+----------------------------
> Reporter:  Roger James <roger@…>  |          Owner:  stuarta
>     Type:  Patch - Bug Fix        |         Status:  new
> Priority:  minor                  |      Milestone:  0.26.1
>Component:  MythTV - EIT           |        Version:  0.26-fixes
> Severity:  medium                 |     Resolution:
> Keywords:  eit idle               |  Ticket locked:  0
>-----------------------------------+----------------------------
>
>Comment (by dekarl@…):
>
> looking at your patch I noticed that you use literal values instead of the
> enum
> {{{
> class MTV_PUBLIC TableID
> {
>   enum
>   {
>     PF_EIT = 0x4e, // always on pid 0x12
>     PF_EITo = 0x4f, // always on pid 0x12
>     SC_EITbeg = 0x50, // always on pid 0x12
>     SC_EITend = 0x5f, // always on pid 0x12
>     SC_EITbego = 0x60, // always on pid 0x12
>     SC_EITendo = 0x6f, // always on pid 0x12
>   }
> }
> }}}
> I have to look up the other points in the standards as most are new for
> me. (e.g. how the programmes get distributed into the different
> "TableIDs")
>
>-- 
>Ticket URL: <http://code.mythtv.org/trac/ticket/11399#comment:1>
>MythTV <http://code.mythtv.org/trac>
>MythTV Media Center