Problems with season recordings - doesn't select right time & day

[UncleJohnsBand]

The web log(in the logs directory or from the statistics tab) will show the recording parameters that are set on the recurring recording when you create it.......post them here.

[servalan]

Looks like it might be timezone confusion...

Code:

<Rules>
  <EPGTitle>The Drum</EPGTitle>
  <ChannelOID>7162</ChannelOID>
  <ChannelName>ABC News 24</ChannelName>
  <StartTime>2010-09-02T08:05:00.0000000Z</StartTime>
  <EndTime>2010-09-02T08:45:00.0000000Z</EndTime>
  <PrePadding>5</PrePadding>
  <PostPadding>5</PostPadding>
  <Quality>3</Quality>
  <Keep>0</Keep>
  <Days>MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY</Days>
  <TimeslotStart>2010-09-02T06:35:00.0000000Z</TimeslotStart>
  <TimeslotEnd>2010-09-02T09:35:00.0000000Z</TimeslotEnd>
</Rules>

2010-09-02 09:52:35.593    [DEBUG][3]     - Already has episode at: 2/09/2010 8:05:00 AM
2010-09-02 09:52:35.609    [DEBUG][3]    LoadListingsMatchingTitle(channel=7162,title=The Drum)
2010-09-02 09:52:35.609    [DEBUG][3]     - Potential episode at: 2/09/2010 8:05:00 AM
2010-09-02 09:52:35.609    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.609    [DEBUG][3]     - Potential episode at: 2/09/2010 2:05:00 PM
2010-09-02 09:52:35.609    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.609    [DEBUG][3]     - Potential episode at: 2/09/2010 6:19:00 PM
2010-09-02 09:52:35.609    [DEBUG][3]       ...scheduling episode
2010-09-02 09:52:35.625    [DEBUG][3]     - Potential episode at: 3/09/2010 8:05:00 AM
2010-09-02 09:52:35.625    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.625    [DEBUG][3]     - Potential episode at: 3/09/2010 2:05:00 PM
2010-09-02 09:52:35.625    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.625    [DEBUG][3]     - Potential episode at: 3/09/2010 6:16:00 PM
2010-09-02 09:52:35.625    [DEBUG][3]       ...scheduling episode
2010-09-02 09:52:35.625    [DEBUG][3]     - Potential episode at: 6/09/2010 8:05:00 AM
2010-09-02 09:52:35.625    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.625    [DEBUG][3]     - Potential episode at: 6/09/2010 2:05:00 PM
2010-09-02 09:52:35.625    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.625    [DEBUG][3]     - Potential episode at: 6/09/2010 6:19:00 PM
2010-09-02 09:52:35.625    [DEBUG][3]       ...scheduling episode
2010-09-02 09:52:35.640    [DEBUG][3]    Checking if multi-record possible...
2010-09-02 09:52:35.640    [DEBUG][3]     - Potential episode at: 7/09/2010 8:05:00 AM
2010-09-02 09:52:35.640    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.640    [DEBUG][3]     - Potential episode at: 7/09/2010 2:05:00 PM
2010-09-02 09:52:35.640    [DEBUG][3]       ...doesnt match recurring rules
2010-09-02 09:52:35.640    [DEBUG][3]     - Potential episode at: 7/09/2010 6:19:00 PM
2010-09-02 09:52:35.640    [DEBUG][3]       ...scheduling episode
2010-09-02 09:52:35.656    [DEBUG][3]     - Potential episode at: 8/09/2010 8:05:00 AM
2010-09-02 09:52:35.656    [DEBUG][3]       ...doesnt match recurring rules

[UncleJohnsBand]

Ok...I will ask sub to take a look....NEWA sets up parameters and passes it into the NPVR API for actual scheduling.....what you are seeing here is the messages provided by the core NPVR code that does scheduling so it may be something in there......

[servalan]

This is the same schedule request from within the NPVR interface - it works fine:

From NPVR.log:

Code:

2010-09-02 10:27:58.140    [INFO][1]    UpdateRecurringRecording(97, 'The Drum'):
<Rules>
  <EPGTitle>The Drum</EPGTitle>
  <ChannelOID>7162</ChannelOID>
  <ChannelName>ABC News 24</ChannelName>
  <StartTime>2010-09-02T08:05:00.0000000</StartTime>
  <EndTime>2010-09-02T08:45:00.0000000</EndTime>
  <PrePadding>5</PrePadding>
  <PostPadding>5</PostPadding>
  <Quality>0</Quality>
  <Keep>0</Keep>
  <Days>MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY</Days>
  <TimeslotStart>2010-09-02T06:35:00.0000000</TimeslotStart>
  <TimeslotEnd>2010-09-02T09:35:00.0000000</TimeslotEnd>
