[mythtv-users] Error: offset>181

John Pilkington J.Pilk at tesco.net
Fri Aug 1 22:39:35 UTC 2014


On 01/08/14 17:03, John Pilkington wrote:
> On 31/07/14 16:09, John Pilkington wrote:
>> On 31/07/14 14:08, Peter Bienstman wrote:
>>>> I'm not sure about this, but I think it's a 'rescan your transports'
>>>> indication.
>>>
>>> Even if after running Kaffeine I'm able to tune through all my channels
>>> again in mythtv?
>>>
>>> Peter
>>>
>>
>> Perhaps not; that sounds as if it's not a DB tables issue.
>> 'mythbackend -v channel' or 'mythbackend -v dvbcam'  ?
>> I'm not sure what to expect, though.
>
> And a comment that I should have made earlier:  it's not clear that the
> two symptoms you report have the same cause.  I have just found my
> system reporting 'offset>181' (with no other obvious problems), and I
> 'rescanned all transports', which is a five-minute job.  Generation of
> that error message is schedule dependent and 'unreliable', so I don't
> know yet if it has been cured.I rarely get failure to lock.

For the record:  it's still being reported after the rescan, at 
irregular intervals of a few seconds in bursts lasting a few minutes, 
and causing no obvious problems.  Probably malformed EIT data for an 
unwatched channel.  Sorry for the noise.

>> John




More information about the mythtv-users mailing list