[mythtv-commits] Ticket #2231: Automatically move nextRecording to other tuner if scheduled tuner is busy for showing LiveTV

MythTV mythtv at cvs.mythtv.org
Thu Aug 24 02:29:24 UTC 2006


#2231: Automatically move nextRecording to other tuner if scheduled tuner is busy
for showing LiveTV
----------------------------------+-----------------------------------------
 Reporter:  mythtv at linux-dude.de  |        Owner:  ijr    
     Type:  enhancement           |       Status:  new    
 Priority:  minor                 |    Milestone:  unknown
Component:  mythtv                |      Version:  head   
 Severity:  medium                |   Resolution:         
----------------------------------+-----------------------------------------
Comment (by derek at battams.ca):

 Instead of using the recording priority to decide if the recording should
 be automatically moved to another tuner why not check the priorities of
 the other tuners?  Something like:

 {{{
 if(liveTV conflict)
 {
    tuners = list of available (and free) tuners w/ priority >= tuner being
 watched
    foreach(tuner as t)
    {
       if(t has program to be recorded)
       {
          change tuner for recording
          return;
       }
    }
 }
 // If we got here then the recording couldn't be moved
 continue on to user popup, etc.
 }}}

 My other idea was to use the recordmatch table to find other instances,
 but a quick look at recordmatch suggests there isn't quite enough data in
 that table to be able to use it (at least not without doing more work
 before making a decision).

 I've been wanting to look into this for some time now.  Seeing this ticket
 was the motivation I needed.  I guess I'll start by modifying the patch
 here with my algo above (hopefully my pseudo code makes sense).  Just out
 of curiosity, shouldn't the scheduler be run again if the switch is made
 since a recording could be scheduled to start during the running time of
 the recording moved?  And then another interesting point - if a recording
 is moved, does the scheduler detect that and act accordingly.  Were any of
 these scenarios tested with the patch here?

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/2231#comment:2>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list