[theHermit]

v1.06

On Sunday night I had scheduled Big Brother (Ch4) and Dawn of the Dead (Ch4, on straight after Big Brother).

We were watching the recording of BB via chase play, and I noticed (in good time, thankfully) that Dawn of the Dead had not started recording! I manually stopped BB and manually started to record Dawn of the Dead, so didn't miss it.

This is not the first time that this has happened...

Has anyone else noticed this before and has this been fixed in v1.10? I'm reluctant to upgrade to the latest version until the bugs that I've read about on this forum have been resolved, and I have more confidence in this version (or a later OTA version)...

Thanks.

[Max Demian]

It's claimed that this can happen when you set the second scheduled recording before the first (when the recordings are consecutive on the same channel).

[woolfynorm]

Originally Posted by Max Demian

It's claimed that this can happen when you set the second scheduled recording before the first (when the recordings are consecutive on the same channel).

This bug was fixed in 1.0.0.8.

Update to 1.0.0.10 the extra features are worth it, and 50 timers!

Woolfynorm

[ico.]

Originally Posted by woolfynorm

This bug was fixed in 1.0.0.8.

Update to 1.0.0.10 the extra features are worth it, and 50 timers!

Woolfynorm

Would do if they broadcast it OTA, another bug I've still got.

[Martin Liddle]

I saw something a bit similar last night. Was watching East Enders (which was set to record with a weekly timer) via chase play (about 20 minutes behind real time). The next program on BBC1 (Holby City?) was also set to record via a weekly timer but realised at about 20:15 that it wasn't recording. Checked and it was still in the list of scheduled recordings and nothing else recording at the same time. Checked that PIP was still available and that free disk space was available. This is with 1.00.10 which was upgraded a few weeks ago and follwed by a reset to default settings.

[BBinBucks]

Isn't this to do with autopadding?

I thought that if you set two consecutive programmes to record on the same channel (or possibly even the same mux), the Hummy ignores autopadding and 'reserves' a single tuner for the job. But when it comes to actually record, it finds that the tuner is still in use, so gives up. And isn't it a specific .10 problem, because earlier versions don't have autopadding?

Whether I'm right or wrong on this, I always manually adjust two consecutive programmes to record as a single unit, then split them afterwards if necessary, tho' I don't normally bother.

Now you're going to tell me that you don't have autopadding set!

[ChrisHay]

Was recording Waking The Dead on Monday due to finish at 10pm,with 3 minute autopadding at the end.
Two programmes were meant to record from 10pm onwards with 2 minutes autopadding at the beginning.
Neither of the 10pm programmes started to record so manual intervention was required.
I have been using version .10 since it was available and this is the first time this problem has occured.

[Martin Liddle]

Originally Posted by BBinBucks

Isn't this to do with autopadding?

I thought that if you set two consecutive programmes to record on the same channel (or possibly even the same mux), the Hummy ignores autopadding and 'reserves' a single tuner for the job. But when it comes to actually record, it finds that the tuner is still in use, so gives up. And isn't it a specific .10 problem, because earlier versions don't have autopadding?

I do have padding set for 3 minutes at the end of recordings. I think padding was introduced at 1.00.06 but there have been some subtle changes between versions. I think what the documentation implies is that padding should be dropped in the situation I describe. It does seem to have been a one off occurrence but given that both scheduled recordings were set as weekly it will be interesting to see whether or not it works next week.