Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Chris!

  1. No worries, I think it was my bad anyway.
  2. We've probably got the key mapping wrong. Delete the key you assigned: https://flirc.zendesk.com/hc/en-us/articles/203653385-How-to-delete-a-key-from-Flirc The go to the keyboard controller: https://flirc.zendesk.com/hc/en-us/articles/202923419-Controller-presets-in-Flirc-GUI Then record the correct keyboard key, here's kodi's list of keys: http://kodi.wiki/view/Keyboard (is it "s" key you want for the shut down menu?)
  3. p.s. i've just updated the help article to clarify what we mean when we say record the same button twice. It wasn't clear before, thanks for pointing it out :)
  4. Are you referring to this article? For example, if you wanted to record the ok button on your remote twice: Press "ok" in the flirc gui, then press the enter button on your remote. The GUI should then say "button recorded" (or something similar) Then repeat step 1 again, the gui will say either "button recorded" again or "key already exists" Repeat step 1 once more and you should get "key already exists" You will need to do this for each key that is being recorded twice. By doing this we are telling flirc that the remote sends one of two signals for the same key press (e.g. ok), but we want flirc to respond the same. Does this help?
  5. For Flirc, I think the current model for firmware distribution is the most suitable. We used to have links for downloading old firmware but don't anymore, we have a beta releases so these bugs are usually worked out before they get send to everyone. There are many drawbacks for the Flirc project having multiple firmwares floating about. Apologies. I'll clarify that changing controllers does not replace existing keys. The documents are quite new so I try to add in detail i've missed as queries come up - I do read every thread in this forum. Also worth noting i've only recently taken up writing help documents and I do this part time (in my spare time).
  6. Looks like you may need to map a remote key to the letter "b" in the flirc GUI: http://kodi.wiki/view/Keyboard
  7. Agreed, i'll tweak it in the near future. Cheers! :)
  8. @Flappy Flirc: I was going to point out something similar. As you mentioned, it can be worked around very successfully so it doesn't seem to be a priority (e.g. some buttons on the amazon fire haven't been sending so Jason has been troubleshooting that a lot recently.)
  9. Using Flirc is a lot simpler to use than you may think, most of the complicated stuff is already done. I've been spending a lot of time writing help documents as forum posts can get very confusing. I think they'll be very helpful for you so I've linked some appropriate ones (but feel free to read all of the help documents). The documents are by no means finished but I believe they're pretty good. https://flirc.zendesk.com/hc/en-us/articles/203689115-What-is-Flirc- See how to program flirc: https://flirc.zendesk.com/hc/en-us/articles/202980419-How-to-set-up-Flirc also see guide to controllers: https://flirc.zendesk.com/hc/en-us/articles/202923419-Controller-presets-in-Flirc-GUI The save configuration is for backing up you configuration or if you wanted to apply it to more than one flirc (without having to go through the steps on each flirc) Yeah, there are limitations to the profile, there is a discussion about it somewhere on the forums. If you open the flirc gui, go into the file menu then advanced settings. Uncheck the "built in profiles" then switch to the keyboard controller and program the letters you want flirc to send with each remote press. Firmware is stored in the GUI, the GUI checks for updates and will notify you.
  10. What firmware number is your flirc running?
  11. Predominantly going to be explaining flirc stuff, in theory there shouldn't be too much tweaking needed. Most of the recent articles in the zendesk are done by me (under Jason's name) as I have more time for doing it, unfortunately I don't know the nitty gritty of how the settings work so Jason will be writing those articles - he has a lot less free time than I do. I do I agree with you though and we are working on it. I've taken the choice to aim the help documents (at least to start with) toward less technical documentation - we will introduce a "technical section" though. Interkey delay is telling flirc how long to wait before sending another command to the computer (even if it receiving ir signals), Increasing the interkey delay will tell flirc to wait longer before deciding the button was let go. Decreasing the interkey delay will tell flirc to wait less before deciding the button was let go. Not sure if the numbers directly correlate
  12. I'm not really picky on remotes so I have the cheapest harmony remote (~£15). It allowed me to map the volume key to always go to my speakers rather than the tv, which is neat, others could probably do that. Any how, the main reason i'm commenting is I thought you'd be interested in having a quick read of our zendesk knowledge base - particularly the "getting started with flirc" it should give you a great overview: https://flirc.zendesk.com/hc/en-us
  13. We're working hard on documentation explaining each setting, for the mean time we've already completed a few documents that try to explain how to modify performance: https://flirc.zendesk.com/hc/en-us/sections/200669959-Troubleshooting-Keypresses
  14. It is really nifty how it does that. @Jason: What is the minimum version of mac flirc gui runs on? (Is it also worth adding this to the download page? http://flirc.tv/downloads/)
  15. If you do figure out the keyboard mappings post back and i'll add it to the help article linked in my post above
  16. Take a look here for what key flirc will assign depending on the controller: https://flirc.zendesk.com/hc/en-us/articles/202923419-Controller-presets-in-Flirc-GUI
  17. Thanks for posting back :) Glad it's working for you now.
  18. I'll definitely make a note of this for future users. Sorry for the hassle. Chris
  19. It should just work out of the box. I've just tried it on a TV remote I had next to me and it worked straight away. The most common reason for it not working is the remote doesn't continuously send signals when the button is held down... I've forgotten if that's the case with the Xbox 360 media remote. Maybe try another remote just to check this? If i've misunderstood and it is repeating but very slowly then you can ajust the inter key delay in the advanced settings in the Flirc GUI
  20. This is strange. I've just double checked using a Flirc I had nearby and it worked on my machine, we'll have to figure out why it's not working for you. Couple of questions: What remote are you using and which button isn't working now? What controller preset are you using the the flirc gui? (minimalist/keyboard/xbmc) When you open the Flirc gui app it should check for updates and flash up an update. 3.5 is the newest firmware that did resolve issues with certain remotes.
  21. Settings may have been lost in the update, try clearing the configuration and reprogramming. Flirc's latest firmware is 3.5 which can be updated through the Flirc GUI app
  22. Awesome, I'll write a zendesk article for it. Thanks for the clarification. Have a great weekend
  23. @yawor: Was the solution you suggested for when a user is experiencing poor Flirc sensitivity? I'm trying to expand Flirc's "troubleshooting keypresses" section of zendesk help articles: https://flirc.zendesk.com/hc/en-us/sections/200669959-Troubleshooting-Keypresses
  24. Fresh off the press, here is the official helpdesk article: https://flirc.zendesk.com/hc/en-us/articles/203167509 Thanks for everyones input :)
  25. FYI, I think Jason is a bit busy atm, I haven't heard from him for a few days - don't worry, you're not being ignored Hang tight :)
  • Create New...