</Rules>

2010-09-02 10:27:58.156    [DEBUG][1]     - Already has episode at: 2/09/2010 08:05:00
2010-09-02 10:27:58.218    [DEBUG][1]    LoadListingsMatchingTitle(channel=7162,title=The Drum)
2010-09-02 10:27:58.218    [DEBUG][1]     - Potential episode at: 2/09/2010 08:05:00
2010-09-02 10:27:58.234    [DEBUG][1]       ...already got this episode scheduled
2010-09-02 10:27:58.234    [DEBUG][1]     - Potential episode at: 2/09/2010 14:05:00
2010-09-02 10:27:58.234    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.234    [DEBUG][1]     - Potential episode at: 2/09/2010 18:19:00
2010-09-02 10:27:58.234    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.234    [DEBUG][1]     - Potential episode at: 3/09/2010 08:05:00
2010-09-02 10:27:58.234    [DEBUG][1]       ...scheduling episode
2010-09-02 10:27:58.265    [DEBUG][1]     - Potential episode at: 3/09/2010 14:05:00
2010-09-02 10:27:58.265    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.265    [DEBUG][1]     - Potential episode at: 3/09/2010 18:16:00
2010-09-02 10:27:58.265    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.265    [DEBUG][1]     - Potential episode at: 6/09/2010 08:05:00
2010-09-02 10:27:58.265    [DEBUG][1]       ...scheduling episode
2010-09-02 10:27:58.296    [DEBUG][1]     - Potential episode at: 6/09/2010 14:05:00
2010-09-02 10:27:58.296    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.296    [DEBUG][1]     - Potential episode at: 6/09/2010 18:19:00
2010-09-02 10:27:58.296    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.296    [DEBUG][1]     - Potential episode at: 7/09/2010 08:05:00
2010-09-02 10:27:58.296    [DEBUG][1]       ...scheduling episode
2010-09-02 10:27:58.328    [DEBUG][1]     - Potential episode at: 7/09/2010 14:05:00
2010-09-02 10:27:58.328    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.328    [DEBUG][1]     - Potential episode at: 7/09/2010 18:19:00
2010-09-02 10:27:58.328    [DEBUG][1]       ...doesnt match recurring rules
2010-09-02 10:27:58.328    [DEBUG][1]     - Potential episode at: 8/09/2010 08:05:00
2010-09-02 10:27:58.328    [DEBUG][1]       ...scheduling episode

[sub]

UJB, where are you getting your EPGEvent you're passing to ScheduleHelperFactory.GetScheduleHelper().ScheduleRecording() when you create the season recording? I think the problem relates to the way the dates have been initialised on the EPGEvent you're using.

[UncleJohnsBand]

UJB, where are you getting your EPGEvent you're passing to ScheduleHelperFactory.GetScheduleHelper().ScheduleRecording() when you create the season recording? I think the problem relates to the way the dates have been initialised on the EPGEvent you're using.

There is an NPVR schedule in NEWA that is the interface to the helper.....I am getting the event that I pass into the scheudule event via the EPGEvent.LoadByOID method....

Code:

private IScheduleHelper scheduleHelper
        {
            get
            {
                if (ScheduleHelperFactory.GetScheduleHelper() == null)
                {
                    //ScheduleHelperFactory.SetScheduleHelper(RecordingServiceProxy.GetServiceInstance());

                    RecordingServiceProxy.ForceRemote();
                    ScheduleHelperFactory.SetScheduleHelper(RecordingServiceProxy.GetInstance());
                }
                IScheduleHelper helper = ScheduleHelperFactory.GetScheduleHelper();
                return helper;
            }
        }

        public override EPGEvent GetEPGEventByOID(int oid)
        {
            return EPGEvent.LoadByOID(oid);
        }

[sub]

The significant difference in the two examples servalan shows above is the 'Z' on the end of the date times. I'm not quite sure why though. If you'd been loading EPGEvents directly, but not using DateTime.SpecifyKind(), that could explain it, but it should be fine if that date had come from EPGEvent.LoadByOID() though.

[UncleJohnsBand]

The significant difference in the two examples servalan shows above is the 'Z' on the end of the date times. I'm not quite sure why though. If you'd been loading EPGEvents directly, but not using DateTime.SpecifyKind(), that could explain it, but it should be fine if that date had come from EPGEvent.LoadByOID() though.

hmmm....I am pulling it from the EPGEvent.LoabByOID()....and not touching it.........

[UncleJohnsBand]

hmmm....I am pulling it from the EPGEvent.LoabByOID()....and not touching it.........

It is coming back from the API that way.....here is the object after the call...



Uploaded with ImageShack.us

[sub]

I can kind of see what is happening, but I need to have a think about how to fix it and not break other things.