Reply to thread

Message

<blockquote data-quote="zoee" data-source="post: 174945" data-attributes="member: 54780">I tried removing the replacement driver and reverting to the original eHome driver, this didn't change anything. From playing about some more with the timing it appears that by lowering the repeat delay I get more and more doubles. Even triples when I have it set very low. Either I have misunderstood the how the timings work or this is the issue. From how I understand it the repeat delay shouldn't make any difference to how commands are accepted until a button has been held long enough to cross the held delay. Since it clearly is affecting it I wander if it can't be an issue in the algorithm that calculates if a button is being held and for how long. I don't know how your software calculates this but from my programming experience thats where I suspect something might be amiss. I'll try to think of a way of trying the remote out without the IR Server and see if the problem persists.</blockquote>

[QUOTE="zoee, post: 174945, member: 54780"] I tried removing the replacement driver and reverting to the original eHome driver, this didn't change anything. From playing about some more with the timing it appears that by lowering the repeat delay I get more and more doubles. Even triples when I have it set very low. Either I have misunderstood the how the timings work or this is the issue. From how I understand it the repeat delay shouldn't make any difference to how commands are accepted until a button has been held long enough to cross the held delay. Since it clearly is affecting it I wander if it can't be an issue in the algorithm that calculates if a button is being held and for how long. I don't know how your software calculates this but from my programming experience thats where I suspect something might be amiss. I'll try to think of a way of trying the remote out without the IR Server and see if the problem persists. [/QUOTE]

Verification