What does the padding in the Config do?

[fldavem]

I have some already scheduled recordings, some through the EWA and some through the GBPVR interface. The GBPVR config is set for 90 minute padding, but the recording I just made had no padding. This is likely one I scheduled through the web.

Can someone tell me

1. Does the padding in the GBPVR Config have any control on web scheduled recording?
   
2. Does changing the GBPVR Config padding have any effect on the recordings already scheduled through the GBPVR interface? What about the next time you change it, what scheduled recordings would change?
   
3. Does it have any effect on recordings not yet scheduled?
   
4. Is there a way to change the default padding of 0 that seems to be on the EWA?
   
5. If there is, again, will that effect recordings already scheduled or only future ones?
   

If it is possible to control future scheduled recordings, what I'd like to do is delete my sporting events, change the padding to add, say 60 minutes post padding, schedule the sporting events, and then change the padding back to 0 for normal tv shows.

[stefan]

90 minutes padding? Is that pre or post padding? Are you sure it's not <AllowableTimeslotVariance> you are talking about? That is set to 90 minutes, but has nothing to do with padding...

[fldavem]

It's post padding, 'cause sometimes the games go extra long.

Is the AllowableTimeslotVariance something that will dynamically control the recording times, like if a show gets postponed a few minutes or something? Or would that be helpful if a scheduled event is supposed to stop at 11pm but because of a tie, the game doesn't end until midnight?

[stefan]

No, AllowableTimeSlotVariance is for shows that get moved a bit. Say that you have a Season recording for show A at 11.00 each week, and this one week it gets moved to 12.00. Then a setting of 90 would still make it record. It has to have been moved in the EPG, though, in order for gbpvr to see that it has been moved.

[fldavem]

So what would help with the recording of longer than expected sporting events?

[ww4397]

So what would help with the recording of longer than expected sporting events?

Post padding. This will add the padding amount to the end of the scheduled end time. This works if there are no other shows to be recorded during the padding period. This is the way it works for a one tuner setup.

Things get a little different with multiple tuners.

[preinke]

Post padding. This will add the padding amount to the end of the scheduled end time. This works if there are no other shows to be recorded during the padding period. This is the way it works for a one tuner setup.

Things get a little different with multiple tuners.

I'm still trying to work out why my setup closes one recording (at the end of it's normal time *without* padding, when a perfectly good tuner card sits idle?

I've described the problem in a different thread, but to recap:
* All shows are pre-pad 5 minutes and post-pad 15 minutes
* Three tuners (Asus P7131 Dual) recording via BDA
* Tuner C starts recording a show on Channel X at 18:55 (Recording is supposed to be 19:00 to 19:30)
* Tuner A starts recording a show on Channel Y at 19:25 (Recording is supposed to be 19:30 to 20:00)
* Recording on Tuner C stops at 19:30 and starts recording Channel Z (recording is supposed to be 19:30 to 20:00)
* Tuner B starts recording a show on Channel Y at 19:55 (recording is suppsed to be 20:00 to 20:30) - note the overlap with Tuner A
* Tuner A stops recording at 20:15 (as expected)
* Tuner B stops recording at 20:45 (as expected)
* Tuner C stops recording at 20:15 (as expected)

Any thoughts as to why it didn't use Tuner B when I would expect it to?

The config.xml has been set up with the "PreferAlternatingCaptureSources" is set to false.

I've attached the full log if it's helpful

Paul

[stefan]

Which version of gbpvr are you using? If you are using the latest (99.5), you also have the option <TryToHonourPaddingIfPossible> to play with.

[elite]

Set "PreferAlternatingCaptureSources" to true

[elite]

Which version of gbpvr are you using? If you are using the latest (99.5), you also have the option <TryToHonourPaddingIfPossible> to play with.

Oooh - hadn't spotted that sneaky addition