Is this a known?:
Last night "Heartbeat" had just started, about 19:02 and I pressed "record". I then went to the EPG (I think I did it this way round) and clicked on "Midsomer" due to start 20:00. I have auto padding on, on software .15. It duly showed the red reservation icon. I later watched Heartbeat on chase play and then noticed, as I deleted it, that "Midsomer" was not recording, even though it was well past 20:00. I think something similar happened the other day when I set an "on the fly" recording going and I lost a scheduled one.

This must be a bug James as it has happened to me a couple of times. I recorded all episodes of Grand Designs when it was on and missed recordings on two occasions when doing an instant record of the Bill before hand.

After the first time I didn't know what had happened. After the second I suspected the cause and never do an instant record before an important scheduled event.

In my case, I didn't do chase play (rarely do).

As you, I am on v15 as v21 slowed the remote response times too much and didn't allow for auto-padding with AR / Series link.

Thanks for the confirmation that it happens! Do you know if they know about it or has it been reported on here? The search engine isn't sophisticated enough to try and pin it down.

I've been to .21 twice and come back to .15. The slowing down in remote response was dreadful and until the broadcasters and Humax get AR and SL working properly without missing bits of starts and endings then I prefer to just use AP.

This limitation is mentioned in the releases notes for V8 of the software.

Thanks, Barry. I've now looked it up. One would think that they might have tried to resolve this one - at least now I know. I've had this machine for ages and I've only just discovered this limitation!

I stumbled across what appears to be this same problem (although I didn't know it was a known issue until I read this thread just now) a day or so after I acquired my 9200 about 3 weeks ago.

I have a 9200TB supplied with v21 software.

From the limited tests I have done so far it appears that contrary to what is said in the V8 release notes the problem is not confined to conflict between scheduled recordings with added padding and instant recording on the same channel but is also triggered using Accurate Recording and with instant recordings on other channels when the scheduled recording starts early as is normally the case with ITV programmes (ITV usually add the advert break from the previous programme to the start of recordings). For example, I set a scheduled recording to start at 11:00 am on ITV2 and started an instant recording on Five to run until 11.30 and a second instant recording on BBC1 which was scheduled to finish at 11:00. The scheduled recording on ITV2 failed completely. At the time I was un-aware of the issue with instant recordings and was really testing the effect of short conflicts due to programmes starting early and so was using instant record to establish the scenario of a early start programme overlapping two current recordings by a few minutes. I was expecting the scheduled recording to start when the a tuner became available on the completion of the instant record set on BBC1, resulting in a slightly shortened ITV2 recording, which is what happens when all the test programmes are scheduled programmes. I have yet to test to see if I get the same results if I repeated the above with just one instant recording on a channel other than the scheduled programme channel.

Colin

Colin, I have a suspicion that ANY instant recording in operation will kill ALL scheduled recordings due to start in that time. I will do some tests sometime but if you do yours first please post them on here.

As an aside to this I believe that there is another phenomenon connected to the inability of the system to do a scheduled recording if it has missed the start. If you have AP of (say) -2 minutes and you programme a recording for 20:00 and actually do it at 19:59 then the red icon appears in the EPG but it doesn't record.

That's correct reservation start time is in the past so recording can't start.

But surely in the real world you wouldn’t do this, as you’re so close to the programme start time you would press the Record button and do an instant record.

But then doing an instant record would prevent the next programme being recorded (if scheduled)!
and the instant record would be set for 19:59 - 20:00 unless you extend it.

OK maybe I should have written "press the Record button and do an instant record" when the programme starts. There has to be an element of common sense here.

But I wanted to watch something else which started at 20:00 - hence the problem.

My old VCR would start a recording if you set a start time before real time, I'm not sure either that my 8000 wouldn't do likewise - I must check, I've still got it hooked up for the odd time I need three recordings!

Don't think my VCR does, it comes up with a message saying something like 'the start time has passed'. To be honest I've selected from the EPG just before a programme start (like you suggested in your post above) but I'm using AR/SL and the programme hadn't started so it worked fine.

I have done some further tests. I have only tested with Accurate Recording (On Time) enabled so have not tested for possible differences if Auto Padding is used. On all the tests that I have done the conflict with instant recordings have all been because of the early starts (relative to scheduled times) of ITV programmes.

My tests show that with just one other channel set to instant record on a different channel to the schedule recording being tested and still recording when a scheduled recording receives the start signal (Now/Next status change) this does not cause a failure of the scheduled recording which starts without delay at the time the Now/Next status changes.

I confirmed the accepted failure mode with the similar scenario to the above but with the instant recording on the same channel as the sheduled recording. I also confirmed my earlier finding that instant recordings set on two channels other than the scheduled recording does cause a failure.

I have not considered any variations in the above results depending on whether the channels used for instant recordings were on the same or different MUXs fron the scheduled recording.

Colin