padding

[rac8006]

How does padding work? Lets say that I have 2 HD tuners. I set the padding to 2 minutes. Then I tell it to record two programs at 9:00PM and then 2 programs at 10:00PM. If the channels are not the same what does it record. I've noticed that if I set padding to 0 then I sometimes miss a little bit of the start of a program.

How do other people handle this case?

thanks
RAC

[SmokeWatcher]

The padding starts the recording before the scheduled show time for however many minutes you set it for. If the recordings are back-to-back, then there is no padding.

[nanook105]

Originally Posted by rac8006

How does padding work? Lets say that I have 2 HD tuners. I set the padding to 2 minutes. Then I tell it to record two programs at 9:00PM and then 2 programs at 10:00PM. If the channels are not the same what does it record. I've noticed that if I set padding to 0 then I sometimes miss a little bit of the start of a program.

How do other people handle this case?

thanks
RAC

Padding is added to the start and end of the shows. If you have back to back on all of your available tuners, you will get start padding and no end padding on the 9:00 shows and no start padding but end padding on the 10:00 shows.

I just added more tuners to address the issue.

[Nick Burns]

Except when it doesn't work.
*sigh*

[nanook105]

Originally Posted by Nick Burns

Except when it doesn't work.
*sigh*

Well, I think that your's is working as defined, but it isn't working as you want

[Nick Burns]

Originally Posted by nanook105

Well, I think that your's is working as defined, but it isn't working as you want

I'm not quite sure I agree with that. (Though I do appreciate your help!) Each show is on it's own tuner to address the padding as you stated above, but it's not padding as it should. If there's no show being recorded on a tuner in the next time slot, then there should be padding on that last show it recorded, regardless if other tuners are recording shows in the next time slot. This doesn't seem to be the case.

Great, and I know it's my fault, but now it appears that now we're talking about the same issue in two different threads.