It seems clear that there were process priorities involved. Unless you suspect low battery, bad aim, or some other issue regarding the comms between remote and DVR, I'm not sure what else it could be.
The DVR works much like multitasking in a PC does, and certain things have priority over others. True, user input should probably have a higher priority than, say, guide info indexing, but it is still basically microprocessor-based, and things can get sluggish, especially if a higher-priority process becomes bogged down. One example is the DVRs typical poor recovery from rain fade, where 771 errors continue hours after a storm passes and things stay very sluggish. Not surprisingly, a reboot usually fixes both issues.
The DVR works much like multitasking in a PC does, and certain things have priority over others. True, user input should probably have a higher priority than, say, guide info indexing, but it is still basically microprocessor-based, and things can get sluggish, especially if a higher-priority process becomes bogged down. One example is the DVRs typical poor recovery from rain fade, where 771 errors continue hours after a storm passes and things stay very sluggish. Not surprisingly, a reboot usually fixes both issues.
