Stupid question, but need an answer

[nv40]

This has probably been answered a million times before, but i spent 20 minutes using the search feature and I'm still sitting here without an answer so I'll surrender myself to the gbpvr gods. I'm trying to set gbpvr to record a show that comes on ever Wednesday, at 9:00-9:30. (southpark, FYI), Anyway, i set up gbpvr to "record every episode in this weekly time slot, on this channel" But with that settings, it also wants to record the episode of southpark that comes on right before it at 8:30-9:00 (the re-run from the previous week). Does gbpvr consider a time slot to be 1 hour, and not 30 minute intervals? Is the any way to change, or work around this? Thanks ahead of time.

P.S. If this has already been addressed, please just point me to the post about it, I swear I looked around for this before posting....thanks.

[sub]

To be within the 'timeslot' a show must have the same title and start within 90minutes +/- the originally scheduled recording start time. This is done to accommodate minor changes to the schedule, where one week a show might be played slightly later or slightly earlier. For the most part this scheme works well.

The size of this timeslot can be configured in config.xml if required by editing the default <AllowableTimeslotVariance>90</AllowableTimeslotVariance> setting.

[nv40]

To be within the 'timeslot' a show must have the same title and start within 90minutes +/- the originally scheduled recording start time. This is done to accommodate minor changes to the schedule, where one week a show might be played slightly later or slightly earlier. For the most part this scheme works well.

The size of this timeslot can be configured in config.xml if required by editing the default <AllowableTimeslotVariance>90</AllowableTimeslotVariance> setting.

My default settings was 120, not 90. I changed this to 25, which should allow it to pick up a show if it gets pushed back like 15 minutes because of a presidential speech or something like that, but it shouldn't pick up a show that is out side of that specific timeslot, correct. In other words, with is set for 25.....it won't pick up the show if it starts at 8:30 instead of 9:00----correct? also, do the settings in the config.xml get set back to default whenever a version upgrade is installed, or will this settings stay for me even through upgrades to gbpvr?

[stefan]

My default settings was 120, not 90. I changed this to 25, which should allow it to pick up a show if it gets pushed back like 15 minutes because of a presidential speech or something like that, but it shouldn't pick up a show that is out side of that specific timeslot, correct. In other words, with is set for 25.....it won't pick up the show if it starts at 8:30 instead of 9:00----correct? also, do the settings in the config.xml get set back to default whenever a version upgrade is installed, or will this settings stay for me even through upgrades to gbpvr?

You are correct about you time assumptions. Regarding the setting staying put between upgrades, I think it will. Most settings do. I have never touched AllowableTimeslotAllowance, so I can't vouch for that specific setting, though.

[sub]

The old default was 120 minutes. New installs have a default of 90 minutes. I purposefully wanted it to be at least 60 minutes, since it is fairly common for shows to be pushed out an hour.

Yes, it'll retain the setting during upgrades.

[nv40]

The old default was 120 minutes. New installs have a default of 90 minutes. I purposefully wanted it to be at least 60 minutes, since it is fairly common for shows to be pushed out an hour.

Yes, it'll retain the setting during upgrades.

I have changed this settings to 25, however it is still picking up shows that are 1 1/2 hours off the time slot. These are recordings that I have setup in season mode before I ever changed this value, do i have to cancel and re-setup these season recordings for this to take effect?

[sub]

do i have to cancel and re-setup these season recordings for this to take effect?

Yes, the timeslot is stored in the recording entry in the database.