Hi Dave,
Yes, I have. After posting, I did some additional searches and - as far as I can tell - this is the culprit. If "Use EPG running state" is chosen, the padding and hand-editing start/stop time take no effect. As such, this explains the behavior I'm seeing (unless I'm mistaken; I believe this option is poorly documented).
It is up to the EPG data provider to update the running flag in the EPG data. It seems that they often fail to do so. Also, I've used editing these fields to work around channels, which "chop" an event into several EPG entries (1. period, 2nd period, 3rd period ... which is just bothersome, since it is much more nices to have one recording; and also, the times don't usually match the actual end(s) of periods).
Overall, I think this is
an user error, but I also think the current UI is extremely counter-intuitive. There should be some notification that editing the times (or padding) will have no effect since the option is selected?