Jump to content
Flirc Forums

yawor

Administrators
  • Content count

    937
  • Joined

  • Last visited

  • Days Won

    64

Everything posted by yawor

  1. yawor

    New downloads for linux don't work

    @EvilWayz please check your apt sources if they are all correct. https://packages.ubuntu.com/bionic/libqt5xmlpatterns5 According to this, the libqt5xmlpatterns5 in Ubuntu 18.04 depends on qtbase-abi-5-9-5, not qtbase-abi-5-9-0 like in your case. Is this a fresh install or did you upgrade from a previous Ubuntu version? From what I see, the qtbase-abi-5-9-0 was provided by Ubuntu 17.10.
  2. yawor

    FLIRC v1 Sleep/Wake

    I've just tested on a Flirc v1 and seems to be working. The wake/suspend key from the Media Keys controller is only able to suspend the computer though. The WAKE key from the Full keyboard controller wakes the computer properly. Make sure you have the Sleep detection enabled in advanced options in Flirc GUI. Also check the Power tab on each USB keyboard device in Device Manager and make sure that they all are allowed to wake your PC.
  3. Yeah the MiBox protocol is a little complicated. Guys at the JP1 forum were able to create a protocol executors for few types of microcontrollers used in UEI remotes (like I've said, I'm using a Nevo C2 which can be programmed using RMIR). As for the Flirc, you need to remember that it emulates a standard USB HID keyboard. So it should be able to control anything that accepts an USB keyboard input. On the IR side, it can be used with many (but not all) standard protocols, but from my experience it works best with NEC family protocols. So if you program your MX-500 to some device which uses one of the NEC protocols, then it should work.
  4. I'm using Flirc with MiBox but in a mixed way. I'm using a Nevo C2 remote and I've set it up so it uses MiBox's native IR for the keys it supports and custom IR via Flirc for more keys (for example to directly control some features in Kodi). This setup works really well. It should also work with just the Flirc (without native IR) with some work. Btw what options do you have when you program your URC? Can you enter custom pronto hex codes? If yes then I could try generating codes for the MiBox.
  5. yawor

    eye-TV

    I don't really know that software nor I have even access to a mac, but a quick Google search for Eye-TV gave me this page: https://www.geniatech.eu/faq/what-are-the-keyboard-shortcuts-for-eyetv/ It contains a list of keyboard shortcuts needed to control the Eye-TV using a keyboard (a requirement with Flirc). Having that list, you should install and open Flirc application and map selected functions to your remote. For example, if you want to map a Select function (which is controller by enter/return key), you should open a Full keyboard controller in the Controllers menu in the Flirc app, click on the enter key on the virtual keyboard and, when asked by the software, press a button on the remote you want to assign to the enter key. You should repeat this for other buttons on the remote.
  6. yawor

    Transmit IR signal over Flirc in a Raspberry

    Sorry it took so long. I've been able to sit down to this today. First of all, the protocol used by your Sagemcom remote is known as Nokia32. I've been able to decode the IR codes included in the attached file. I've also been able to transmit then from my Flirc and the received signal is correct (I've built myself a little Arduino based IR analyser, so I can record and analyse signals). On the other hand, I can't decode the IR signal data from your first post. The software I'm using doesn't recognise it neither a Nokia32 nor any other known protocol. I think may be somehow malformed. Try sending other signals, for example the ones from the file you've attached, and check if your box reacts to them.
  7. Do you use multimedia keys on the Flirc? If yes then this is probably your window manager on Ubuntu informing you that the key is not mapped to any function or can't be used right now. You can test this by connecting a normal keyboard with multimedia keys and try pressing some of them like Play/Pause etc. The same happens on my Arch Linux with Cinnamon when I press the Play button on the keyboard and no player is running. If, for example, I open the Spotify app, then the Play button on the keyboard works on doesn't show that symbol. This is not a Flirc issue but your OS configuration issue. You need to make sure that the software you're using can properly use multimedia keys or change OS configuration to somehow force them. I rarely use multimedia keys and had no issues with them, so I won't be able to help more than this. --edit-- Alternatively you can check what keyboard shortcuts are supported by the software you're using and map them properly to your remote using Flirc GUI.
  8. yawor

    Added functions to Kodi Profile

    Yeah, there's no notion of controller in the Flirc itself. It only stores key codes and IR hashes. Many people get the wrong idea that they can use only a single controller in the GUI, where in fact the controllers in GUI are only to group different key sets (for example the Kodi controller is just a set of predefined keyboard shortcuts). I think this is more of a documentation issue than anything else.
  9. yawor

    Transmit IR signal over Flirc in a Raspberry

    Could you also try checking the exact model of the box? Does it have a model name or number on the bottom of the device?
  10. yawor

    Transmit IR signal over Flirc in a Raspberry

    Can you open the log window with IR debugging turned on, press some buttons multiple times, then save the log to the file and post it here?
  11. yawor

    Flirc backup and restore

    The configuration on the device is updated automatically every time you record or delete a key or change something in advanced options. Yes, restoring the backup (using load configuration options in the GUI) overwrites previous config stored on the device.
  12. yawor

    On screen keyboard in Windows Media Center?

    Well, Flirc is a keyboard, so maybe WMC thinks it doesn't need to open an on-screen keyboard, because it got the event from the "real" one (to the system there's no difference between real keyboard event and Flirc events). But this is only a theory. I've never used WMC.
  13. yawor

    Transmit IR signal over Flirc in a Raspberry

    Hi, What TV box is that? I'm trying to decode the signal data you've used by I don't recognise the protocol. Is the Flirc IR window pointing in the TV box's direction? Flirc has really good IR receiver but the IR transmitter is not very powerful.
  14. yawor

    Flirc backup and restore

    @Bob Sutton you can name your config files any way you want. The name of the config file doesn't matter to Flirc. It is only a backup of the config. Flirc doesn't load its config from a file as the config is stored ON the device. To make it clear: save configuration is used to backup Flirc's internal config area to a file and load configuration is used to restore Flirc's internal config area from a previously saved file. You don't need to save the config for Flirc to work. The "invalid length" has nothing to do with config files. Can you send me your log with that message?
  15. @Bob Sutton my question was about that specific remote which @Cubytus asked about. I don't understand why do you need to teach your remote something. For example here's my usual approach with my universal remotes: 1. If this is a multi-device universal remote, select a device slot I want to use with Flirc. 2. Select some device like a Samsung TV (or other type of equipment; the idea is this has to be something you don't actually have in your home) and program it on the selected device slot. 3. With Flirc GUI test how many keys I'm able to record, if they are all unique, if they work on each key press and if the key repeat works. Not all hardware has need to use all keys on the remote so some keys may be inactive. If I'm not happy with that setup then I format Flirc and go back to point 2 and select different device. 4. After finding a device setup on the remote Flirc is happy with, I start programming each key on the remote with specific functions (for example in Kodi controller) or key combinations (in full keyboard controller - not all functions are predefined in the Kodi controller, but it's easy to find default keyboard controls on Kodi wiki pages). 5. Some functions in Kodi don't have a key combination assigned in the default keyboard control mappings. If you need to control such function directly with Flirc, you need to modify your Kodi keyboard mappings (search for keyboard.xml on Kodi wiki pages) and include added key combinations in your Flirc config using Flirc GUI. This is a most generic instruction which should work with any universal remote. With Harmony remotes you also have predefined Flirc harmony profiles. I'm using a setup for some Samsung TV model (uses NECx2 protocol) for few years now. I've used it with original Flirc (in clear plastic) and I'm using it with new Flirc gen2 (metal one).
  16. yawor

    Dreambox Remote

    No, unfortunately it wouldn't solve anything, because hashing algorithm doesn't work properly with XMP signal (protocol used by Dreambox). This means that even if you have two different frames captured in the debug, they can still produce the same hash. Like I've already said, this protocol is really ugly to work with.
  17. yawor

    Dreambox Remote

    Well, I thought that my response was enough as for me the other questions were based on the assumption of using the Dreambox remote. As the Dreambox remote is not supported, any of the features you've proposed wouldn't help. Anyway: A1: It's not possible to create hash yourself. The hashing algorithm is proprietary. A2: This is a nice idea and has been proposed few times by some people (myself included). There are plans to implement this (but it would still not help with Dreambox). A3: I understand what would you like to achieve with this but I don't think it would be possible to do. Please understand that Flirc tries to be as universal as possible when it comes to supported remotes/different IR protocols, but some of the protocols are so complicated that adding support for them would make the algorithm much more complicated and slower that all the other supported remotes would also suffer from the slow down.
  18. yawor

    Dreambox Remote

    Hi, Sorry to disappoint you but the protocol used by the Dreambox remotes (XMP) is not supported yet. It's really hard to tell when (if ever) it's going to be supported as it's a really nasty one. Besides sending 2 or 3 different frames on every single key press, it also uses 4-bit encoding scheme - it encodes each 4 bits of the data as one of 16 different burst/gap lengths.
  19. The post is hollow, but this doesn't impede the heat transfer in any significant way. The post itself may have less heat capacity, than a solid block, but the whole case acts as a heat sink and heat spreader so the heat from the CPU is dissipated quickly enough.
  20. @Cubytus is this an universal remote? Can it be programmed to control different devices? If yes, then you can try reprogram it for some other type of hardware and then try using it with Flirc.
  21. yawor

    win 10 software window too big

    Try playing with display scaling in Windows settings.
  22. yawor

    how to enter scan code to flirc?

    Flirc doesn't operate on scan codes, but on HID codes for keyboard and consumer tables (consumer table is currently limited to 1 byte only, so codes only up to 255 - some specific codes above 255 are also supported by other means), because Flirc is a HID device. HID keyboards know nothing about scan codes. Scan codes are generated from received HID codes by the operating system according to keyboard layout settings (for keyboard table) or other drivers (for multimedia/consumer table).
  23. yawor

    Flirc + Harmony => Keyboard, how?

    Controllers are interchangeable. They only group different keys together, but Flirc doesn't store information about selected controller. So you can record some keys from one controller and some keys from another. Most controllers (like Kodi for example) are just a collection of pre-configured, ready to use keyboard shortcuts and you can actually achieve the same functionality using full keyboard controller if you know those shortcuts. Flirc doesn't deal with key codes. It works on a lower level and maps your IR signals to USB HID codes. It's up to your OS to interpret them and emit key codes to applications (which is done by the keyboard layout selection in most OSes). You can use flirc_util for more precise control as there is a "record_api" command which takes two 1-byte values (decimal) as a key definition. But you need to enter HID codes, not key codes. I like to use this http://www.freebsddiary.org/APC/usb_hid_usages.php to get my HID codes. Scroll down to table 7 (keyboard). Bear in mind that information on that page is only true for US QWERTY and other compatible layouts. HID codes are assigned to a physical key location on the keyboard, not to a specific letter or symbol. So key "Y" on QWERTY will have the same HID code as key "Z" on QWERTZ.
  24. @orion just edit the /etc/apt/sources.list and replace debian with ubuntu and buster with with xenial in the Flirc repo address. Then run apt-get update and apt-get install flirc again.
  25. Thanks for sharing. This is really good info. It may help us troubleshoot in the future. BTW the new Apple's FaceID also uses IR projector. This may apply also to other mobile face or eye scanning technologies. I wonder if/how they interfere with Flirc. I've just checked on my Huawei P10 Lite but I need to point the screen at the Flirc right next to it. I wonder if cameras with laser focus could also affect it. Unfortunately P10 Lite doesn't have one and my Nexus 6P has broken down.
×