Automatic soft padding running on the TiVo

[iankb]

Originally Posted by cwaring

... no UK channel has ever deliberately over-run by your stated ten minutes just because they felt like it.

ITV certainly went over by almost 10 minutes once with 'Who Wants To Be a Millionaire'. They were trying to stop people switching over to another programme on BBC1.

[cwaring]

I just knew someone would give an example Fair enough, but as I said, it's not a very common occurence

[maxwells_daemon]

Hi Peter,

Originally Posted by petestrash

The last few days on just one TiVo some of the validity rules have been ignored and the global padding settings used instead.

Tuesday 00:25:01 : channel GWN-WA validity 20:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1
Tuesday 00:25:01 : channel GWN-WA validity 22:01-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1
...SNIP...
Tuesday 22:55:00 : Added 300 seconds end padding to {Last Man Standing} on GWN-WA

Even though I have channel GWN-WA set for 'validity 22:01-06:00 endpad 20', at 22:55 only the global 5 minutes endpading was added not 20.

Last Man Standing wasn't scheduled to start at exactly 22:00, was it? It is the start time that is important for the validity selection, since if the start of the programme is delayed, chances are the end is too. Your time-dependent settings have a gap from 22:00 to 22:01, so if the scheduled start time fell in there, it would pick up the global settings.

To close the gap, you should instead specify

channel GWN-WA validity 20:00-22:00 endpad 18
channel GWN-WA validity 22:00-06:00 endpad 20

The validity 20:00-22:00 includes 20:00, but excludes 22:00 (ie. goes up to 21:59:59), so there wouldn't be any overlap (not that that would be a problem).

Does this explain your observation?

Tim.

[mike0151]

Originally Posted by cwaring

I just knew someone would give an example Fair enough, but as I said, it's not a very common occurence

The Frank Skinner Show usually over-runs by 8 to 10 minutes on ITV1.

[cwaring]

tarball'd /var/hack from my Tivo and cpio'd it onto my brother's unit.

Got the following in the.log file. Replacing with default .config file didn't help

Friday 13:39:54 : 
Friday 13:39:54 : endpad.tcl 1.4.2-md5 log file, starting up
Friday 13:39:54 : Start padding set to 120 seconds
Friday 13:39:54 : End padding set to 300 seconds
Friday 13:39:54 : Negative start padding set to 0 seconds
Friday 13:39:54 : Force Negative startpadding is 0
Friday 13:39:54 : Suggestions will be padded, even if that means cancelling a subsequent suggestion
Friday 13:39:54 : Detected TiVo software version 2.5.5-01-1-023
Friday 13:39:54 : Suggestion quality change disabled
Friday 13:39:54 : Timezone 00:00
Friday 13:39:54 : Sorted configuration options (last match used):-
Friday 13:39:54 : startpad 2 endpad 5 negpad 0 forceneg 0 maxneg -1 sugeq 1 sugqual -1
Friday 13:39:54 : Woken up
Friday 13:39:55 : Error detected
Friday 13:39:55 : can't read "rectype": no such variable
while executing
"if {$rectype == 3} {

# Recording active
set isrec 1

# Get details of currently recording programme
RetryTransaction ..."
Friday 13:39:55 : Attempting to recover
Friday 13:40:25 : Woken up
Friday 13:40:25 : Error detected
Friday 13:40:25 : can't read "rectype": no such variable
while executing
"if {$rectype == 3} {

# Recording active
set isrec 1

# Get details of currently recording programme
RetryTransaction ..."
Friday 13:40:25 : Attempting to recover
Friday 13:40:25 : Too many errors, stopping

Probably something simple, like a difference between the two Tivos or something. Just got no idea what

[sanderton]

Clean TiVo? Endpad won't run unless there are two items in the To Do list.

Mentioned a few times above. These newbies who don't read the thread before posting.

[petestrash]

Originally Posted by maxwells_daemon

Hi Peter,

Last Man Standing wasn't scheduled to start at exactly 22:00, was it? It is the start time that is important for the validity selection, since if the start of the programme is delayed, chances are the end is too. Your time-dependent settings have a gap from 22:00 to 22:01, so if the scheduled start time fell in there, it would pick up the global settings.

