peloy at chapus
Jul 4, 2009, 3:14 PM
Post #6 of 18
(2935 views)
Permalink
|
On Sun, Jul 05, 2009 at 01:37:41AM +1000, Jean-Yves Avenard wrote:
> 2009/7/5 Eloy Paris <peloy [at] chapus>:
> > I am having a similar problem. It doesn't happen always and I am not
> > 100% what causes it. Suspending the frontend and resuming it seems to
> > be one of the triggers. I see this is on a frontend-only machine so I
> > doesn't seem to be a problem with the backend.
>
> it's the backend that is getting a channel lock problem, not the
> frontend. The frontend is just passining on the information
That's the thing: as far as I can tell there is no channel lock problem
-- by the time I get the "You should have gotten a channel lock by now"
message, the frontend is already happily showing a LiveTV recording for
the selected channel and pressing "ok" in that dialog will keep LiveTV
going.
Another data point is that non-LiveTV recordings work just fine.
Also, once I start to get the "You should have gotten a channel lock
by now" message everytime I change a channel while watching LiveTV, I
can make the problem go away by restarting the frontend. I don't have
to touch the backend at all to make the problem go away. Of course, the
problem eventually comes back (I've noticed that a trigger is resuming
from S3 sleep.)
> Usually it's due to a poor antenna signal, but as it works with other
> media player, it's puzzling
Everything else works fine; if it were poor antenna signal I'd expect to
see pixelation or something wrong with the image, but no, it's perfect
at all times. No question it's puzzling, though.
> the backend must show something in its log.. he'll need to post that
I actually should increase verbosity of the backend log messages since
that's something I haven't done yet.
Cheers,
Eloy Paris.-
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
|
