Reply to thread

Message: <blockquote data-quote="CyberSimian" data-source="post: 1182257" data-attributes="member: 141969">Agreed.  (Apologies to the thread starter for this diversion.)  Could someone who has the necessary authorisation please move all of the relevent posts to a new thread?  Thank you.I first looked at this problem back in 2011 (when I was using WMC), so I am trying to remember the reasons why I came to the conclusions that I did.  The crux of the test case is this sequence of button presses:(1) Press GUIDE button (sends signal for WMC/MP).(2) Press VOLUME_UP button (sends signal for Sony amplifier).(3) Press GUIDE button (sends signal for WMC/MP).This is what happens:(A) If the individual device-specific remote controls are used, this sequence works correctly.(B) If a Harmony universal remote control is used, this sequence works correctly.(C) If a One-for-All (or other) universal remote control is used, this sequence does not work correctly; action (3) is ignored.Comparing (A) with (C) indicates that the One-for-All universal remote control is not correctly emulating the individual device-specific remote controls.  This ultimately lead to my conclusions about the toggle flag.However, one can invert the test case, and perform this sequence of button presses:(1) Press VOLUME_UP button (sends signal for Sony amplifier).(2) Press GUIDE button (sends signal for WMC/MP).(3) Press VOLUME_UP button (sends signal for Sony amplifier).If the error resides solely in the remote control, action (3) would again be ignored.  But it is not.  With my Sony amplifier, action (3) is executed normally.  This result lead me to conclude that there is an error in the Microsoft driver (because the corresponding microcode in the Sony amplifier does not exhibit the same problem).The final piece of the puzzle was the effect of changing the Windows registry setting to disable debounce processing.  With debounce disabled, action (3) in the original test sequence was now executed correctly when using the One-for-All universal remote control.  However, the side effect was the introduction of spurious actions due to contact bounce in the remote.  Example: pressing and releasing the DOWN button when in the EPG would cause the focus to move down two or three lines; with debounce enabled, the focus moves down one line only.Yes, I still have all of the relevant hardware, and can reproduce the error on demand.  However, I have not so far ventured into the world of IRSS, so it might take me a while to figure out how to set things up. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite26" alt=":unsure:" title="Unsure    :unsure:" loading="lazy" data-shortname=":unsure:" />Finally, let me re-iterate that I have not seen any source code for the Microsoft driver, or looked at data traces for the IR signalling, so my conclusions are based on the tests that I have performed, and the outcomes resulting.  My hypothesis is (so far) consistent with the test results <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite6" alt=":cool:" title="Cool    :cool:" loading="lazy" data-shortname=":cool:" />, but that does not mean that my hypothesis is correct. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin    :D" loading="lazy" data-shortname=":D" />-- from CyberSimian in the UK</blockquote>

Verification