I guess I made too many assumptions

My 1st assumption was a validity of 20:00-22:00 was inclusive and not 20:00-21:59 inclusive.

My 2nd assumption was that when endpad woke up at 22:55 to add the endpadding, it would then check the validity rules that applied at that time and then apply the endpad amount. I did not realise the start time was used for endpadding validity.

Unfortunately I didn't keep the logs showing the other programs that had problems, to see if they all fell into the hole at 22:00, but it's quite possible.

Originally Posted by maxwells_daemon

Does this explain your observation?

I believe it explains that one, but I also have another anomaly on a different tivo using the same version of endpad.

Friday 00:25:01 : endpad.tcl 1.4.2-md3 log file, log rotated
Friday 00:25:01 : Start padding set to 60 seconds
Friday 00:25:01 : End padding set to 300 seconds
Friday 00:25:01 : Suggestions will not be padded if another suggestion immediately follows them
Friday 00:25:01 : Detected TiVo software version 3.0-01-1-000
Friday 00:25:01 : Suggestion quality change disabled
Friday 00:25:01 : Timezone 00:00
Friday 00:25:01 : Configuration options:-
Friday 00:25:01 : default: endpad 5 sugeq 0 sugqual -1 startpad 1
Friday 00:25:01 : channel Nine-WA validity 20:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1
Friday 00:25:01 : channel Nine-WA validity 22:01-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1
Friday 00:25:01 : channel Seven-WA validity 20:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1
Friday 00:25:01 : channel Seven-WA validity 22:01-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1
Friday 00:25:01 : channel Ten-WA validity 20:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1
Friday 00:25:01 : channel Ten-WA validity 22:01-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1
Sleeping, checking every minute for kill signal...................
...SNIP...
Friday 23:58:00 : Woken up
Friday 23:58:00 : No recording in progress
Friday 23:58:00 : Next recording is Cops on Ten-WA at 00:00
Friday 23:58:00 : No end padding required:
Friday 23:58:00 : No recording in progress
Friday 23:58:00 : Next end padding setting due 00:25
Friday 23:58:00 : Added 60 seconds start padding to Cops on Ten-WA
Friday 23:58:00 : Next start padding setting due 00:25
Friday 23:58:00 : Next wake up will be 00:25
Sleeping, checking every minute for kill signal............................
Saturday 00:25:00 : Woken up
Saturday 00:25:00 : Recording Cops on Ten-WA now
Saturday 00:25:00 : Recording Scheduled End Time: 00:30
Saturday 00:25:00 : Next recording is Raid on SBS-WA (Suggestion) at 00:45
Saturday 00:25:00 : Current recording is on Ten-WA and starts at 00:00 so use endpad 20
Saturday 00:25:00 : Gap to next programme is 900 seconds
Saturday 00:25:00 : Added 900 seconds end padding to Cops on Ten-WA
Saturday 00:25:00 : Next end padding setting due 02:45
Saturday 00:25:00 : Not time to add start padding yet
Saturday 00:25:00 : Next start padding setting due 00:43
Saturday 00:25:00 : Next wake up will be 00:43
Saturday 00:25:00 : endpad.tcl 1.4.2-md3 log file, log rotated
Saturday 00:25:00 : Start padding set to 60 seconds
Saturday 00:25:00 : End padding set to 1200 seconds
Saturday 00:25:00 : Suggestions will not be padded if another suggestion immediately follows them
Saturday 00:25:00 : Detected TiVo software version 3.0-01-1-000
Saturday 00:25:00 : Suggestion quality change disabled
Saturday 00:25:00 : Timezone 00:00
Saturday 00:25:00 : Configuration options:-
Saturday 00:25:00 : default: endpad 5 sugeq 0 sugqual -1 startpad 1
Saturday 00:25:00 : channel Nine-WA validity 20:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1
Saturday 00:25:00 : channel Nine-WA validity 22:01-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1
Saturday 00:25:00 : channel Seven-WA validity 20:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1
Saturday 00:25:00 : channel Seven-WA validity 22:01-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1
Saturday 00:25:00 : channel Ten-WA validity 20:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1
Saturday 00:25:00 : channel Ten-WA validity 22:01-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1
Sleeping, checking every minute for kill signal...................
Saturday 00:43:00 : Woken up
Saturday 00:43:00 : Recording Cops on Ten-WA now
Saturday 00:43:00 : Recording Scheduled End Time: 00:45
Saturday 00:43:00 : Next recording is Raid on SBS-WA (Suggestion) at 00:45
Saturday 00:43:00 : Current recording is on Ten-WA and starts at 00:00 so use endpad 20
Saturday 00:43:00 : Gap to next programme is 900 seconds
Saturday 00:43:00 : Added 900 seconds end padding to Cops on Ten-WA
Saturday 00:43:00 : Next end padding setting due 02:45
Saturday 00:43:00 : Gap to previous recording is 0 seconds
Saturday 00:43:00 : Can't add start padding to Raid
Saturday 00:43:00 : Next start padding setting due 02:45
Saturday 00:43:00 : Next wake up will be 01:13
Sleeping, checking every minute for kill signal...............................
Saturday 01:13:00 : Woken up
Saturday 01:13:00 : Recording Raid on SBS-WA (Suggestion) now
Saturday 01:13:00 : Recording Scheduled End Time: 02:50
Saturday 01:13:00 : Next recording is {Queens Supreme} on Ten-WA at 04:00
Saturday 01:13:00 : Not time to add end padding yet
Saturday 01:13:00 : Next end padding setting due 02:45
Saturday 01:13:00 : Not time to add start padding yet
Saturday 01:13:00 : Next start padding setting due 03:58
Saturday 01:13:00 : Next wake up will be 01:43

