yawor
-
Posts
1,003 -
Joined
-
Last visited
-
Days Won
74
Posts posted by yawor
-
-
BTW, as it turns out it was this easy. It would be just as easy creating a new layout. All that's needed is a new image, more or less :p
Yeah, I agree, more or less :P. But remember that there are so many keyboard layouts out there. Many countries have multiple different layouts. Even in USA some people prefer Dvorak instead of QWERTY. I use Polish Programmers layout which is basically US QWERTY but adds polish characters which are available by using Alt Gr (right alt key) and normal letter combinations. But there's also an older standard based on QWERTZ (I think it was based on German keyboards) which has polish characters available directly. There's also a Polish Dvorak keyboard (which is not the same as Dvorak).
As you can see having all the layouts as images built into the program is not really possible because it would take a lot of space on the disk and would take much longer to download the installer. Also having just a different image is not really enough because other controllers (like the Kodi controller for example) are just preconfigured with specific HID codes right now, which is bad for different layouts. To add to the issue there are also different PC keyboard standards. The GUI right now is using the PC101 keyboard layout. You probably have the PC102 physical keyboard which adds extra key between left shift and Z key (like in the images above). There's also a PC104 keyboard for example.
I think to do this properly the app would need to be rewritten to use some definition files and render the keyboard on the fly instead of using a static image. Linux is a very good source for such definitions and I've already checked them out. The good thing is it has support for most (if not all) keyboard layouts out there and also there are geometry definition files that define the exact look of the keyboard for different keyboard types (PC101, PC102, PC104, Mac, etc). And the files are just text files. The bad thing is this would require to create a parser for all the files and to create whole new logic to use them which is certainly not an easy task.
-
Can you tell me what keyboard layout are you using exactly? It would be best if you could find and post an image representing your physical keyboard. It would be also helpful if you can write what you need to press on your physical keyboard to get + and - symbols (for example if you need to hold shift or other modifier).
---edit---
Depending on what you've written earlier I think this is your layout:
If I'm right the "-" symbol is on the key right next to the right shift. In US QWERTY layout a key in that position has "/?" symbols. That means to get "-" from Flirc on your layout you need to record a button for "/?" key in the GUI. It is in the same position on the keyboard as the "-" on your physical layout. Are you getting now where's this going? Also the "+" symbol on your physical keyboard is in the same position where the "-" symbol is in the GUI. So to use "+" you actually need to record button for "-" key in the GUI.
I hope this is now more understandable.
-
It's actually only a single person behind both hardware and software part of Flirc and he's doing it in addition to his main job and family responsibilities and portion of the profits from selling Flirc are donated to a cancer research facility.
I understand that as a paying customer you would want a fully working solution but on the other hand I think you exaggerate a little the amount of work around you must do to just record two keys. You should be able to do this in less than 5 minutes.
I myself think of Flirc not as a full solution but as a means to achieve it. For simple things Flirc itself is OK, but you will need to do some work if you ever want to extend the functionality beyond what it's capable of.
BTW I've already had a conversation with Jason (the person behind Flirc) about the keyboard layout issue quite some time ago. Please believe me if I say that I'm 100% supporter of having keyboard layout selection support implemented in the software. This would probably solve a good portion of the issues people have on the forum. But as a programmer myself I also understand the amount of work required to implement support for layouts (you need to get them from somewhere in the first place) and this is not only needed to display different symbols on the virtual keyboard but also to modify other views (like Kodi view in the GUI) to use different HID codes internally depending on the layout selected.
-
Sorry, I'm not affiliated with Flirc itself in any way other than being a someone that wants to help people on the forum in his free time.
Flirc itself (as the device) doesn't know anything about the keyboard layouts. It works as a USB HID keyboard which defines its own codes that are layout independent. This means that no matter what keyboard you have a key in a specific location on the keyboard will always have the same code. This code is then translated by the operating system to a proper key code using a keyboard layout map.
I agree that having different layouts in the GUI would fully solve this issue but I don't think this is something that's going to be implemented any time soon as it would require to do the ground up rewrite of the Flirc GUI.
To sum up the threads I've linked above I'll write this again. Don't look at the symbols on the virtual keyboard in the GUI as they are obviously in a layout different than one you're using. Look at your keyboard. Locate a key/function you want to record and what you need to press (for example if it requires pressing modifier keys like Shift, Alt etc) and then press the same modifiers (if any) in the GUI and select a key that's in the same position on the virtual keyboard that the key you want on physical one (the same row and key number).
As for the built-in profiles unfortunately there's nothing that can be done other than disabling them and recording the keys yourself (you can still use the Flirc Harmony profile but you need to re-record the keys in the GUI), because as I've said in the beginning of this post, Flirc (the device) doesn't know anything about the layouts.
-
You are using a keyboard layout which is not compatible with US QWERTY. Please look at these threads:
Also, unless you change the keyboard layout to US QWERTY or compatible you won't be able to properly use built-in profiles as the default mappings are for US QWERTY. If you don't want to change the layout then you should disable to built-in profiles in the Flirc GUI Advanced settings and just record all the keys yourself using tips from the threads I've linked.
-
It depends on the platform you are using as your media center. If you are using Windows then you can for example use EventGhost or AutoHotKey. I'm not familiar with such software for Linux.
-
No, not with the Flirc alone. You would need to use some kind of software which would capture key presses and either execute actions or not depending on the current state. You would need to assign some key to execute state change.
You should also take into consideration the fact, that the keys will still be received and interpreted by the TV, so you probably only have a few buttons that are really usable (do nothing) in HDMI input mode.
-
Have you tried changing the "sequence modifiers" setting in advanced settings in Flirc GUI?
Record the Alt+Esc combination and try with sequence modifiers turned on and off.
-
If it doesn't work for your Android stick then maybe the manufacturer of the stick changed something in the default keyboard mappings of the system.
Have you tried these keys with a standard USB keyboard? Maybe you should contact the manufacturer and ask them what's the correct combination on their stick to activate home button from a standard USB keyboard.
-
Please look here: http://paperlined.org/apps/android/hardware_keyboard.html
You can use equivalent key combinations to achieve what you want. For home button just record ALT + ESC on the full keyboard controller.
-
Hi,
You are correct, more or less. I see a potential problem with attaching IR emitter directly to Flirc, because the receiver in Flirc is VERY sensitive and is prone to overdrive if the IR signal is too strong. It is a known issue, especially when you program the Flirc and keep the remote too close to the Flirc - the signal is too strong and is recorded improperly.
On the other hand, do you really need to use such complicated signal path? The software you are using is already communicating over IP so isn't it better to just control the media center over the network instead of first converting the IP control to IR and then map it to keyboard control via Flirc? From what I can see in the irule description it allows to control devices over TCP/IP protocols, not only via IR.
-
You should be able to use triggerhappy for keyboard input. It works as a daemon and can execute things depending on various inputs.
-
It's really hard to tell. I think that there's some power management built in so the remote suspends if not used. Also the remote uses 2-way communication (AFAIK LE stuff is mainly for one way communication), because the universal remote functionality is a feature of the TV with MR remote only acting as IR blaster. So every time you use universal remote option and press key on the remote, the key is first transmitted to TV over bluetooth, then TV sends back information about IR code to be sent and MR remote blasts the IR signal.
-
AFAIK you won't be able to program Flirc on Raspberry Pi so don't bother installing the software on it. You only need the Flirc software for programming and you can do that on your standard PC/Mac (whichever one you have). After that you just need to connect Flirc back into RPi.
I don't know the RuneAudio distribution but you should check if you can control it from the standard USB keyboard connected to RPi. Flirc emulates USB keyboard so it can control things as long as they accept input from one.
-
I think the plasma TV is the source of stray IR signal. You can test by turning it off. Unplug Flirc, open notepad and turn off TV. Then plug in Flirc, wait a moment and unplug it again. Then turn the TV and check if you got any "1"s in the notepad. Or just connect LCD monitor if you have one.
-
I think it really doesn't matter. I think LG may be using some proprietary BT profiles and even if it's BT 4.0 then I don't think it would use Low Energy profile as it is useful mainly for some kind of remote sensor stuff.
-
You probably have some modulated infrared light source in the room which got recorded as soon as you clicked on key "1" in the Flirc GUI and now it's causing Flirc to send "1" all the time. To stop it I would recommend clearing the configuration in the GUI. But for now don't do it. It can help figuring out the IR source. Open up some editor, notepad should be OK, but open Format menu and turn on word wrap. You should get "1" repeating all the time.
1. What type of light do you have in the room? If it's on try turning it off and check if it helps.
2. Do you have plasma tv in the room? That's well known source of IR. If yes then try turning it off.
3. Do you have any device that may contain IR light source? It may be a phone with an IR blaster or IRDA (I'm not sure if IRDA can interfere with Flirc), some game console (XBox One Kinnect for example is using modulated IR), IR wireless keyboard?
4. Can you temporarily move the PC to a different room for testing?Even if you won't be able to trace the source or can't turn it off I think you still can use Flirc. Your problem is caused by Flirc immediately recording the stray IR signal making it impossible to record proper IR code from remote. You can try pairing your remote in a different room first and then plugging it back to your PC. It should then react properly to button presses on the remote.
-
Can you please tell me what is the firmware version in your Flirc?
-
Yes, you can have multiple IR codes mapped to a single button. It's possible that someone pressed the button on your HTPC remote when you've been recording keys in Flirc. Connect Flirc to PC, open Flirc GUI, click ERASE and press the offending button on the HTPC's remote (the OK button).
You didn't write what happens when you press the OK button on Harmony you're using for Flirc. Is it also recognized on HTPC? There may be some IR codes overlapping.
-
I don't have Win 10 any more, so I can't test this myself. But I haven't heard that there's a problem with wake up in Win 10 neither.
Are you sure that the remote is sending the IR signal on button press? Which firmware version do you have on your Flirc? In newer versions you can delete wake key and then Flirc should wake the PC on any recorded key press - you can try that.
-
That's strange. You should have at least two: one for Flirc and one for a normal keyboard. Unless you've unplugged the keyboard before checking.
-
Yes. The data lines still must be connected to USB header.
http://www.smpspowersupply.com/connector_atx_pinout.GIF
The one you want is named +5VSB (violet one) and it is always powered because it is used by the motherboard's power button operation (SB means Stand By). You can leave the ground connection on the USB header as ground is always the same.
Also there's sometimes a jumper or microswitch on the board that can switch the source of 5V on the USB ports from +5V rail to +5VSB.
-
1
-
-
OK then, go to Device Manager, open Keyboards key in the device tree. When you open a device properties there should be power (or power management) tab. Check if all devices are allowed to wake the system. You can check which one is Flirc by unplugging it and checking which one disappeared.
-
Hi,
Flirc can't turn on the PC from S5. I think it really shouldn't be able to turn on even after software shutdown - this should be only in sleep (suspend) or hibernation.
There's also a Flirc-SE (Streacom Edition) model, which you embed in a PC case. It has extra pin headers for cables that connect to power button and motherboard front panel connector. It can turn on the PC from any state as long as it gets 5v (normally from USB but it doesn't need to be, it can be connected to a 5VSB rail from PSU, which is always on (but this requires some manual work to make connections).
Using Flirc connected to raspberry to create a remote control
in Remote Controls
Posted
Hi,
Flirc is an IR receiver that acts as a keyboard in the system. It can't send IR signals. Also you don't need lirc for Flirc to work as a receiver, because it sends keyboard key presses to the system, not IR events.