Jump to content
Flirc Forums

yawor

Administrators
  • Content count

    894
  • Joined

  • Last visited

  • Days Won

    60

yawor last won the day on February 11

yawor had the most liked content!

Community Reputation

73 Excellent

2 Followers

About yawor

  • Rank
    Forum Support
  • Birthday 03/03/1983

Profile Information

  • Gender
    Male
  • Location
    Warsaw, Poland

Recent Profile Visitors

5,149 profile views
  1. Send keyboard long press / not remote long press

    Unfortunately this is not possible. At least not right now. What exactly are you trying to use Flirc with?
  2. Send keyboard long press / not remote long press

    As long as you hold the remote button pressed, Flirc should also keep the keyboard key pressed.
  3. Search button from keyboard on Flirc

    @foto808 well, it's not that easy. It's not enough to send a hid report with specific hid usage, the device needs to first send a hid descriptor telling the host system what it is and what it does. If you send gamepad usage codes without first telling host system that you're a gamepad, the system won't know what to do with that report. Also many hid codes have extra payload like the X/Y axis position.
  4. NEC is slow because it's quite sparse timing-wise. The whole single frame is 108 ms long (when lead-out is included). This means that the signal is repeated every 108 ms when a button is being held down. With recent firmware versions you can try playing with Sony20 protocol. It's frame is only 45 ms long with lead-out. RC5 is not really that fast. Its frame is 114 ms long with the lead-out, so it's even slower than NEC. RC6 (and MCE which is in RC6 family) frame is 107 ms long with lead-out.
  5. NO_PUBKEY 3F0B7E963CBA18E3

    This repository is no longer in use. Please check https://flirc.tv/downloads for instructions how to add a new repository to your installation.
  6. Next gen flirc?

    Well, the wake up went through some significant changes, but I can't tell you with 100% certainty that 2nd gen is going to work better or worse in your case. The ability to wake the system up depends on many different components like motherboard, BIOS type and version, USB controller, power being delivered or not to USB ports on suspend/hibernate, the operating system, drivers and also other hardware being connected. If you search through the forum you'll see that after 2nd gen has been introduced and the wake up functionality has been added in one of the firmware updates, there were a lot of problems with it, where the 1st gen worked properly. And the implementation followed USB guidelines for wake up. Also in some situations, on the same hardware, it worked under Linux but had issues under Windows. Fortunately these issues have been resolved. I would say that if it doesn't work now (after all the work that went into that function), it's a high possibility that it's some issue with the computer or its configuration rather than the Flirc itself.
  7. Next gen flirc?

    There are few reasons why would you want to upgrade: Because of the hardware limitations of 1st gen, all new features will be only introduced to 2nd gen. Recently added support for long press and macros. Built-in IR LED which allows to send IR signals to other devices using command line util or through a released API. It's smaller and better looking :).
  8. Which Flirc model do you have? If it's 2nd gen one, then you can create macros using a command line tool (not yet supported in the GUI). But there's already a wake/suspend function you can use. It's in the GUI in Media keys controller.
  9. Long Key Presses

    If it's Flirc-SE then it's a 1st gen model. You can try changing the interkey delay value in advanced settings. Try decreasing it by 1 and do some tests. If not enough, then lower it again. This controls the time window within which the next received signal is treated as a repeat signal instead of releasing and pressing again. This value will also affect the ability to detect actual signal repeats. The new, 2nd gen model doesn't have that setting anymore as it records the actual signal delay value for each recorded button.
  10. You've probably recorded buttons from Samsung TV profile (maybe by accident). Connect Flirc to your PC, open Flirc GUI and press Erase, followed by one of the duplicated buttons from Samsung TV profile on the remote. Repeat for all duplicated buttons.
  11. Exactly as @FrogFan2 explained. To be more specific, you have two options: cd "C:\Program Files (x86)\Flirc\" flirc_util.exe record power or straight away: "C:\Program Files (x86)\Flirc\flirc_util.exe" record power There's also an option to add "C:\Program Files (x86)\Flirc\" to the PATH environment variable, which would allow you to execute flirc_util.exe from any location. To add Flirc to your PATH follow this page: https://www.computerhope.com/issues/ch000549.htm (just one of the first results when searching "windows add to path" in Google).
  12. Long Key Presses

    @arabesc I have few questions regarding your setup: 1. Which Flirc model do you have? 2. What remote are you using? Is it an universal remote? If yes, what profile have you selected? 3. If you have new Flirc model (the metal one), please open Flirc GUI and open Device Log in File menu. Then select enable IR debugging and press few buttons on your remote which you're using with Flirc. Please save it to a file and attach it here. 4. Save your configuration and attach it here.
  13. plain Debian repos not supported?

    Just change it manually to: deb https://packagecloud.io/Flirc/repo/ubuntu/ zesty main The packages should all be the same anyway.
  14. Control my Audio server with Harmony 900

    Unfortunately, you'd have to record everything again, as the IR signals would change and wouldn't be recognised anymore.
  15. Control my Audio server with Harmony 900

    Hi, Any software you want to control with Flirc needs to support keyboard controls. So first of all you need to make sure the MediaMonkey can be fully (or at least at satisfactory level) controlled with just a normal (or multimedia) keyboard. As MediaMonkey is not directly supported in Flirc (no predefined controller in the Flirc GUI) you need to know the key shortcuts/key combinations for all functions in the software that you're interested in. On the Harmony side, you can use one of the Flirc profiles, but you need to remember, that they are predefined for specific usages (Kodi, Media Center etc). This means that not all buttons on the remote are even mapped to some function and because of that they are disabled. You can still use them if you really want but you can also choose some 3rd party hardware profile, for example for some Samsung or LG TV (these usually work well with Flirc). Just remember to choose something you don't actually own (if you have Samsung TV, then don't use Samsung TV profile to use with Flirc). On the Flirc side, start the Flirc GUI application. If you want to stick with Flirc profile on Harmony you probably should disable built-in profiles (as MediaMonkey is not supported by these anyway). In the GUI, go to Advanced settings (in menu) and uncheck all built-in profiles. If you choose something else than Flirc profile in Harmony, then you can skip the previous step. Then in Controllers menu, select Full Keyboard or Media Keys (you'll probably need both). Then select a key or key combination which controls some function in the MediaMonkey - you should be asked by the application to press some button on the remote. Press the button you want to assign to the function you've selected. And continue that way until you map everything you need. If some buttons on the Harmony don't record then that means that the button is not used in the Harmony profile you've selected and is disabled (doesn't send any signal).
×