[mythtv-users] MythTV 0.25 tuner inititialisation problem

[mythtv .]

Ok so a bit more on this story. It seems that if I reboot the system then
immediately (or relatively immediately ie after a few mins, maybe more I
haven't timed it) go to liveTV (or a scheduled recording kicks off) then it
fails and I get partial lock on each tuner the first time they are
accessed. Subsequent accesses are fine.

On the other hand yesterday (and I noticed this recently once more but
didnt realise what had happened), I rebooted the system and then forgot to
do what I was doing (ie accessing each tuner one by one to get past the
partial lock issue - this had become my norm after a reboot - not that I
reboot very often). Anyway a few hours later I went to cycle through the
tuners to get them out of their partial lock state and they were all fine???

I have never noticed this before I must admit but it could have been
inherent behaviour all along. Does MythTV need a certain amount of time to
initialise the tuners???? Am I just rushing things here, or is it that it
is accessing the tuners in the background for ecample to get the EIT data
and simply doing in effect what I was doing? ie has this problem been user
error is it some form of system error?

Cheers

Martin


On 4 February 2013 08:09, mythtv . <mythtv at harley-jones.co.uk> wrote:

> I have been running MythTV 0.24 on Mythbuntu 11.04 using two twin tuner
> Hauppauge DVB-T NOva-TD USB sticks with no problems for several years.
>
> I recently updated to Mythbuntu 12.04LTS and MythTV0.25 and now have the
> following problem:
>
> On rebooting (or restarting mythbackend having configured mythbackend)
> recordings/live TV will fail the first time.
>
> The easiest way to see this is to reboot and then go into Live TV. Myth
> will get a Partial Lock and then flag the error that a lock should have
> been received. Exiting LiveTV and then going back to viewing and it works
> fine. This procedure has to be done for each Tuner (1 thro 4 - 2 twin tuner
> sticks). But once done on say tuner 1 my second virtual tuner on tuner 1
> will be fine so probably an intitialisation issue? After doing this it
> works flawlessly until the next restart of mythbackend/reboot and the
> procedure must be done again.
>
> I have tried deleting all tuners etc in the backend setup and
> re-configuring but still the same.
>
> Any ideas? Is this a known problem? Would moving up yet again to 0.26
> solve this?
>
> Cheers
>
> Martin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130228/b7131c98/attachment.html>