[mythtv-users] explain defaultinput field in capturecard table in mythconverg

[Michael T. Dean]

On 05/12/2014 06:26 PM, Eyal Lebedinsky wrote:
>
> On 05/13/14 01:17, Michael T. Dean wrote:
>> On 05/12/2014 01:24 AM, Eyal Lebedinsky wrote:
>>> My first query is: what is the exact semantics of this field? I 
>>> notice that in the past
>>> it defaulted to DVBInput but it now defaults to Television, so I 
>>> have a mix of both.
>>
>> When you configure a capture device with a single input, MythTV will 
>> always set the default input properly.  However, since kernel drivers 
>> have changed over time--in some (many) case(s) changing the input 
>> identifiers--this tends to happen when you add cards at different 
>> times (though it can happen when adding all cards at the same time if 
>> you misconfigure the cards--even if you think you undid the 
>> misconfiguration and reconfigured correctly).
>>
>> The best way to fix the problem is to use the "Delete all capture 
>> cards" (not "Delete all capture cards on <hostname>") portion of 
>> http://www.gossamer-threads.com/lists/mythtv/users/264034#264034 . 
>> Doing so will have no impact on your Channels or Video Sources (just 
>> don't do the "Delete all video sources" portion), and takes only 
>> seconds.  (I can delete all my capture cards and reconfigure the six 
>> of them--spread across 2 backend systems--in about 30 seconds.)
>>
>> This is also why it's recommended that any time you do a major system 
>> upgrade (i.e. distro upgrade or kernel upgrade) you should repeat the 
>> "Delete all capture cards" procedure.
>>
>> You'll also need to do as Stephen suggested to ensure consistent 
>> device numbering
>>
>> Mike
>
> So where does one set/change this field? I did not find it in the 
> "capture cards" setup dialogue.

Since--as Bill mentioned--the field is not used, anymore, there's 
absolutely no reason to set it (or even worry about it).

>
> The "input connections" setup lists all cards with DVBInput, never 
> Television. Should capturecard.defaultinput
> reflect the same?
>
> There surely is some confusion in the system that requires cleanup, 
> even if, as others said here, this
> field is not used (never or just for digital tuners?).

And what makes you think it requires cleanup?  If you're seeing a 
problem, you should explain what problem that is, then we can help you 
find its true cause.  The database value of an unused field is not 
causing you any problems.

Mike