ok that makes sense... so i tried this:
#1 channel 7 is recording (card 1) something up until 2300 #2 i have scheduled something on channel 9 that starts at 2130 -> 2330 #3 i have scheduled something on channel 7 that starts at 2300 -> 0040 fine so far. #4 now i schedule something on channel 9 that starts a 2330 -> 0130 and the #3 becomes red ie conflict. i would have assumed that the scheduler would have picked card 2 for #2, then card 1 for #3 as it did, but when i add #4 it should just use card 2, instead it conflicts #3 and uses card 1. 2005-10-15 20:37:12.556 Reschedule requested for id -1. Query 0: /record.search = :NRST AND (record.recordid = :NRRECORDID OR :NRRECORDID = -1) AND program.manualid = 0 AND program.title = record.title 2005-10-15 20:37:12.569 |-- Start DB Query 0... 2005-10-15 20:37:12.573 |-- -1 results in 0.001252 sec. 2005-10-15 20:37:12.578 +-- Done. 2005-10-15 20:37:12.581 PruneOldRecords... 2005-10-15 20:37:12.584 AddNewRecords... 2005-10-15 20:37:12.589 |-- Start DB Query... 2005-10-15 20:37:12.596 |-- 8 results in 0.003785 sec. Processing... 2005-10-15 20:37:12.602 +-- Cleanup... 2005-10-15 20:37:12.604 AddNotListed... 2005-10-15 20:37:12.608 |-- Start DB Query... 2005-10-15 20:37:12.613 |-- 0 results in 0.000787 sec. Processing... 2005-10-15 20:37:12.616 Sort by time... 2005-10-15 20:37:12.621 PruneOverlaps... 2005-10-15 20:37:12.624 Sort by priority... 2005-10-15 20:37:12.628 BuildListMaps... 2005-10-15 20:37:12.632 SchedNewRecords... 2005-10-15 20:37:12.636 Scheduling: +Payback 90 1090 15 21:27-23:40 1 1 1 S 1 1 +Tri Nations Rugby League - "Austral 90 1090 15 23:27-01:40 1 2 2 S 2 1 +Mysterious Island 7 1007 15 19:37-23:10 1 2 2 S 2 1 ?Executive Command 7 1007 15 23:00-00:40 1 2 2 S - 1 ?Executive Command 7 1007 15 23:00-00:40 1 1 1 S - 1 ?Executive Command 7 1007 15 22:57-00:40 1 2 2 S - 1 ?Executive Command 7 1007 15 22:57-00:40 1 1 1 S - 1 ?Executive Command 7 1007 15 23:00-00:50 1 2 2 S - 1 ?Executive Command 7 1007 15 23:00-00:50 1 1 1 S - 1 ?Executive Command 7 1007 15 22:57-00:50 1 2 2 S - 1 ?Executive Command 7 1007 15 22:57-00:50 1 1 1 S - 1 2005-10-15 20:37:12.688 ClearListMaps... 2005-10-15 20:37:12.693 Sort by time... 2005-10-15 20:37:12.696 PruneRedundants... 2005-10-15 20:37:12.700 Sort by time... --- print list start --- Title - Subtitle Chan ChID Day Start End S C I T N Pri Mysterious Island 7 1007 15 19:37-23:10 1 2 2 S 2 1 Payback 90 1090 15 21:27-23:40 1 1 1 S 1 1 Executive Command 7 1007 15 22:57-00:50 1 0 0 S C 1 Tri Nations Rugby League - "Austral 90 1090 15 23:27-01:40 1 2 2 S 2 1 --- print list end --- 2005-10-15 20:37:12.724 Scheduled 4 items in 0.1 = 0.02 match + 0.12 place 2005-10-15 20:37:12.730 Recording starts soon, AUTO-Startup assumed 2005-10-15 20:37:12.734 Estimated program length: 200 minutes, size: 34689 MB, free space: 128976 MB 2005-10-15 20:37:12.737 TVRec(2): Changing from None to RecordingOnly 2005-10-15 20:37:12.741 DVB#1 Using DVB card 1, with frontend Zarlink MT352 DVB-T. 2005-10-15 20:37:12.803 Started recording: Mysterious Island: channel 1007 on cardid 2, sourceid 1 2005-10-15 20:37:13.458 DVB#1 DVB SI Table Parser Started 2005-10-15 20:37:13.576 Prog title: Mysterious Island 2005-10-15 20:37:13.602 DVB#1 Data read from DMX - This is for debugging with transform.c Cheers Dave On 10/15/05, David Engel <[EMAIL PROTECTED]> wrote: > On Sat, Oct 15, 2005 at 01:04:53PM +1000, David Shirley wrote: > > ok from record table the dupmethod is set to 6 is that right? > > Yes, that's the default. > > > also with your mini-patch i still get the same problem when i schedule > > a bunch of shows - > > One of your earlier comments led me to believe you were talking about > future recordings only. For the example you gave, this is the > expected behavior. Once a program starts recording, its times are > fixed. > > FWIW, that mini-patch does fix a real bug and a variation of it will > be in my commit. Thanks for inadvertently pointing it out. > > > HOWEVER if i restart mythbackend it resolves them all: > > This is because the recordings are no longer being recorded. They > need to be restarted, but doing so runs them through the scheduling > process again. The change I'm going to commit restores the ability to > change an in-progress end time, even with soft padding, so you'll be > able to resolve the conflict without restarting the backend. > > David > -- > David Engel > [EMAIL PROTECTED] > > > _______________________________________________ > mythtv-dev mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev > > > > _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
