TiVo recording at wrong time (or is is right time)

[Wanted]

I have noticed for the last couple of days by TiVo has been starting recording at the true start time. That is, it isn't starting 5 minutes early and fininshing 10 minutes late. A program from 8:30 - 9:00 is a 30 minute recording from 8:30 onstead of a 45 minute recording from 8:25. There aren't other recorings happening before and after either. The clock looks correct too. Any idea why this is happening?

[thomson]

That is, it isn't starting 5 minutes early and fininshing 10 minutes late.

EndPad/EndPadPlus is the process responsible for padding the recordings.
The log file for this process can be found at /var/log/endpad.log (although you may also want to check endpad.sys, etc). You should be able to check these from the command line or via the TivoWeb Log module.

If you wish to check if the process is still running you can use: "pp auxww | grep endpad". In fact if you are a little linux savy you could setup an alias/shortcut in your .profile that reads:

alias pp='ps auxww | grep -v "grep -" | grep -i'

This will allow you to check for running processes using "pp endpad"

[Wanted]

Here is my output:

[TiVo [p0] ~]# alias pp='ps auxww | grep -v "grep -" | grep -i'
[TiVo [p0] ~]# pp endpad
root       188  0.0  8.2  8296  1144  ?  S    08:47   0:03 tivosh /var/hack/endp
adplus.tcl -run 5 10 {-auto\015}

Can't tell if that means it is running or not. :-/

The log seems to just repeat this over and over every 30mins:

Tuesday 08:47:34 : EndPadPlus log file, log rotated
Tuesday 08:47:34 : Back to sleep...
Tuesday 08:47:34 : Checking every minute for kill signal...............................
Tuesday 09:17:00 :
Tuesday 09:17:00 : Rise and shine!
Tuesday 09:17:00 : Processing current recording(s):
Tuesday 09:17:00 : * No recordings in progress
Tuesday 09:17:00 : Processing next recording(s):
Tuesday 09:17:00 : * Charmed on [3 TV3] from 19:30 to 20:30 (Season Pass)
Tuesday 09:17:00 : Not time to add start padding yet
Tuesday 09:17:00 : Next end padding setting due 20:23
Tuesday 09:17:00 : Next start padding setting due 19:23
Tuesday 09:17:00 : Next wake up will be 09:47
Tuesday 09:17:00 : Back to sleep...
Tuesday 09:17:00 : Checking every minute for kill signal...............................
Tuesday 09:47:00 :
Tuesday 09:47:00 : Rise and shine!
Tuesday 09:47:00 : Processing current recording(s):
Tuesday 09:47:00 : * No recordings in progress
Tuesday 09:47:00 : Processing next recording(s):

I have tried settime -rtc and rebooted a couple of time. Still seems to start on the exact start time.

[Wanted]

I think when I was doing my testing it wasn't getting to 17 or 47 minutes past the hour so endpad wouldn't have run to set this up. It seems to run every half hour unless it sets itself to run before a sheduled recording (checked when it runs every half hour). I'll see what happens over the next day or so because one of the reboots may have fixed it.