Jump to content
Flirc Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


yawor last won the day on October 19

yawor had the most liked content!

Community Reputation

60 Excellent


About yawor

  • Rank
    Forum Support
  • Birthday 03/03/1983

Profile Information

  • Gender
  • Location
    Warsaw, Poland

Recent Profile Visitors

4,584 profile views
  1. Error message in log

    The gen1 device doesn't support debug log. It is still supported by the software. The message may need some editing because it may cause confusion. Have you tried plugging Flirc to a different USB port? It may be an issue with Windows drivers. I had similar issue few times on my system and switching to another port worked for me.
  2. Bugs in 3.1.0

    With WMC (or any other RC5/RC6 protocol remote) you always need to record the key twice. There's no other way as Flirc is not a dedicated WMC receiver. It does not decode the protocol and retrieve the command. For Flirc to work universally with most of the remotes (not only WMC) it uses a proprietary algorithm which calculates a hash from a signal timing information. Changing even a single bit (the RC5/RC6 toggle bit) changes the timings and the hash is different. So to Flirc each key press is actually a totally different button on the remote. When you have built-in profiles enabled and you only record the key once, it interferes with the built-in table With WMC you have following choices: Don't record buttons that are already supported by the built-in WMC profile (like direction keys) If you record some of them, always record them twice with the same key selected in the GUI or flirc_util (may cause issues if you forget to record some key twice) Disable the WMC built-in profile and record all keys you want in the way you want (recording twice is still a requirement) Can you record a key from your WMC remote and attach the config file? I want to check something. Be sure to hold the key while recording.
  3. Does flirc able to do Fn functions?

    Fn key is not a modifier key in the same sense as other modifier keys like ctrl, alt, shift. Normal modifier keys are being processed on the USB host device (your computer or other device you connect the keyboard or Flirc to). When you press for example ctrl + F, the keyboard sends hid code for key F with modifier code for ctrl. Fn key is being processed on the controller which is built into the keyboard. When you press Fn + F12, the keyboard doesn't send hid code for F12 key anymore. It sends something that's dependant on the keyboard itself (different makers and models have different Fn functions on different keys). In your case, the Fn + F12 is the media key for Play/Pause. You can find it in Flirc GUI in Media Keys controller.
  4. Flirc App V3.1.0 Is virus infected

    Thanks for the update :).
  5. Flirc App V3.1.0 Is virus infected

    It's either a false positive or something on your system. Here's a scan of freshly downloaded installer: https://virusscan.jotti.org/en_US/filescanjob/wfqftu0ylv
  6. Bugs in 3.1.0

    I can confirm that. I don't think that's a bug, but I agree that there could be some kind of warning about the GUI. Maybe in the help message or when any error is reported. As for the actual detection of the GUI being opened, I don't know if there's an easy way to check that in a cross-platform way (remember that this would need to work across all supported systems). Maybe some locking mechanism could be used. Flirc v2 doesn't support the interkey delay setting because it actually learns the interkey delay from the remote itself and stores it for each recorded key. For that to work properly you need to actually hold the button when recording (so the signal has a chance to repeat itself) not just press it quickly. I can't reproduce this. At least not on Linux. Please remember that the MCE remote is using RC5 protocol with two separate signals for each key. You need to erase it twice in the same way you record it. The Erase button in GUI uses the same procedure as the delete command in the flirc_util. Sorry to hear that. I hope it'll get sorted out as soon as possible. @jason?
  7. Ubuntu Install 404 not found error

    Don't use that instruction. It's not valid anymore. To get new instructions, go to https://flirc.tv/downloads, select Linux, accept terms and click on the link. It'll take you to the page with current instructions. Follow the one for Debian based system.
  8. Harmony Flirc run one on two events

    Did you use an Windows MCE remote profile on the Harmony? If yes then either don't use it (or any other RC5 or RC6 ones) or you need to record each remote button twice. RC5/6 protocols have a toggle bit which changes for each consecutive button press making the signal seen by the Flirc different.
  9. FLIRC Update loop

    It seems that the Windows installer wasn't updated to 3.1.0 for some reason. Please ignore the update dialog for now. Sorry for the inconvenience. @jason will fix the issue as soon as possible (probably later today).
  10. 2 Flircs with harmony

    Have you programmed the wake key on the gen1? If you didn't then any known key is going to wake the PC. Still it's probably a bug that it also wakes it up upon receiving a signal from Flirc/Kodi profile when the built-in profiles are disabled. Try recording a wake button for gen1 so that only that single button wakes your basement PC.
  11. Compatibility with dive computer

    Do you want to transfer some data from your dive computer to the PC? If yes, then Flirc is not what you want, because it's not a generic IR receiver. Flirc is a specialised IR receiver which translates IR commands from a remote control to keyboard key presses. It doesn't allow access to RAW IR signal. If you mean something else than data transfer then please describe it in more details. I'm not familiar with this kind of equipment.
  12. Assigning multiple buttons to same key

    Try using something different then. At least to try find the cause. If you don't have a Samsung TV, create a profile for some newer model in your Harmony and record few keys (especially the ones that you have problems with like direction keys). Samsung uses NECx2 protocol which works really well with Flirc. You can also try using LG or Panasonic TV profile.
  13. Assigning multiple buttons to same key

    You can try using different profile on your Harmony and then reprogram your Flirc to use it instead of the current one. What Harmony profile are you using currently?
  14. Assigning multiple buttons to same key

    You can have multiple remote buttons assigned to the same key/function in Flirc. Just record the same key in the GUI multiple times pressing different remote button each time. So in your example, click on the Q key in the GUI, the software will ask you to press a button on the remote. Press the back arrow on the remote. The click the Q key in the GUI once again and when asked, press the circular arrow on the remote. When the keyboard key/remote button pair is saved into the Flirc, only the remote button must be unique. If it's not unique (it's been already assigned to some keyboard key) then you'll get an error that the button is already in use.
  15. Assigning multiple buttons to same key

    You can only assign a single key combination per each individual remote button. A key combination is a normal key + optional modifier keys (shift, ctrl, meta/win, alt). There's a feature planned that will allow to create key sequences: one press of a remote button will execute a user predefined sequence of key presses, but it's not yet implemented. Why would you want to assign multiple keys anyway? Can you describe in more details what do you want to achieve?