Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1182838" data-attributes="member: 82144">Yeah, correct - what the OFA remote is doing doesn't make much sense to me.As far as I know SIRC (the Sony protocol) does not have a toggle flag. This is the information I'm going by:<a href="http://www.sbprojects.com/knowledge/ir/sirc.php" target="_blank">http://www.sbprojects.com/knowledge/ir/sirc.php</a><a href="http://users.telenet.be/davshomepage/sony.htm" target="_blank">http://users.telenet.be/davshomepage/sony.htm</a>I guess a SIRC receiver detects a single continuous button press using this property:In other words: if the space between commands is longer than 40 ms, it's the equivalent of flipping the toggle bit.LOL. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />It's because IRSS's debounce processing is across all protocols.In code terms, this is it:[code]if (!firstPress &amp;&amp; _lastRemoteButtonCodeType == codeType &amp;&amp; _lastRemoteButtonKeyCode == keyCode){&nbsp; // process the button press}[/code]In layman's terms...Debounce processing only applies for consecutive button presses that came in via a single protocol. In other words, IRSS doesn't ignore the second GUIDE button press (3) because it was preceded by a SIRC command [instead of an MS RC-6 command]. The SIRC command breaks/resets the debounce processor. If IRSS didn't receive or understand the SIRC command (ie. if your amp happened to be located on the opposite side of the room from the PC's MCE-compatible receiver, or IRSS didn't support SIRC), you'd experience exactly the same symptoms as you have with the &quot;MS driver&quot;.</blockquote>

[QUOTE="mm1352000, post: 1182838, member: 82144"] Yeah, correct - what the OFA remote is doing doesn't make much sense to me. As far as I know SIRC (the Sony protocol) does not have a toggle flag. This is the information I'm going by: [URL]http://www.sbprojects.com/knowledge/ir/sirc.php[/URL] [URL]http://users.telenet.be/davshomepage/sony.htm[/URL] I guess a SIRC receiver detects a single continuous button press using this property: In other words: if the space between commands is longer than 40 ms, it's the equivalent of flipping the toggle bit. LOL. :) It's because IRSS's debounce processing is across all protocols. In code terms, this is it: [code]if (!firstPress && _lastRemoteButtonCodeType == codeType && _lastRemoteButtonKeyCode == keyCode) { // process the button press } [/code] In layman's terms... Debounce processing only applies for consecutive button presses [I]that came in via a single protocol[/I]. In other words, IRSS doesn't ignore the second GUIDE button press (3) because it was preceded by a SIRC command [instead of an MS RC-6 command]. The SIRC command breaks/resets the debounce processor.[I] [/I]If IRSS didn't receive or understand the SIRC command (ie. if your amp happened to be located on the opposite side of the room from the PC's MCE-compatible receiver, or IRSS didn't support SIRC), you'd experience exactly the same symptoms as you have with the "MS driver". [/QUOTE]

Verification