[mythtv-users] Many recordings fail and then succeed a second later

[Klaas de Waal]

On Mon, 20 Jan 2020 at 12:39, Daryl McDonald <darylangela at gmail.com> wrote:

>
>
> On Mon, Jan 20, 2020 at 5:44 AM Hika van den Hoven <hikavdh at gmail.com>
> wrote:
>
>> Hoi Ross,
>>
>> There have been incidents reported where an instable network
>> connection caused problems. Both through bad nics (especially Realtec
>> Gb cards) and unstable switches. Also check if at the time of failure
>> there are heavy network loads. I myself have my homerun on a dedicated
>> nic.
>>
>> Monday, January 20, 2020, 5:25:17 AM, you wrote:
>>
>> > Since my failures occur 0.005 seconds after the initial attempt, it
>> > doesn't seem that any of the timeout parameters are having an
>> > effect.  If they were, it would wait 1 - 3 seconds (or maybe up to
>> > 6? the docs mention it's doubled in some circumstances) before
>> > failure.  It's hard to imagine that increasing them will make a
>> difference.
>>
>>
>>
>> > HDHRSH[1](10424297): DeviceSet(channel 8vsb:563000000): ERROR: lock no
>> longer held
>> >  looks to me as if it's a failure to get a lock on the HD HomeRun
>> > device, not a failure of the HDHR to get a lock on the channel.
>> > Oddly, I have been unable to find "no longer held" in the sources
>> > for myth or libhdhomerun.  It looks as if the message is coming from
>> the latter.
>>
>>
>>
>>
>>
>> Tot mails,
>>   Hika                            mailto:hikavdh at gmail.com
>>
>> "Zonder hoop kun je niet leven
>> Zonder leven is er geen hoop
>> Het eeuwige dilemma
>> Zeker als je hoop moet vernietigen om te kunnen overleven!"
>>
>> De lerende Mens
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
>
>  Are you saying that instead of 4 records in capturecard there should be 2?
>
> Yes, then in input connections, increase number of simultanious recordings
> to 2 for both.
>
> It looks to me that all your errors are related to the locking. What you
perceive as a channel scan could be the EIT in action which tries to scan
every multiplex in the video source for program guide information. This is
in your configuration enabled for the first tuner of the two tuners. Your
configuration looks correct to me.

Please check that you have a recent v30 (v30.1 or v30/fixes) and not the
original v30. In ticket #13407 there is a bug fixed related to the
HDHomeRun locking and this fix is in the latest v30/fixes and of course in
master / pre-v31 but not in the original v30.

If your HDHomeRun is on your in-house network (as opposed to a dedicated
line to your mythtv backend) then you can verify the correct operation of
HDHomeRun itself by using e.g. an Android app or a PC app. An intermitted
failure, e.g. from the power supply, could also cause the lock to be lost
but this should then also influence the behaviour with the original
HDHomeRun apps.

Klaas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20200120/2556f324/attachment.htm>