CDK Scheduler AdjustEndTime

[KingArgyle]

Fla, when you get a chance, you might want to check out the RecordingUtils.dll file and see if AdjustEndTime is being used correctly. In the PriorityRecordings.xml file there are two optional tags under the Padding element called AdjustStartTime and AdjustEndTime, these elements allow for the program start and end times to be adjusted to get around scheduling conflicts. typical situation is to schedule a program from 9:00pm to 10:01pm, so that if another program starts at 10:00 on a competing station the program isn't scheduled.

The AdjustStartTime element seems to be working correctly in that if their is a conflict it will correctly adjust the start time by the time of the program in conflict (i.e. lower priority recording) to get around the confict (i.e adjust the start time of the program to 10:01pm).

AdjustEndTime is supposed to adjust the end time by the time specified if it is included. So if a -1 is specified it should subtract 1 from the end time of the program to get around the conflict. Unfortunately it doesn't seem to work in the version that I'm using. AdjustStartTime is working so I can use that, but the original intent was to give the flexibility to the user to control and work around these weird scheduling issues that the networks play.

[fla]

I added it to my list.

What's your EPG source btw now that zap2it is gone? I use zap2xml scraper and don't have any extra EPG info like unique ID and recorded a duplicate recently because the description was slightly different. One of the items on my list is to integrate the SchedulesDirect utilities into CDK Scheduler and XSuite to replace zaptools but I don't have an account yet. Any other ways to get enhanced EPG data other than SchedulesDirect utilities.

[KingArgyle]

I use SchedulesDirect as my data source, with the xmltv grabber. For duplicate detection, I use RecTracker, and CDK Scheduler.

CDK Scheduler relies on RecTracker's duplicate detection algorithim which is the Title, SubTitle, and Description. If all of that is the same then it's a duplicate, otherwise it's a new show. Works about 99.9% of the time with SchedulesDirect, and doesn't rely on the unique ids.

[fla]

Fixed. Code checked into sourceforge and new version on the wiki. It was just a small copy paste error in XSearch's AddFutureRecordingPopup which is used by XGuide and XRecord too.