Reply to thread

Message

<blockquote data-quote="hairlesshobo" data-source="post: 893463" data-attributes="member: 121339">I don't know the exact repeat time, but i can say that when i use blasting to control my receiver that it responds as quickly as if I were using the original remote control.I have had similar issues that you are speaking about with response speed in the past using learning remote controls, and it usually came down to a poorly learned code. My setup is using WinLirc with EventGhost, and then I just use IRSS for blasting the channel change of my cable DTAs. I have two different Blasters, both of which are USB MCE units with two blaster outputs. One is HP branded and one is Dell branded, but both operate the exact same way. I don't know if you are familiar with WinLirc, but if you decide to give it a shot, the key is to make sure that the code is not learned in Raw mode. When learning in Raw mode, from my understanding, it is basically just taking a snapshot of the code that it receives and sends it back out. So if you hold the button for say, 250ms, then the code length will be roughly 250ms. This may not be 100% correct, but it seems to be how it has worked with me in the past. So I say this to tell you that I also agree that the code is likely too long. Have you tried relearning the code a couple times to see if the condition gets any worse or any better?</blockquote>

[QUOTE="hairlesshobo, post: 893463, member: 121339"] I don't know the exact repeat time, but i can say that when i use blasting to control my receiver that it responds as quickly as if I were using the original remote control. I have had similar issues that you are speaking about with response speed in the past using learning remote controls, and it usually came down to a poorly learned code. My setup is using WinLirc with EventGhost, and then I just use IRSS for blasting the channel change of my cable DTAs. I have two different Blasters, both of which are USB MCE units with two blaster outputs. One is HP branded and one is Dell branded, but both operate the exact same way. I don't know if you are familiar with WinLirc, but if you decide to give it a shot, the key is to make sure that the code is not learned in Raw mode. When learning in Raw mode, from my understanding, it is basically just taking a snapshot of the code that it receives and sends it back out. So if you hold the button for say, 250ms, then the code length will be roughly 250ms. This may not be 100% correct, but it seems to be how it has worked with me in the past. So I say this to tell you that I also agree that the code is likely too long. Have you tried relearning the code a couple times to see if the condition gets any worse or any better? [/QUOTE]

Verification