I have noticed an oddity and I am wondering if it is normal and whether it can be worked round at all.
I had 2 recordings scheduled for Sunday evening - one from 8-9pm and one from 9-10pm (both series recordings). I then set a recording (one off - single program) for something else on the following Wednesday evening. I then didn't think anything of it until I looked on Monday and discovered that it had recorded all 3 already. The problem is that it moved the Wed program to an alternate broadcast on Sunday which went from something-9pm. This meant that when the 9-10pm program started the AR had not stopped the other 2 recordings and so it missed the start of the program and gave the 'did not track as already recording 2 things - do you want to play it anyway' type message.
It didn't miss much, but the recording started a couple of minutes into the actual program.
I'm used to a system where it would automatically use a later showing of one of the programs to avoid the potential truncation of one. In this case it worked against me and created the truncation by moving a recording to a different time than I set even though there were no other recordings scheduled on the Wed. I really don't care if it records something a few days later, but I do care about missing the start of a program (though that is better than the end of a program).
Is that normal behaviour? Is there any way I could have done things differently to avoid it?
I presume if I had padding on the later recording or both the earlier ones then it would not have because it would have been a true 3 way clash - but I would rather use AR on channels I know I can rely on it (and I haven't found any I can't rely on so far).
I had 2 recordings scheduled for Sunday evening - one from 8-9pm and one from 9-10pm (both series recordings). I then set a recording (one off - single program) for something else on the following Wednesday evening. I then didn't think anything of it until I looked on Monday and discovered that it had recorded all 3 already. The problem is that it moved the Wed program to an alternate broadcast on Sunday which went from something-9pm. This meant that when the 9-10pm program started the AR had not stopped the other 2 recordings and so it missed the start of the program and gave the 'did not track as already recording 2 things - do you want to play it anyway' type message.
It didn't miss much, but the recording started a couple of minutes into the actual program.
I'm used to a system where it would automatically use a later showing of one of the programs to avoid the potential truncation of one. In this case it worked against me and created the truncation by moving a recording to a different time than I set even though there were no other recordings scheduled on the Wed. I really don't care if it records something a few days later, but I do care about missing the start of a program (though that is better than the end of a program).
Is that normal behaviour? Is there any way I could have done things differently to avoid it?
I presume if I had padding on the later recording or both the earlier ones then it would not have because it would have been a true 3 way clash - but I would rather use AR on channels I know I can rely on it (and I haven't found any I can't rely on so far).