Jump to content
Flirc Forums

jason

Administrators
  • Posts

    2,704
  • Joined

  • Last visited

  • Days Won

    116

Everything posted by jason

  1. I think I can explain this. Which remote profile are you using? I believe this double key remote profile is one of those microsoft remotes that use the non standard frequency, 56kHz. 38kHz is the frequency most remotes use, which is the center frequency for flirc. While I played some tricks to get flirc to work at 56kHz, the placement from the front of the computer, to the back of the computer, will actually have slightly different frequency drifts, changing the unique pattern associated with a button. Does that make sense? Try changing the remote to a samsung, panasonic, etc. I don't believe this issue will persist.
  2. This may be the remote profile you chose. If it's not outputting Infrared, then flirc wont be able to learn anything. You can try verifying with another remote, or using another key on the remote that works.
  3. You shouldn't have to touch your xml file. This looks to be the same problem as above, but can be circumvented. Let me know how it goes.
  4. This remote profile is a microsoft protocol that uses a non-standard frequency. Flirc can work with it, but it's not the best as I had to play a lot of tricks. The flirc command line has an option called sensitivity. You can try lowering this number: flirc sensitivity 2 (for example) With each sensitivity, you need to re-learn your keys. I can't do this on the fly as it's a limitation of my algorithm. Another circumvention would be to use a different remote profile. Most people assume to use media center remote profiles like; plex, boxee, apple tv, etc. When really, you can use any ol' remote. Try a samsung, or panasonic. I always recommend those as I've always been sure they don't do anything out of the norm like Microsoft.
  5. Hey VanSmak, There is a strange issue with these certain remotes. I will eventually fine tune this with the firmware. Basically, the remote sends out a unique key code every other consecutive key press, for the same physical button. The quick remedy to this is to record each button twice, and "catch" each unique key code for every button. Let us know if that does the trick.
  6. jason

    XBMC + FLIRC

    This is great, thanks so much guys for registering, and posting. I'm just getting used to these forums, so things might shift, but I'm extremely grateful for you guys.
  7. jason

    Welcome!

    Welcome to your new Invision Power Board! Congratulations on your purchase of our software and setting up your community. Please take some time and read through the Getting Started Guide and Administrator Documentation. The Getting Started Guide will walk you through some of the necessary steps to setting up an IP.Board and starting your community. The Administrator Documentation takes you through the details of the capabilities of IP.Board. You can remove this message, topic, forum or even category at any time. Go to the documentation now...
×
×
  • Create New...