Hi !

I've been using the Flirc GUI v.3.27.16 and I'd like to change the duration of a keypress. Is that possible ?

Example : I've paired a button with the "A" key. And when I press the button only a single A appears in a text editor.

But trying some games with it, the key press duration is too long and triggers 2 in game a presses.

 

Anyway to change that in a config or something ?
Thanks

4 hours ago, potomax said:

Hi !

I've been using the Flirc GUI v.3.27.16 and I'd like to change the duration of a keypress. Is that possible ?

Example : I've paired a button with the "A" key. And when I press the button only a single A appears in a text editor.

But trying some games with it, the key press duration is too long and triggers 2 in game a presses.

 

Anyway to change that in a config or something ?
Thanks

This is really dependent on the operating system. It's usually referred to the key repeat time. The game might be overriding it because the flirc shows up as a keyboard, no reason otherwise it would have a different rate than the OS. Let us know what you find.

Thanks for the answer @jason But I don't think it's that

I used this site to test it : https://www.clickspeedtester.com/keyboard-latency-test/
 

When I use my physical keyboard, the duration of the press is usually around 70-80ms (q key in the screenshot)
But when it's triggered with flirc, it's always 192ms minimum (a key in the screenshot)

So the keypress triggered by flirc is 2.5 times longer than my regular key presses

 

can you save and post your config?

Of course, here it is.
Thanks.

flirc-potomax-wasd.fcfg

I see a couple things.

Can you tell me if you see the same results with the left arrow and the right arrow?

Yep same result.

For every arrow the minimum duration is 192ms

 

How about the other keys recorded, 's', 'w', etc.

Can you also go to file->advanced, and then enable IR debugging. Press and hold the right arrow, save and send that here too.

 

I sent s and w in screenshots in the above answer. Same thing.

In the log, I pressed the right key 3 times without holding and then I held it for a couple seconds

Log right arrow.txt

Edited February 6, 20251 yr by potomax

It looks very strange. Are you super close to it? Make sure to aim at the ceiling if you are. Also, batteries could be low on the remote. It's not getting clear signals.

I tried various angles and distances and battery change and it's always the same.

But, isn't it your software that translate those signals into a virtual keystroke.
Can't something be parametrized at that level, adjusting the virtual keystroke ?

Because other than the length of the press everything is working fine, it's pressing the right keys at the right time.

I just wanted to add that I have this issue and I've found it to be a long standing issue with the FLIRC and it's what kept me from buying more than one.  The 'single press' is held too long and it makes it hard to do 'rapid sequential presses' rather than 'holding a button until repeat kicks in'.

I use MCE receivers on Windows based machines where I can but on Steam OS that driver is missing some buttons and doesn't map real friendly.  I love this thing 95% of the time but this is the issue that's kept me from just retiring all the MCE receivers.

I can use a keyboard in Kodi to 'hit an arrow over and over again quickly' without going into 'key held, just repeat'.  I can do the same with my MCE remotes and an MCE receiver.  But use that MCE remote with a FLIRC and it's just not quite as responsive as the MCE receiver.  Also sometimes it seems 'gum up' and not send all the presses on time, causing a delay, then it sends a bunch of them at in short order, as if the button queue had filled up faster than it could send the output.

I did the same test as the OP.  The first example is the FLIRC, it averages 224ms but sometimes shorter.

 

Same PC, same MCE RC6 remote, but with a standard MCE Receiver:

The key presses on the MCE receiver are not only shorter but extremely consistent