[mythtv] Re: Ticket #430: Tuner busy on consecutive recordings

[Mark Kundinger]

I was also experiencing the tuner busy problem yesterday.  And making
the eventsleep change suggested did nothing.

For what it's worth, testing 7416 (which includes the change Daniel
made in 7410), I was able to tape 5 back-to-back shows on one tuner
(MPEG) and 3 back-to-back on the other (MJPEG).

This apparently diverges from JR's experience with 7410, and I cannot
offer any explanation for that.



--- Daniel Kristjansson <danielk at cuymedia.net> wrote:

> On Sat, 2005-10-08 at 09:23 +0000, MythTV wrote:
> > #430: Tuner busy on consecutive recordings
> > Using r7410 it still misses every consecutive recording I throw at
> > it. I recently enabled 90 global seconds of under and over
> recording
> > just to see if it made a difference, but it didn't. It seems to not
> > do consecutive recordings whether there is any global under and
> over
> > recording time or not.
> 
> I think the WaitForEventThreadSleep() changes are a Red Herring.
> Perhaps the inoverrecord state simply hasn't been entered when
> StartRecording is called, but will be entered a few seconds in
> the future.
> 
> Could you try adding this before "if (inoverrecord)"
> 
>     VERBOSE(VB_IMPORTANT, "inover("<<inoverrecord<<
>         ") time-till end("<<
>         QDateTime::currentDateTime().secsTo(curRecording->recendts));
> 
> It might tell us something....
> 
> I'm thinking perhaps this is a race with the event loop for
> setting the inoverrecord variable. When it ran every 1/1000th
> of a second it usually won, but now that we run it once a
> second it often looses.
> 
> -- Daniel
> 
> 
> > _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>