Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1182329" data-attributes="member: 82144">So the implication of this is either:<ol>
<li data-xf-list-type="ol">Harmony remote and receiver processing is correct; One-for-All and other universal remotes are not manipulating the toggle bit(s) correctly. OR...</li>
<li data-xf-list-type="ol">One-for-All and other universal remote processing is correct; receiver processing is wrong... but so is the Harmony remote, because a correctly implemented remote control should give the same [erroneous] result.</li>
</ol>The first option seems more likely to me.Not necessarily. The result depends on how the amp receiver does its processing.The clear implication from the change in behaviour is that disabling de-bounce processing means that the receiver will ignore the toggle bit state. With that change, commands that would otherwise have been ignored because the toggle bit hadn't changed would now be actioned. That's the source of the spurious actions, and the reason why step 3 produces an action.To me this is further evidence that the One-for-All remote is not tracking and manipulating the RC-6 and MS RC-6 toggle bits correctly. It's just so easy for the remote to get it wrong given MS's non-standard RC-6 toggle bit implementation.IRSS is fairly easy.1. Install the latest version attached to the first post here:<a href="https://forum.team-mediaportal.com/threads/irss-1-5-0-110-mp1-6-and-newer-unoficial-testing-version-no-support.119847/" target="_blank">https://forum.team-mediaportal.com/threads/irss-1-5-0-110-mp1-6-and-newer-unoficial-testing-version-no-support.119847/</a>During installation, make sure you tick the option to install the MP Control plugin.2. Open MediaPortal Configuration.3. Go the &quot;remotes &amp; input devices&quot; section and ensure all handlers are disabled.4. Go to the &quot;plugins&quot; section and enable the MP Control plugin.5. Close MediaPortal Configuration.6. Open IRSS Input Service configuration.7. Click &quot;advanced&quot; up the top.8. Ensure log verbosity is set to debug and click OK.9. Find &quot;Microsoft MCE&quot; in the &quot;device plugins&quot; list and ensure &quot;receive&quot; is ticked.10. Up the top, click &quot;stop&quot; then &quot;start&quot; to restart the service and apply the changes.Now you should be able to reproduce the problem.IRSS log files can be found in c:\ProgramData\IR Server Suite\Logs.</blockquote>

[QUOTE="mm1352000, post: 1182329, member: 82144"] So the implication of this is either: [LIST=1] [*]Harmony remote and receiver processing is correct; One-for-All and other universal remotes are not manipulating the toggle bit(s) correctly. OR... [*]One-for-All and other universal remote processing is correct; receiver processing is wrong... [B]but so is the Harmony remote[/B], because a correctly implemented remote control should give the same [erroneous] result. [/LIST] The first option seems more likely to me. Not necessarily. The result depends on how the amp receiver does its processing. The clear implication from the change in behaviour is that disabling de-bounce processing means that the receiver will ignore the toggle bit state. With that change, commands that would otherwise have been ignored because the toggle bit hadn't changed would now be actioned. That's the source of the spurious actions, and the reason why step 3 produces an action. To me this is further evidence that the One-for-All remote is not tracking and manipulating the RC-6 and MS RC-6 toggle bits correctly. It's just so easy for the remote to get it wrong given MS's non-standard RC-6 toggle bit implementation. IRSS is fairly easy. 1. Install the latest version attached to the first post here: [URL]https://forum.team-mediaportal.com/threads/irss-1-5-0-110-mp1-6-and-newer-unoficial-testing-version-no-support.119847/[/URL] During installation, make sure you tick the option to install the MP Control plugin. 2. Open MediaPortal Configuration. 3. Go the "remotes & input devices" section and ensure all handlers are disabled. 4. Go to the "plugins" section and enable the MP Control plugin. 5. Close MediaPortal Configuration. 6. Open IRSS Input Service configuration. 7. Click "advanced" up the top. 8. Ensure log verbosity is set to debug and click OK. 9. Find "Microsoft MCE" in the "device plugins" list and ensure "receive" is ticked. 10. Up the top, click "stop" then "start" to restart the service and apply the changes. Now you should be able to reproduce the problem. IRSS log files can be found in c:\[B]ProgramData[/B]\IR Server Suite\Logs. [/QUOTE]

Verification