Bug Report L180: End padding automatically zeroed for no reason

[Cheezmo]

I create a timer for Thursday 9:00 -> 9:58pm (since I don't want to mess with the padding and know it will add 3 minutes.

But, when I look at it, the end padding has been reset to 0.

I turns out there is an existing recording on another channel from 9:00 -> 9:30pm. For some reason, that "intersection" causes the padding to be 0'd.

Another bug, the other recording is on SHOHD. If I try to edit it, it tells me:

"Information 670
You may not edit a timer that is setup up for a Pay-Per-View event."

Not the "setup up" typo and of course the obvious problem that it is not a Pay-Per-View event (it is Penn & Teller).

[Cheezmo]

Another note, from the description, it appears that Penn & Teller had it's start and end time padding zeroed out also. I can't really check since attempts to edit it give me the Pay-Per-View error.

[Cheezmo]

And one more thing.

I just checked and my Sunday timer for Alias, which I set for 8:00 -> 8:58 now has its end padding set to 0 also and I can't set it back to 3. So, I had to edit the timer to change it back to 8:00 -> 9:00.

There are no overlapping timers on that one, but there is a timer later that night from 10:30 -> 12:05 am.

I almost thought all my weekly timers had lost their 3 minute padding, but the ones set to fire tonight still have it.

[Cheezmo]

Here is yet another scenario.

1) Created a timer from 2:00->4:00
2) Created a timer from 2:00->2:30
3) Created a timer from 3:30->5:00
4) Old timer existed from 6:00->7:45

2->2:30 still has all padding.
2-4 lost end padding
3:30-5:00 lost all padding
6->7:45 still has all padding

[the_tx_dude]

Here is yet another scenario.

1) Created a timer from 2:00->4:00
2) Created a timer from 2:00->2:30
3) Created a timer from 3:30->5:00
4) Old timer existed from 6:00->7:45

2->2:30 still has all padding.
2-4 lost end padding
3:30-5:00 lost all padding
6->7:45 still has all padding

I have seen same thing and have been very frustrated with it. I am not a programmer but this seems like pretty simple logic to set up once you decide how it should operate.

[Cheezmo]

The 2->2:30 recording ended up as a 0 second unplayable recording. Gee, and it is the only one that didn't have its padding messed with.

[David_Levin]

Yep, the pads are sure bizzare with this version.

If they can't get the padding to work, they should just take it out. Or just use the pads to adjust the initial guide based start/end times, then create the timer accordingly.

I'd rather have the pads work, but sheesh, they've caused more problems.

[SimpleSimon]

I know nothing about the GUI internals of this box, but these problems (changing days & padding) sure sound like the problems that occur when programming Windows dialogs and having the input control block definitions out-of-sync.

In other words, memory corruption.