Runaway Recording IN PROGRESS!

[prpr]

As expected, nothing amiss here:

02/18 19:00:54 Event 17472:14139 4E:23 started 19:00:00 01:00:00 "Antiques Roadshow" "/m/WWE1" "/m/QU9K/02"
02/18 20:00:41 Event 17472:14140 4E:24 started 20:00:00 01:00:00 "New: Inside the Factory" "/m/11FD5" "/m/10BGN"
02/18 21:01:24 Event 17472:14141 4E:25 started 21:00:00 01:30:00 "Miners' Strike: A Frontline Story" "/m/11FDG" ""

02/18 19:00:57 Event  4287:14172 4F:25 started 19:00:00 01:00:00 "Antiques Roadshow" "/m/WWE1" "/m-QU9K/02"
02/18 20:00:42 Event  4287:14173 4F:26 started 20:00:00 01:00:00 "New: Inside the Factory" "/m/11FD5" "/m-10BGN"
02/18 21:01:24 Event  4287:14174 4F:27 started 21:00:00 01:30:00 "Miners' Strike: A Frontline Story" "/m/11FDG" ""

 

[antipodean]

Strange event today.
Recorded Antiques Roadshow but it didn't stop at end but continued to end of Inside the Factory - two hours instead of one but I didn't have to manually stop the recording

Hmm, I recorded it and it stopped correctly.
I'm using padding, not AR, if that makes a difference. It may have missed the AR stop (or more correctly the AR start for the next program) if you are using that.

 

[prpr]

I'm using padding, not AR, if that makes a difference.

Obviously it does, as padding just uses clock time rather than anything the broadcasters send.
There isn't an AR stop. It just stops because the next programme gets an AR start, and you can only have one active programme per service.

 

[MymsMan]

Obviously it does, as padding just uses clock time rather than anything the broadcasters send.
There isn't an AR stop. It just stops because the next programme gets an AR start, and you can only have one active programme per service.

I do use AR and @prpr's data indicates the breaks did occur at the expected time - so not obvious why recording didn't stop when expected

 

[Black Hole]

so not obvious why recording didn't stop when expected

Or, more to the point, why it managed to stop at all!

 

[MymsMan]

Or, more to the point, why it managed to stop at all!

When a recording is in progess a timer is set for 2 hours byond the scheduled end time which, I presume, is intended to catch long overunning programmes
(Issue nugget timers command while a scheduled recording is on progress)
But it still leaves a mystery:

1. Why did my recording stop after only one hour overunning? - it must have something to do with he other recordings scheduled to start then
2. Why doesn't the backstop timer stop other runaways?

 

[antipodean]

Or, more to the point, why it managed to stop at all!

Well, as I suggested in my post it stopped at the next AR mark. It wasn't actually a runaway program, it just missed the AR mark at the start of the program following Antiques Roadshow and instead stopped on the next AR mark.

 

[prpr]

AR marks, as you call them, are transmitted continuously. They don't just get sent once at the start of a programme.

 

[Black Hole]

They don't just get sent once at the start of a programme.

If that were the case we would expect many more failed recordings!