home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
Input/Output Interfaces
MCE RC6 IR receivers shortcomings
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1182204" data-attributes="member: 141969"><p>Yes, that is exactly right. But that is not what the Microsoft driver is doing. Commands intended for other RC6 devices (such as my Sony amplifier) <em>do</em> affect WMC and MP (because the debounce processing performed by the Microsoft driver is incorrect). It is a subtle error, so perhaps it is not surprising that the authors of the Microsoft driver got it wrong.</p><p></p><p>The test case that I described in my GreenButton post reproduces the error every time (assuming that you have appropriate hardware). If you use that test case, and work through the two pseudo code samples that I gave, the subtle error should become apparent. (The test case and pseudo code provide a more precise demonstration of the error than trying to describe the error in words.)</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1182204, member: 141969"] Yes, that is exactly right. But that is not what the Microsoft driver is doing. Commands intended for other RC6 devices (such as my Sony amplifier) [i]do[/i] affect WMC and MP (because the debounce processing performed by the Microsoft driver is incorrect). It is a subtle error, so perhaps it is not surprising that the authors of the Microsoft driver got it wrong. The test case that I described in my GreenButton post reproduces the error every time (assuming that you have appropriate hardware). If you use that test case, and work through the two pseudo code samples that I gave, the subtle error should become apparent. (The test case and pseudo code provide a more precise demonstration of the error than trying to describe the error in words.) -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
Input/Output Interfaces
MCE RC6 IR receivers shortcomings
Contact us
RSS
Top
Bottom
