[mythtv] *buntu trusty ppa: loss of multirec

[John Pilkington]

On 27/01/16 17:14, Stuart Auchterlonie wrote:
> On 27/01/16 15:18, John Pilkington wrote:
>> On 27/01/16 14:59, John Pilkington wrote:
>>> On 27/01/16 14:50, John Pilkington wrote:
>>>> On 27/01/16 14:14, Stuart Auchterlonie wrote:
>>>
>>>>>
>>>>> Time for the silly questions. did you go into the recording options and
>>>>> set multirec to > 1 ??
>>>>>
>>>>> Regards
>>>>> Stuart
>>>>
>>>> Yes.  2 default, I use 5, but now no effect.
>>>>
>>>> mysql> select cardid, parentid, videodevice, schedorder, livetvorder
>>>> from capturecard ;
>>>> +--------+----------+-----------------------------+------------+-------------+
>>>>
>>>>
>>>>
>>>> | cardid | parentid | videodevice                 | schedorder |
>>>> livetvorder |
>>>> +--------+----------+-----------------------------+------------+-------------+
>>>>
>>>>
>>>>
>>>> |      1 |        0 | /dev/dvb/adapter0/frontend0 |          1 |    5 |
>>>> |      2 |        1 | /dev/dvb/adapter0/frontend0 |          0 |    0 |
>>>> +--------+----------+-----------------------------+------------+-------------+
>>>>
>>>>
>>>>
>>>> 2 rows in set (0.00 sec)
>>>>
>>>> Cheers,
>>>>
>>>> John
>>>
>>> That was as I had left it.  Just rentered setup and set max recordings
>>> to 5.
>>>
>>> mysql> select cardid, parentid, videodevice, schedorder, livetvorder
>>> from capturecard ;
>>> +--------+----------+-----------------------------+------------+-------------+
>>>
>>>
>>> | cardid | parentid | videodevice                 | schedorder |
>>> livetvorder |
>>> +--------+----------+-----------------------------+------------+-------------+
>>>
>>>
>>> |      1 |        0 | /dev/dvb/adapter0/frontend0 |          1 |    5 |
>>> |      2 |        1 | /dev/dvb/adapter0/frontend0 |          0 |    0 |
>>> |      3 |        1 | /dev/dvb/adapter0/frontend0 |          0 |    0 |
>>> |      4 |        1 | /dev/dvb/adapter0/frontend0 |          0 |    0 |
>>> |      5 |        1 | /dev/dvb/adapter0/frontend0 |          0 |    0 |
>>> +--------+----------+-----------------------------+------------+-------------+
>>>
>>>
>>> 5 rows in set (0.00 sec)
>>>
>>
>> For this particular setup (after comparison with another box)
>>
>> "update capturecard set schedorder=1, livetvorder=5 ;"
>>
>> re-allows the scheduling.
>>
>> select cardid, parentid, videodevice, schedorder, livetvorder from
>> capturecard ;
>> +--------+----------+-----------------------------+------------+-------------+
>>
>> | cardid | parentid | videodevice                 | schedorder |
>> livetvorder |
>> +--------+----------+-----------------------------+------------+-------------+
>>
>> |      1 |        0 | /dev/dvb/adapter0/frontend0 |          1 |    5 |
>> |      2 |        1 | /dev/dvb/adapter0/frontend0 |          1 |    5 |
>> |      3 |        1 | /dev/dvb/adapter0/frontend0 |          1 |    5 |
>> |      4 |        1 | /dev/dvb/adapter0/frontend0 |          1 |    5 |
>> |      5 |        1 | /dev/dvb/adapter0/frontend0 |          1 |    5 |
>> +--------+----------+-----------------------------+------------+-------------+
>>
>> 5 rows in set (0.00 sec)
>
> Hmmm, looks like it's not applying the schedorder & livetvorder to all
> the multirec devices.
>
> Smells like a bug
>
> Regards
> Stuart

Yes, but I think it first appeared with the fix for non-autoswitching 
DVB-T2.  Before that the name of the device was shown; now it isn't, and 
full recognition is probably not happening.  But I think I've done at 
least two 'delete all capture cards' with full retunes for different 
transmitters since then.  I have the impression that one of the many 
recent changes has given an extra push.

John