PDA

View Full Version : antirepeat and 3.0.24



Ron
October 13th, 2002, 12:55 PM
What number are you using for the anti repeat ?

bherrin2
October 13th, 2002, 12:55 PM
All,

Is the antirepeat function broken in 3024? My pronto is sending double codes to Girder so i started messing with the antirepeat (as each action was being carried out twice).

As an example, have a command to toggle between full screen and windowed mode for WinDVD, I can set the A.R. interval to 2000 ms (2 seconds), Save the GIR exit and restart Girder, click the button three time in a row and WinDVD will toggle three times (a total of six executions of the command) within the 2 seconds it should be ignoring the command.

An AVS forum member gave me a work around that does seem to work. For each command I set the statecount to 2, begin state to 2, check execute on all but 1. This works for now but it doesn't seem like a long term solution.

Any thoughts?

<font size=-1>[ This Message was edited by: bherrin2 on 2002-01-10 23:18 ]</font>

bherrin2
October 13th, 2002, 12:55 PM
Ron,
I tried 500 (.5s) 750 (.75s) and 2000 (2s)
see below for the real fix for the problem.

Well,

I got it fixed late last night. THe setup I was having trouble with was for WinDVD, using codes from my APEX DVD remote (the player crapped out a few months ago but i kept the remote). I noticed that a single code (cursor up) was working correctly so I started looking at the learned IR codes in girder. I noticed that the working code was exactly 4 hex bytes (not sure about the term but the code was 16 characters shorter) than all the rest of the codes. On a hunch I relearned another button from the apex to the pronto being VERY carefull to just tap the source button instead of pressing it. Downloaded the proto and checked that code again and it to came up 4 bytes shorter and it to was now working using default state settings.

So.. I re learned all the codes again and they are are all working now.

Looks like the apex remote was sending double codes because i was holding the button down too long. I seems that the code was over running the input buffer and girder was truncating the code back to a "valid" IR code. I say this because trying to edit the learned codes to shorten them resulting in girder spitting out an invalid IR string. I'll try and get some screen caps of the before and after code so i can compare the two side by side and see what the exact diff is between the "bad" codes and the good ones.

Whatever the technical root cause (probably me fat fingering the remote) was, It's working now.

I'll go back and look a the antirepeat setting tonight and see if it functions differently with proper IR codes assigned.

<font size=-1>[ This Message was edited by: bherrin2 on 2002-01-11 13:20 ]</font>

<font size=-1>[ This Message was edited by: bherrin2 on 2002-01-11 13:23 ]</font>

ravton
October 13th, 2002, 12:55 PM
No help here, but it does the same thing for me. 3.0.24 ignores the antirepeat setting for me. With a button held down I get around 10 events per second, regardless of what the antirepeat setting is (same code every time).