Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1182133" data-attributes="member: 141969">I believe that there are two problems here:(1) Most universal remote controls do not emulate separate remotes correctly (I say &quot;most&quot; because so far I have found only one brand that works correctly, namely Logitech Harmony).&nbsp; When a universal remote is setup to operate two or more devices that use toggle codes, the remote needs the maintain a separate toggle flag for each device.&nbsp; The Logitechs presumably do this (because they work correctly).&nbsp; Other universal remotes (such as those made by One-for-All or Universal Remote) maintain a single toggle flag that is then used for all devices.&nbsp; As a result, those universal remotes sometimes send signals with the wrong setting for the toggle flag.This is easily demonstrated when the VOLUME UP/DOWN and MUTE buttons are setup to control an audio amplifier that uses toggle codes, while the remaining buttons are setup to control WMC or MP.&nbsp; Using the universal remote causes the problem to occur, whereas using the separate remotes avoids the problem occurring (so the universal remote is not correctly emulating the separate remotes).(2) The Microsoft driver does not implement debounce processing correctly.&nbsp; In the post that I referenced above I included some pseudo code for what I think the Microsoft driver has implemented, and what I think it should have implemented (there is one line that is different!).Note that the problem of button-presses being ignored occurs only when both factors are present in a user's system.&nbsp; If only one factor is present, no problem is apparent.&nbsp; I suspect that this is why most users do not encounter this problem.-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1182133, member: 141969"] I believe that there are [B]two[/B] problems here: (1) Most universal remote controls do not emulate separate remotes correctly (I say "most" because so far I have found only one brand that works correctly, namely Logitech Harmony). When a universal remote is setup to operate two or more devices that use toggle codes, the remote needs the maintain [I]a separate toggle flag for each device[/I]. The Logitechs presumably do this (because they work correctly). Other universal remotes (such as those made by One-for-All or Universal Remote) maintain [I]a single toggle flag that is then used for all devices[/I]. As a result, those universal remotes sometimes send signals with the wrong setting for the toggle flag. This is easily demonstrated when the VOLUME UP/DOWN and MUTE buttons are setup to control an audio amplifier that uses toggle codes, while the remaining buttons are setup to control WMC or MP. Using the universal remote causes the problem to occur, whereas using the [I]separate remotes[/I] avoids the problem occurring (so the universal remote is not correctly emulating the separate remotes). (2) The Microsoft driver does not implement debounce processing correctly. In the post that I referenced above I included some pseudo code for what I think the Microsoft driver has implemented, and what I think it [I]should[/I] have implemented (there is one line that is different!). Note that the problem of button-presses being ignored occurs only when [I]both[/I] factors are present in a user's system. If only one factor is present, no problem is apparent. I suspect that this is why most users do not encounter this problem. -- from CyberSimian in the UK [/QUOTE]

Verification