[mythtv-users] scheduler confusion

[Mike Holden]

blind Pete wrote:
> On Fri, 8 Aug 2014 21:32:05 +0930
> Mark Perkins <perkins1724 at hotmail.com> wrote:
>
>> > On 7 Aug 2014, at 6:02 pm, "blind Pete" <0123peter at gmail.com>
>> wrote:
> [snip]
>> bP, what do you have for your base tuner priorities, ie what is
>> the
>> output of (MySQL):
>>
>> select cardinputid, cardid, schedorder, livetvorder from
>> cardinput;
>
>
> mysql> select cardinputid, cardid, schedorder, livetvorder from
> mysql> cardinput;
> +-------------+--------+------------+-------------+
> | cardinputid | cardid | schedorder | livetvorder |
> +-------------+--------+------------+-------------+
> |           1 |      1 |          1 |           1 |
> |           6 |      6 |          6 |           6 |
> |           2 |      2 |          1 |           1 |
> |           3 |      3 |          1 |           1 |
> |           4 |      4 |          1 |           1 |
> |           5 |      5 |          1 |           1 |
> |           7 |      7 |          6 |           6 |
> |           8 |      8 |          6 |           6 |
> |           9 |      9 |          6 |           6 |
> |          10 |     10 |          6 |           6 |
> |          11 |     11 |         11 |          11 |
> |          12 |     12 |         11 |          11 |
> |          13 |     13 |         11 |          11 |
> |          14 |     14 |         11 |          11 |
> |          15 |     15 |         11 |          11 |
> +-------------+--------+------------+-------------+
> 15 rows in set (0.00 sec)
>
> mysql>
>
> Six stands out like a sore thumb.
>
> Presumably that would be due to seeing the second tuner on the dual
> tuner card before the first was configured to have five virtual
> tuners.  Can that be fixed without reinstalling?  Re-installing
> might
> just reproduce the problem.  B-(
>
> It has been suggested elsewhere that mythtv has no concept of
> virtual
> tuners belonging to a physical tuner.

6 doesn't stand out at all! It's just that the SQL query specified
has output the records in a random order due to a lack of an "ORDER
BY" clause.

If you try the following query, you will see it looks as expected:

select cardinputid, cardid, schedorder, livetvorder from cardinput
ORDER BY cardinput;

You would normally expect to see the schedorder and livetvorder to
go in opposite directions, rather than being identical as in this
case, but unless you are using Live TV, this shouldn't impact what
is happening.
-- 
Mike Holden