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

[MythTV]

#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@…):

 Just putting the parts of the spec in that I based my understanding on.

 I was referring to EN 300 468 section 5.2.4. "Event Information Table"
 where they explain the format of the "Event information section".
  version_number: This 5-bit field is the version number of the sub_table.
 The version_number shall
  be incremented by 1 when a change in the information carried within the
 sub_table occurs. When it
  reaches value 31, it wraps around to 0. ... (part about
 current_next_indicator omitted)

  section_syntax_indicator: The section_syntax_indicator is a 1-bit field
 which shall be set to "1".

 from section 3.1 "Definitions" about the sub_table
  sub_table: collection of sections with the same value of table_id and:

  for a EIT: the same table_id_extension (service_id), the same
 transport_stream_id, the same
  original_network_id and version_number

  NOTE: The table_id_extension field is equivalent to the fourth and fifth
 byte of a section when
  the section_syntax_indicator is set to a value of "1".

 and from the same section about table
  table: comprised of a number of sub_tables with the same value of
 table_id

 I did not notice the explicit mention of ONID and TSID earlier, but that
 makes sense as it avoids collisions between tables for the same service_id
 on different transports in a different original network. (e.g. service_id
 1 in the ONID 2 scope colliding with service_id 1 but a different ONID on
 the same satelite)

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/11399#comment:9>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center