On this TiVo the log says "Saturday 00:25:00 : Current recording is on Ten-WA and starts at 00:00 so use endpad 20" which the other TiVo does not show. If it did I wouldn't have posted the previous question

There is a 15 minute gap between 'Cops' and a suggestion 'Raid'. The endpad validity is set for 20 minutes, but endpad did not cancel the suggestion and only endpaded the 15 minutes gap.

Then 13 minutes into the endpadding time, endpad woke up again and tried to add another 15 minutes endpading. There were no errors in the log, but the extra endpadding was not added and the suggestion was still recorded.

Peter

PS I have since fixed the 22:00 gap on this TiVo also.

[Fozzie]

Just noticed this:

Thursday 20:58:00 : Woken up
Thursday 20:58:01 : Error detected
Thursday 20:58:01 : no such object: {CONFLICT err=errTmActiveLockConflict}
while executing
"dbobj $cstation get CallSign"
("uplevel" body line 11)
invoked from within
"uplevel $body"
invoked from within
"transaction {uplevel $body}"
(procedure "RetryTransaction" line 4)
invoked from within
"RetryTransaction {
set crec [db $db openid $recfsid]
if {$version >= 3} {
set crecbeh [dbobj $crec get RecordingBehavi..."
Thursday 20:58:01 : Attempting to recover
Thursday 20:58:31 : Woken up
Thursday 20:58:32 : Error detected
Thursday 20:58:32 : no such object: {CONFLICT err=errTmActiveLockConflict}
while executing
"dbobj $cstation get CallSign"
("uplevel" body line 11)
invoked from within
"uplevel $body"
invoked from within
"transaction {uplevel $body}"
(procedure "RetryTransaction" line 4)
invoked from within
"RetryTransaction {
set crec [db $db openid $recfsid]
if {$version >= 3} {
set crecbeh [dbobj $crec get RecordingBehavi..."
Thursday 20:58:32 : Attempting to recover
Thursday 20:58:32 : Too many errors, stopping

And ideas Stuart?

[sanderton]

Restart the TiVo? - it's having trouble retriving data drom the database.

[Fozzie]

Thanks. I've done that just in case. No doubt it's just one of those things that happens from time to time. Still, not bad though since I think that's the first time ever that endpad has keeled; shame I didn't notice yesterday before the end of Casualty was chopped! Makes you realise how vital Endpad is (and Dailymail for telling me it had stopped running).

[Ian_m]

Another suggestion for endpad functionality (or a separate CRONable tcl module if anyones interested, Sanderton ???????).

A module/function/endpad functionality to automatically set the ratings for programmes based on the start record time and/or channel. The reason for adding to endpad is it already has CFG init file reading capability and is "active" when a programme is recording. Could also be done as a CRON job once a day to process the ToDo and/or Now Playing list.

This would work in conjunction with the TiVo Parental controls systems to stop kids viewing things they shouldn't ie if they select "Lesbian Lavatory Lust the Series" they would be prompted for a TiVo password (ie 4 numbers). I know Parental controls (possibly) works with films, but not with other recordings.

The cfg file would have a lines like:-

default U
18:00-21:00 12 L
21:00-6:00 18 M
M&M 18 M
CBEEBIES U

Where U=U rating, 12=12 rating etc, M&M = Men and Motors channel, L=strong language, M=violent material. See page 17 of the UK 2.5.5 TiVo user guide for the ratings recognised.

Not to sure if series can have ratings or not. Exploring MFS I can see fields for movies of MpaaRating and Advisory, but nothing equivalent for a series/one off. Wonder if these fields were added to a series/one off the TiVo would honour it in the Parental controls.

Might also need an add-on to TiVoWeb to allow the programme rating to be edited if set wrong. (or the kids to bypass it if they eventually hack TiVoWeb).

Any thoughts anyone ? Looking for an interesting new module Sanderton ?

[Ian_m]

Another suggestion for endpad functionality (or a separate CRONable tcl module if anyones interested, Sanderton ???????).

A module/function/endpad functionality to automatically set the ratings for programmes based on the start record time and/or channel. The reason for adding to endpad is it already has CFG init file reading capability and is "active" when a programme is recording. Could also be done as a CRON job once a day to process the ToDo and/or Now Playing list.

This would work in conjunction with the TiVo Parental controls systems to stop kids viewing things they shouldn't ie if they select "Lesbian Lavatory Lust the Series" they would be prompted for a TiVo password (ie 4 numbers). I know Parental controls (possibly) works with films, but not with other recordings.

The cfg file would have a lines like:-

default U
18:00-21:00 12 L
21:00-6:00 18 M
M&M 18 M
CBEEBIES U

Where U=U rating, 12=12 rating etc, M&M = Men and Motors channel, L=strong language, M=violent material. See page 17 of the UK 2.5.5 TiVo user guide for the ratings recognised.

Not to sure if series can have ratings or not. Exploring MFS I can see fields for movies of MpaaRating and Advisory, but nothing equivalent for a series/one off. Wonder if these fields were added to a series/one off the TiVo would honour it in the Parental controls.

Might also need an add-on to TiVoWeb to allow the programme rating to be edited if set wrong. (or the kids to bypass it if they eventually hack TiVoWeb).

Any thoughts anyone ? Looking for an interesting new module Sanderton ?

[sanderton]

Easiy enough to code in - if it works! Would need someone to try manually adding those attributes to see. As there is no diffeence in MFS between movies and episodes I think there's agood chance it would.

You can use dbget and dbset to try it out.

[Ian_m]

Thinking about it a bit more, a CRON job running once a day would be better as it could have its own CFG input file and own output LOG file, thus not "contaminating" endpads CFG and LOG files.

You could also invoke it manually if needed as well.

I feel the hard bit (if implemented) would be modifying TiVoWeb to allow the attributes to be modded.

I am sure someone a while back said they were looking for ideas for something new to write for their TiVo......

[sanderton]

No, that's very easy. You'd just add a line of code to the Edit Recording page.

Trouble with doing it from cron is that recordings would be unproteced for a while.

[Ian_m]

Originally Posted by sanderton

Trouble with doing it from cron is that recordings would be unproteced for a while.

No it probably wouldn't, as if you put the ratings in the ToDo data and ran the CRON job daily, the programme would have the rating "inserted" maybe upto 2 weeks in advance.

Anyway, for your homework tonight, Mr Sanderton I expect a complete working and debugged programme (CRON script and TiVoWeb mods), to be ready on my desk by the morning, else its no TiVo for you...... (only joking )

[LJ]

Having a problem with DS9 on Sky at the moment where it always seems to start a little early. Would it be possible to add the start version of "negpad", so the preceeding programme is ended early rather than not being recorded at all?

[maxwells_daemon]

I've been running endpad-1.4.2-md5 for the last six weeks and it seems to work fine. Did anyone else try that version yet?

I noticed one oddity that I hope tym (in particular) can comment on. A few times the logfiles show that the same suggestion is deleted twice "to make room for startpad". The result seems to be OK (the suggestion is gone and the subsequent programme has the padding added), but I don't understand why this should happen. Maybe the suggestion is cancelled too early and so it pops up again.

Come to think of it, why does the suggestion have to be explicitly deleted at all? If the start padding is increased before the previous suggestion starts recoding, won't it give a conflict so the suggestion isn't recorded?

Anyway, this double deletion took place in 3 of the 15 times that my suggestions were deleted to make room for start padding. Here's one example from the logfile:-

Friday 18:58:00 :  Woken up
Friday 18:58:00 :  Next recording ({Boston Legal} at 20:00 on Fri) starts in 17:00-05:00 so use startpad 1
Friday 18:58:00 :  Deleting suggestion {The Simpsons} on SKYONE to make room for 60 seconds startpad of {Boston Legal} on LIVING
Friday 18:58:00 :  Recording {Veronica Mars} on LIVING  now
Friday 18:58:00 :  Recording Scheduled End Time: 19:02
Friday 18:58:00 :  Next recording is {Boston Legal} on LIVING  at 20:00
Friday 18:58:00 :  Next recording ({Boston Legal} at 20:00 on Fri) starts in 17:00-05:00 so use startpad 1
Friday 18:58:00 :  No end padding required:
Friday 18:58:00 :  End padding of 120 seconds already set
Friday 18:58:00 :  Next end padding setting due 20:55
Friday 18:58:00 :  Gap to previous recording is 3480 seconds
Friday 18:58:00 :  Added 60 seconds start padding to {Boston Legal} on LIVING 
Friday 18:58:00 :  Next start padding setting due 20:55
Friday 18:58:00 :  Next wake up will be 19:28
Sleeping, checking every minute for kill signal............................... 
Friday 19:28:00 :  Woken up
Friday 19:28:00 :  Next recording ({Boston Legal} at 20:00 on Fri) starts in 17:00-05:00 so use startpad 1
Friday 19:28:00 :  Deleting suggestion {The Simpsons} on SKYONE to make room for 60 seconds startpad of {Boston Legal} on LIVING
Friday 19:28:00 :  No recording in progress
Friday 19:28:00 :  Next recording is {Boston Legal} on LIVING  at 20:00
Friday 19:28:00 :  Next recording ({Boston Legal} at 20:00 on Fri) starts in 17:00-05:00 so use startpad 1
Friday 19:28:00 :  No end padding required:
Friday 19:28:00 :  No recording in progress
Friday 19:28:00 :  Next end padding setting due 20:55
Friday 19:28:00 :  Added 60 seconds start padding to {Boston Legal} on LIVING 
Friday 19:28:00 :  Next start padding setting due 20:55
Friday 19:28:00 :  Next wake up will be 19:58

Tim.

[maxwells_daemon]

Originally Posted by petestrash on 22nd Oct concerning endpad.tcl 1.4.2-md3

On this TiVo the log says "Saturday 00:25:00 : Current recording is on Ten-WA and starts at 00:00 so use endpad 20" which the other TiVo does not show. If it did I wouldn't have posted the previous question

That's odd. Did the two TiVos have the same configuration parameters?

There is a 15 minute gap between 'Cops' and a suggestion 'Raid'. The endpad validity is set for 20 minutes, but endpad did not cancel the suggestion and only endpaded the 15 minutes gap.

Then 13 minutes into the endpadding time, endpad woke up again and tried to add another 15 minutes endpading. There were no errors in the log, but the extra endpadding was not added and the suggestion was still recorded.

Sorry, I don't have any ideas (I didn't really look at that part of the code). Can you try the latest version, endpad-1.4.2-md5? That includes tym's code for deleting suggestions to allow start padding too. If there's a bug, it would be easiest to spot in our latest code.

Thanks,
Tim.

[tym]

Originally Posted by maxwells_daemon

I noticed one oddity that I hope tym (in particular) can comment on. A few times the logfiles show that the same suggestion is deleted twice "to make room for startpad". The result seems to be OK (the suggestion is gone and the subsequent programme has the padding added), but I don't understand why this should happen. Maybe the suggestion is cancelled too early and so it pops up again.

Come to think of it, why does the suggestion have to be explicitly deleted at all? If the start padding is increased before the previous suggestion starts recoding, won't it give a conflict so the suggestion isn't recorded?

Tim.

Tim

I have thought about relying on the TiVo not recording the suggestion automatically and not deleting the suggestion, but your example above seems to indicate that the TiVo is rescheduling the suggestion even though it should be blocked by the startpadding that is added immediately after the deletion the first time. In any case, the current setup seems to work even though it may be a little heavy handed. I've been using 1.4.2-md5 for 8 weeks now without issue.

You could experiment with commenting out the DeleteSuggestion (but leaving in the rest of the related code, in particular the 'set dostartpadnow 1').

Tym

[petestrash]

I just noticed it has happened again, a suggestion was recorded in preference to end padding a season pass:

Tuesday 00:25:00 : endpad.tcl 1.4.2-md3 log file, log rotated
Tuesday 00:25:00 : Start padding set to 90 seconds
Tuesday 00:25:00 : End padding set to 1200 seconds
Tuesday 00:25:00 : Suggestions will not be padded if another suggestion immediately follows them
Tuesday 00:25:00 : Detected TiVo software version 3.0-01-1-000
Tuesday 00:25:00 : Suggestion quality change disabled
Tuesday 00:25:00 : Timezone 00:00
Tuesday 00:25:01 : Configuration options:-
Tuesday 00:25:01 : default: endpad 5 sugeq 0 sugqual -1 startpad 1.5
Tuesday 00:25:01 : channel Nine-WA validity 19:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1.5
Tuesday 00:25:01 : channel Nine-WA validity 22:00-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1.5
Tuesday 00:25:01 : channel Seven-WA validity 19:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1.5
Tuesday 00:25:01 : channel Seven-WA validity 22:00-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1.5
Tuesday 00:25:01 : channel Ten-WA validity 19:00-22:00 endpad 18 sugeq 0 sugqual -1 startpad 1.5
Tuesday 00:25:01 : channel Ten-WA validity 22:00-06:00 endpad 20 sugeq 0 sugqual -1 startpad 1.5
Sleeping, checking every minute for kill signal.... 
...Snip...
Tuesday 20:25:00 : Woken up
Tuesday 20:25:00 : Recording Surface on Ten-WA now
Tuesday 20:25:00 : Recording Scheduled End Time: 20:30
Tuesday 20:25:00 : Next recording is {The Ghost Whisperer} on Seven-WA (Suggestion) at 20:30
Tuesday 20:25:00 : Current recording is on Ten-WA and starts at 19:30 so use endpad 18
Tuesday 20:25:00 : Gap to next programme is 0 seconds
Tuesday 20:25:00 : Can't add end padding to Surface
Tuesday 20:25:00 : Next end padding setting due 21:25
Tuesday 20:25:00 : Not time to add start padding yet
Tuesday 20:25:00 : Next start padding setting due 20:27
Tuesday 20:25:00 : Next wake up will be 20:27
Sleeping, checking every minute for kill signal....

I'll load up endpad-1.4.2-md5 as tim suggested and see if the problems continue.

Peter

[snowrides]

HI All,

Newbie here. I'm having trouble getting endpad to start automatcially.
I'm running a UK series 1 tivo software version 2.5.5a
I'm also a little confused as some threads talk about a config file which overrides the rc script.

If I run the following command manually endpad runs OK, but I cant get it to run automatically.
/var/hack/endpad.tcl -s -2 -e 5 -sugqual 75

My /etc/rc.d/rc.sysinit.author is as follows:

# Call the Tivo Package Manager Startup Scripts
/etc/rc.d/rc.sysinit.tpm
/var/hack/endpad.tcl -s -2 -e 5 -sugqual 75 -auto >> /dev/null &
/var/hack/tivowebplus/tivoweb console

Any help would be much appreciated

thanks

[sanderton]

Are you intending to have minus two as the start padding?

Is TiVoWeb plus running OK - it might be that the call to run /etc/rc.d/rc.sysinit.tpm is not finishing properly and returning control to run the last two lines of this script.

[cwaring]

Originally Posted by snowrides

/var/hack/endpad.tcl -s -2 -e 5 -sugqual 75

Do I spy an extra (ie not-needed) minus sign there before the 2?

[snowrides]

Thanks fior the quick replies.
I've corrected the "-2" typo and still it wont start.
Tivoweb also doesnt start. I have to start it manually , so I guess your right the call for the run script is not finishing.

Any ideas how I can check it?

[tym]

Originally Posted by petestrash

I just noticed it has happened again, a suggestion was recorded in preference to end padding a season pass:

Tuesday 00:25:00 : Suggestions will not be padded if another suggestion immediately follows them

Taking another look at the code, it would appear this is a bug that occurs if you have sugeq option selected or if the suggestion is on the same channel. Possible fix (line 1254):

Old: if {$gap < $endpadding && $nselectiontype == 6 && $ncallsign != $ccallsign && $sugcancancelsug == 1} {
New: if {$gap < $endpadding && $nselectiontype == 6 && {{$ncallsign != $ccallsign && $sugcancancelsug == 1} || $cselectiontype != 6}} {

Tym

[Trinitron]

I've trawled through the thread but haven't found a mention of this quirk, that's happened two weeks running...

We have 2 Season passes set for Thursdays:
1900-1955 The Avengers BBC4
2000-2030 Bleak House BBC1

Endpad is perfectly ok until it wakes up at 1957 to add start padding (default 1.5 minutes). It has added 298 seconds to the first recording at 1950, making the end time 19:59:58. But at 19:57:30 it adds another 298 seconds to the revised end time and overlaps the start of the next programme. Tivo doesn't lose the second recording, just starts it 4 minutes late.

I'm using Sanderton's 1.4.0 version. I'll try one of the later version and hunt for programmes starting 5 minutes apart, but is there an explanation?

Sleeping, checking every minute for kill signal...............................
Thursday 19:27:31 : Woken up
Thursday 19:27:31 : Recording {The Avengers} on BBC4 now
Thursday 19:27:31 : Recording Scheduled End Time: 19:55
Thursday 19:27:31 : Next recording is {Bleak House} on BBC1NW at 20:00
Thursday 19:27:31 : Not time to add end padding yet
Thursday 19:27:31 : Next end padding setting due 19:50
Thursday 19:27:31 : Not time to add start padding yet
Thursday 19:27:31 : Next start padding setting due 19:57
Thursday 19:27:31 : Next wake up will be 19:50
Sleeping, checking every minute for kill signal........................
Thursday 19:50:00 : Woken up
Thursday 19:50:00 : Recording {The Avengers} on BBC4 now
Thursday 19:50:00 : Recording Scheduled End Time: 19:55
Thursday 19:50:00 : Next recording is {Bleak House} on BBC1NW at 20:00
Thursday 19:50:00 : Gap to next programme is 300 seconds
Thursday 19:50:00 : Added 298 seconds end padding to {The Avengers}
Thursday 19:50:00 : Next end padding setting due 20:25
Thursday 19:50:00 : Not time to add start padding yet
Thursday 19:50:00 : Next start padding setting due 19:57
Thursday 19:50:00 : Next wake up will be 19:57
Sleeping, checking every minute for kill signal.........
Thursday 19:57:30 : Woken up
Thursday 19:57:30 : Recording {The Avengers} on BBC4 now
Thursday 19:57:30 : Recording Scheduled End Time: 19:59
Thursday 19:57:30 : Next recording is {Bleak House} on BBC1NW at 20:00
Thursday 19:57:30 : Gap to next programme is 300 seconds
Thursday 19:57:30 : Added 298 seconds end padding to {The Avengers}
Thursday 19:57:30 : Next end padding setting due 20:25
Thursday 19:57:30 : Gap to previous recording is 2 seconds
Thursday 19:57:30 : Can't add start padding to {Bleak House}
Thursday 19:57:30 : Next start padding setting due 20:25
Thursday 19:57:30 : Next wake up will be 20:25
Sleeping, checking every minute for kill signal.............................
Thursday 20:25:00 : Woken up
Thursday 20:25:01 : Recording {Bleak House} on BBC1NW now
Thursday 20:25:01 : Recording Scheduled End Time: 20:30
Thursday 20:25:01 : Next recording is {Sensitive Skin} on BBC2 at 22:00
Thursday 20:25:01 : Gap to next programme is 5400 seconds
Thursday 20:25:01 : Added 600 seconds end padding to {Bleak House}
Thursday 20:25:01 : Next end padding setting due 22:25
Thursday 20:25:01 : Not time to add start padding yet
Thursday 20:25:01 : Next start padding setting due 21:57
Thursday 20:25:01 : Next wake up will be 20:55

[sanderton]

Later versions had some bug fixes; I can't remember if this was one but it rings a bell.

[Trinitron]

Ok, I've loaded the latest version and rebooted Tivo for good measure.

I'll try to record 2 progs 5 minutes apart and see what happens.

0025 BBC1 Strutting Our Stuff is scheduled to 0055
0100 BB4 The Late Edition is scheduled to 0130

Start padding is 1.5 mins, end padding 10 mins.

Off to bed now. See what Tivo says in the morning!

[Trinitron]

No good. Same error...

Friday 00:22:30 : Woken up
Friday 00:22:30 : No recording in progress
Friday 00:22:30 : Next recording is {Strutting Our Stuff} on BBC1NW at 00:25
Friday 00:22:30 : No end padding required:
Friday 00:22:30 : No recording in progress
Friday 00:22:30 : Next end padding setting due 00:50
Friday 00:22:30 : Added 90 seconds start padding to {Strutting Our Stuff} on BBC1NW
Friday 00:22:30 : Next start padding setting due 00:50
Friday 00:22:30 : Next wake up will be 00:50
Sleeping, checking every minute for kill signal.............................
Friday 00:50:00 : Woken up
Friday 00:50:00 : Recording {Strutting Our Stuff} on BBC1NW now
Friday 00:50:00 : Recording Scheduled End Time: 00:55
Friday 00:50:00 : Next recording is {The Late Edition} on BBC4 at 01:00
Friday 00:50:00 : Gap to next programme is 300 seconds
Friday 00:50:00 : Added 300 seconds end padding to {Strutting Our Stuff} on BBC1NW
Friday 00:50:00 : Next end padding setting due 01:25
Friday 00:50:00 : Not time to add start padding yet
Friday 00:50:00 : Next start padding setting due 00:57
Friday 00:50:00 : Next wake up will be 00:57
Sleeping, checking every minute for kill signal.........
Friday 00:57:30 : Woken up
Friday 00:57:30 : Recording {Strutting Our Stuff} on BBC1NW now
Friday 00:57:30 : Recording Scheduled End Time: 01:00
Friday 00:57:30 : Next recording is {The Late Edition} on BBC4 at 01:00
Friday 00:57:30 : Gap to next programme is 300 seconds
Friday 00:57:30 : Added 300 seconds end padding to {Strutting Our Stuff} on BBC1NW
Friday 00:57:30 : Next end padding setting due 01:25
Friday 00:57:30 : Gap to previous recording is 0 seconds
Friday 00:57:30 : Can't add start padding to {The Late Edition}
Friday 00:57:30 : Next start padding setting due 01:25
Friday 00:57:30 : Next wake up will be 01:25
Sleeping, checking every minute for kill signal.............................
Friday 01:25:00 : Woken up
Friday 01:25:01 : Recording {The Late Edition} on BBC4 now
Friday 01:25:01 : Recording Scheduled End Time: 01:30
Friday 01:25:01 : Next recording is {The Daily Show with Jon Stewart} on MORE4P1 (Suggestion) at 04:25
Friday 01:25:01 : Gap to next programme is 10500 seconds
Friday 01:25:01 : Added 600 seconds end padding to {The Late Edition} on BBC4
Friday 01:25:01 : Next end padding setting due 04:55
Friday 01:25:01 : Not time to add start padding yet
Friday 01:25:01 : Next start padding setting due 04:22
Friday 01:25:01 : Next wake up will be 01:55
Sleeping, checking every minute for kill signal...............................