[mythtv] DVB scanning broken in SVN 10056

[Justin Hornsby]

Hi.

I've been testing SVN for a while on a spare box, and I've encountered a 
problem with scanning.

When I scan, all of the channels I'm supposed to get (UK Freeview) are 
present & correct.

However it seems that the frequency information is being stored 
incorrectly.  A mux with a frequency of 754166670 is being stored as 
753999990 and so on.

I could  very well just grab the dtv_multiplex & channel tables from my 
working system, but that wouldn't be much use in terms of getting the 
problem fixed would it? ;-)

A dump of my dtv_multiplex table from the SVN build is here:

+---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+---------------------+
| mplexid | sourceid | transportid | networkid | frequency | inversion | 
symbolrate | fec  | polarity | modulation | bandwidth | lp_code_rate | 
transmission_mode | guard_interval | visible | constellation | hierarchy 
| hp_code_rate | sistandard | serviceversion | updatetimestamp     |
+---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+---------------------+
|      6 |        1 |       24576 |      9018 | 810166680 | a         | 
       NULL | NULL | NULL     | NULL       | 8         | 3/4          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |              8 | 2006-05-29 16:42:13 |
|      5 |        1 |       20480 |      9018 | 786166680 | a         | 
       NULL | NULL | NULL     | NULL       | 8         | 3/4          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |              8 | 2006-05-29 16:42:02 |
|      4 |        1 |       16384 |      9018 | 841999990 | a         | 
       NULL | NULL | NULL     | NULL       | 8         | 3/4          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |              8 | 2006-05-29 16:42:30 |
|     3 |        1 |       12290 |      9018 | 850000010 | 0         | 
      NULL | NULL | NULL     | qpsk       | 8         | 1/2          | 2 
                 | 1/32           |       0 | qam_64        | n 
| 2/3          | dvb        |              3 | 2006-05-29 16:42:30 |
|      2 |        1 |        4104 |      9018 | 753999990 | a         | 
       NULL | NULL | NULL     | NULL       | 8         | 3/4          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |              8 | 2006-05-29 16:41:56 |
|      1 |        1 |        8203 |      9018 | 834166680 | a         | 
       NULL | NULL | NULL     | NULL       | 8         | 1/2          | 
2                 | 1/32           |       0 | qam_64        | n 
  | 2/3          | dvb        |              5 | 2006-05-29 16:42:23 |
+---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+---------------------+


.. and here is a dump of the same table from my working system:


+---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+-----------------+
| mplexid | sourceid | transportid | networkid | frequency | inversion | 
symbolrate | fec  | polarity | modulation | bandwidth | lp_code_rate | 
transmission_mode | guard_interval | visible | constellation | hierarchy 
| hp_code_rate | sistandard | serviceversion | updatetimestamp |
+---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+-----------------+
|       1 |        1 |        4104 |      9018 | 754166670 | a         | 
          0 | auto |          | auto       | 8         | 2/3          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |              8 |  20051107014037 |
|       2 |        1 |        8203 |      9018 | 834166670 | a         | 
          0 | auto |          | auto       | 8         | 1/2          | 
2                 | 1/32           |       0 | qam_64        | n 
  | 2/3          | dvb        |              8 |  20051107014051 |
|       3 |        1 |       12290 |      9018 | 850166670 | a         | 
          0 | auto |          | auto       | 8         | 1/2          | 
2                 | 1/32           |       0 | qam_64        | n 
  | 2/3          | dvb        |             25 |  20051107014106 |
|       4 |        1 |       16384 |      9018 | 842166670 | a         | 
          0 | auto |          | auto       | 8         | 2/3          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |             16 |  20051107014128 |
|       5 |        1 |       20480 |      9018 | 786166670 | a         | 
          0 | auto |          | auto       | 8         | 2/3          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |              2 |  20051107014149 |
|       6 |        1 |       24576 |      9018 | 810166670 | a         | 
          0 | auto |          | auto       | 8         | 2/3          | 
2                 | 1/32           |       0 | qam_16        | n 
  | 3/4          | dvb        |              1 |  20050720004101 |
+---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+-----------------+

Is this expected behaviour?  I can't get livetv or recordings to work, 
so I'm guessing that the incorrect frequency data is causing the problems.

Regards,
Justin