hairy_mutley
Active Member
I have my redring set to show clock and elapsed time during playback.
Last night I noticed that the time being displayed was wrong (apparently GMT) although the on-screen time was being shown correctly.
About to post this morning, and thought that I should double-check... the problem has gone, the time is correct.
So why different last night? Well, I had been decorating yesterday, so the PVR had been completely off (no mains supply) for most of the day.
So, as an experiment, I turned the box off (at rear power switch, long enough for the redring to go out) and then turned it back on.
Sure enough, the problem is back; on screen time is correct, but redring time is GMT.
Interestingly, I turned if to standby, came and wrote a little more, went back and turned it on again, and the problem has now gone away again.
Last night it was wrong the whole time it was on (over an hour).
So I presume that it must be removing the power that causes the problem and on -> standby -> on that fixes it.
Well, at least that explains why, it hasn't been observed and reported before, and it is no big deal anyway since it corrects itself, but interesting nevertheless.
Last night I noticed that the time being displayed was wrong (apparently GMT) although the on-screen time was being shown correctly.
About to post this morning, and thought that I should double-check... the problem has gone, the time is correct.
So why different last night? Well, I had been decorating yesterday, so the PVR had been completely off (no mains supply) for most of the day.
So, as an experiment, I turned the box off (at rear power switch, long enough for the redring to go out) and then turned it back on.
Sure enough, the problem is back; on screen time is correct, but redring time is GMT.
Interestingly, I turned if to standby, came and wrote a little more, went back and turned it on again, and the problem has now gone away again.
Last night it was wrong the whole time it was on (over an hour).
So I presume that it must be removing the power that causes the problem and on -> standby -> on that fixes it.
Well, at least that explains why, it hasn't been observed and reported before, and it is no big deal anyway since it corrects itself, but interesting nevertheless.