Originally Posted by creddish:
“Interesting stuff. You have obviously analysed this in more detail than I have. You have what I would describe as a large number of Timers set so I would expect slow response to start building up over a one day period after re-booting (that would be the case on my T825). Presumably you are watching and deleting recordings at a similar rate to that at which new recordings are being made? Would you care to measure after 3 days of use before re-booting how long it takes to access the Timers list, how long it takes to set a new Series Timer event and how long it takes to skip 24 hours in the EPG after pressing the Blue button. I find these actions produce the most significant delays when it starts slowing down.”
Re glitches
Last night it was recording Gardeners' World and QI back to back, while we watched Mock The Week. I have to fast forward over Jack Whitehall's hair as it disturbs me

, so we were putting a lot of strain on the box. We got 2x Category 3 glitches and 1x category 2 glitches in GW. Bad, but that's a worst case scenario I guess. We rarely do so much FF. Haven't checked QI yet.
Re speed of response
timers
- lots of dross, eg I series linked local news so we can watch the weather. That's 9 timers on its own, 1x bulletin on weekdays + 2 on each weekend day. We rarely watch them.
- lots of repeats. For example Jamie's 30 Minute Meals seems to be about 8 timers even though it's only on a few nights a week. V3.4 is supposed to sort this, I will try resetting the J30MM series timer
- "hangover" timers where the series has ended but the timer remains, for example Mock The Week. I guess the BBC never told the box it was the last episode in the series
- The rest is stuff which tends to build up and get deleted when the disc gets full. Our principle is record everything that looks vaguely interesting, then delete it when it turns out not to be! We probably only watch half the stuff we record
I will have a timer clearout now I have V3.4. Something Futaura suggested.
I wonder if more timers = more glitches. The box obviously has to work hard, presumably comparing the broadcast Now & Next table with the internal Timers table. I would guess the CPU load to do this goes up linearly with number of timers, but maybe it's worse than that. You say it affects EPG speed, maybe it affects glitching too when the CPU overloads.
I will do some more scientific checks, but I have noted that if the box has not been rebooted recently, in the EPG
- setting a series timer can take up to 30 seconds, worst for programmes where there are about 10 instances in a week (for example Quest often does 2 episodes a day for 5 days). For a normal once-a-week series, usually 5-10 secs
- sometimes it doesn't detect key presses on the remote, you have to press twice
- skipping 24 hours is never onerous, perhaps it takes a few seconds, ditto accessing the Timers list
The EPG definitely slows down, but it never gets as slow as my Sagem which is astonishingly slow, like using a spreadsheet back in the 1980s. You have to count key presses "do 8 presses along and 2 down, wait 10 seconds for the cursor to move, then see where we are, repeat until you find the right programme". The Sagem
always takes 30 seconds to set a series timer. If it finds a conflict smoke comes out the back and it can take up to a minute to resolve it.
I did note last night that with V3.4 and a fresh reboot the Library list was quite slow. Pressing Play resulted in a significant delay before playback started, similarly deleting a recording. Worrying. But no sign of that this morning, it's all fast.
So it looks like V3.4 hasn't significantly affected glitching which is disappointing but not surprising. I guess Vestel isn't monkeying with the MPEG firmware too much for fear of regressions creeping in.
@ OP outrageous thread hijack - sorry!