A few posts back, I mentioned that I installed Media Center 2005 on my old P4 1.8GHz computer. Since I’ve now fallen in love with it, I figured it was time to assimilate its remote control functionality into my 2-year-old Marantz RC9200 universal remote. As a side note, my wife was gracious enough to give me the RC9200 as a gift after I had been salivating over it for months. Although it’s a couple years old, it has been a fantastic remote control. It is truly universal in that it can “learn” by recording other remote infra-red (IR) signals, it can broadcast radio frequency (RF) signals (to control your X10 room lighting, for example), and it has custom software that allows you to completely configure everything, including the look and feel of the screen. It’s not for the faint-of-heart, but if you like programming, you have a bit of creativity, and you are a patient person, you can work wonders. Here are a few of my screens:
As usual, I plugged the RC9200 into my computer and started recording IR commands from the Media Center remote. The process went smoothly, and I was able to successfully record the codes for each key. I configured the macros I planned on using and hooked up my virtual touch-screen buttons to their appropriate IR counterparts. After downloading the new configuration to my universal remote, I carried it downstairs for its first test. Initially, it seemed as if everything was working just fine. However, after a few short moments, I quickly realized that something was amiss. The first press of my down arrow button worked properly, but it wouldn’t accept a second press…that is, until I pressed something else first. And the other buttons all behaved in a similar fashion. Very strange.
So, I turned to the remote control experts at Remote Central and The Green Button. A casual search of their forums turned up a couple of posts (here and here) about similar behavior with other learning remotes. Turns out that the Media Center remote has two sets of codes that alternate with each button press (apparently using a bit flipping technique). This method is used so that a single key press isn’t accidentally received twice by the computer and is referred to as debounce. From what I’ve been able to find on the internet, it seems that IR codes can inadvertently be received more than once by reflecting off surfaces or being interfered with by displays, lamps, etc. How interesting. To avoid this effect, the Media Center remote sends the first IR command for down arrow, and when the user presses the button again, it sends a second IR command for down arrow. If a different button is pressed in between these two presses, it doesn’t matter, because clearly, it’s not a key “bounce” in that scenario. It’s interesting to note that this is exactly the behavior I was noticing.
There are a few suggested options to deal with this. First, you can follow every normal command with a “do nothing” command. Unfortunately, it’s often difficult to identify a do nothing command on the remote. For example, if the clear command did nothing useful on the remote, you could conceptually program the down arrow functionality as: down arrow + clear. By doing this, you’ve sent a second real command to the receiver, and your next down arrow command will be considered a second press. Not pretty, but a functional hack. The second option is to literally duplicate the user interface panels and switch between them with each press of a key. Of course, you’d have two panels, each with their own set of IR codes. Although it sounds doable, it’s definitely more work, and it sounds like even more of a hack. And I’m no fan of hacks.
The third option is to simply disable the debounce feature of Media Center and use a single set of IR codes. I don’t know why this isn’t exposed in the settings screens in Media Center, because it’s something that anyone with a learning remote will run into. To disable the debounce feature, you need to modify a single registry key. Standard registry editing rules apply…make sure you create a backup, know what you’re doing, etc., etc. The key is called EnableDebounce, and from what I’ve read in various posts, it’s found in the following locations:
For Media Center 2004: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\idIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da
For Media Center 2005: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da
So, fire up RegEdit, navigate to the appropriate key, and change the EnableDebounce value from 1 (its default setting) to 0. Note that you’ll have to reboot your system for this change to take effect. After this modification, my universal remote now works like a charm, and I’ve added one more remote to the remote control graveyard behind my big screen TV.