If everyone had this problem, there would be HUNDREDS or THOUSANDS of posts about this. My wife can't stand it, so it's NOT something subtle.
And why would it be "more severe" for me?
If 1/3 of all presses are missed, isn't that a massive problem?
It means either 1) there's a hw design problem (which I doubt since it doesn't happen for everyone), 2) a fw problem (possibly not caching presses? maybe remote not connected to interrupts?, or 3) a unit-specific problem which IS possible because both of these units were from the same store.[/I]
The variations in the problem are legendary, from missed input to unresponsive, to simply unack'd.. It is more severe at one time than another, not forever on one machine. Rebooting will often snap things up for a while. The number of variables involved is large, so only a certain combination will produce a specific symptom, and that symptom changes with usage patterns and housekeeping demands. The demands on the processor are all over the map, not stable at all.
Very few people report never having problems with remote response at one time or another. Given my own experience with 3 different non-24 dvrs for nearly four years, I don't readily accept "I never have seen that", but it is remotely possible that the many number of variables influenced by their usage patter has just not triggered the problem. Overall, I'm skeptical about the "never happened here" response to such a widespread problem (with the non-24 series). The 24 series are less vulnerable, but not immune. Until the code is better optimized, even the 24 series can be affected (see all the posts, they are numerous.
So in the case of the 24 series they are merely "numerous", while in the non-24 series they are ubiquitous.
HR44-700, WD20EURX 2 TB eSATA/ThermalTake Max 5 Enclosure
HR24-200, WD20EVDS 2 TB eSATA/ThermalTake Dock
HR24-200, H21-200. Samsung UN60C6400 60" LED/LCD
DirecTV since 1995