I get a message at around 85 saying the max # of timers has been reached. With memory cost so low you would think they allow a lot. While on the subject how do you back-up timers to the remote on a 722k?
getstuff4less said:I get a message at around 85 saying the max # of timers has been reached. With memory cost so low you would think they allow a lot. While on the subject how do you back-up timers to the remote on a 722k?
I believe it's a 96-timer limit. Hold zero for backing up.
Correct 96 timers or 576 events which ever is reached first. ALL events count even skipped events so it is easy to reach the event limit with just a few timers for shows that air multiple times a day.
It most likely could be fixed w/ a s/w update. But for some reason they have never changed it from where it is now.Nobody really addressed why timer limits are so low. I would think this only takes up a few MB. I wonder if a software update can fix the issue.
It is much more likely that the limit is there for performance considerations rather than memory use.
The memory needed to store 96 timers and 576 events shouldn't be much more than a few hundred kilobytes, I'd be surprised if it's more than one megabyte.
When you do get to 96 times or 576 events, you'll notice that skipping events and such is much slower than if you only have a handful.
I would guess that the limit is merely there to control possible complaints about slowness.