Jump to content
Flirc Forums

Better support for multiple/held down keypresses


Chris!

Recommended Posts

Hi All,

Thought i'd let you know that Jason is concerned about the "sticky key" effect sometimes observed (e.g. when a key on the remote is pressed multiple times in quick succession resulting in a lot more scrolling than anticipated).

This is due to the way Flirc currently implements how it receives a signal, Jason explains it beautifully below:

Here is a quick tutorial:

Remotes send out a 'packet of data' in the form of light pulses. These packets are separated by each other by ~40ms-120ms. That number is constant on each remote, but varies from remote to remote.

When you press the button, the remote sends out a bunch of packets all with this fixed spacing (again, where the fixed spacing is different on each remote).

So when you press a remote button, flirc actually may sees like 30 packets. If you are rapidly pressing a button, I need to distinguish if this is you holding the button down, or if you are just pressing it rapidly.

It's not very easy to do, and I have a general concept that works for remotes, but will often feel 'sticky'.

As you can see there are significant variables in there:

As you can imagine and appreciate it will take a lot of Jason's work and (personal free) time, so your patience is appreciated - rest assured it's on his list, at the earliest after wake is perfected.

Pleasant regards

Chris

  • Like 3
Link to comment
Share on other sites

  • 1 month later...

Interesting. Sounds extremely difficult if not impossible to have a perfect solution for every single remote out there. Personally, I would love to be able to tweak this myself to get perfect repeat detection with my own remote, rather than a mediocre catch-all solution. I understand the desire to have flirc be as easy as possible to setup but, perhaps, as the community grows, we could help develop "profiles" for specific remotes that are selectable in the GUI that have the necessary settings ready to go. In other words, help us help you B)

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

I'd settle for a configurable delay even if it was a settings text/xml/plist file that had to be edited externally. I understand the desire to make it elegant but given the pace of development, quick and dirty is preferable for me. I purchased three of the flircs, but really only use one because of the quirks and wife-acceptance-factor.

Link to comment
Share on other sites

Chris,

I would like to "throw my name in the hat" as someone who wants to adjust flirc's response to rapid button presses. I recently purchased two flircs, and I was sad to find that it takes a fair bit of patience to navigate XBMC with all the runaway scrolling.

Would it be possible for us to patch the firmware ourselves with a hex editor? Could jason give us some pointers on how to do this?

Kind regards,

Elliot.

Link to comment
Share on other sites

  • 4 weeks later...

Hi mike,

You're right there hasn't been any new beta's for quite a while. Jason is working through the kinks - restructuring code rather than the processes he was doing, you can keep up to date with what he's doing via his blog (blog.flirc.tv).

It does sound rather promising (taken from his latest blog posting)

My goal is to have major releases by the end of the month of both the firmware and the GUI.

Pleasant regards

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...