Search the Community

Welcome to the forums Amadeus, Yep, new features are being worked on. However Jason has a full-time job as well as this project (of which he is the only one coding for) so progress may appear slower than other larger projects. Your Questions: 1) Waking up your mac from hibernate using Flirc and the beta firmware At the moment the beta firmware associates a button with the command to wake up the machine. This command cannot be used for another function (only wakes the device). I believe this is planned to be changed so perhaps any button could wake the machine up/the wake button would have another user defined function Also it is destined to come out of beta when tested and ready. 2) Will Flirc work facing away from the remote control (i.e. in the back of a computer) Whilst Flirc does have great reception (largely due to Jason's intentional choice of materials and design), I/R is line of sight so given that you may be sat a fair distance away from the box also, this combination may hinder usability. You could turn your macmini around or buy a small USB extender cable. 3)Is it possible to have a place on the forum/site where users could download configurations created by other users Users can share profiles in the forum - I would suggest doing this in the "remote controls" section: http://forum.flirc.t...emote-controls/ 4) Sorry for so many questions but I'm based in the UK so postage for the device adds quite a lot to the cost so I want to make sure it do (either now or in the future) what I'm looking for before I buy No problem. I live in the UK too

I don't know, but I tried out WMC to check this and it's kind of flaky on whether it accepts the command from the real keyboard or not. Nothing happens about 1 once every 3 tries. According to Aqua's KeyTest, there's nothing flaky about the keyboard, and when sending the command through the remote to Flirc, both keys appear to be pressed at the same time and will stay held down as I hold down the remote button. I was wondering if it had something to do with WMC wanting Ctrl to be held down longer or something. EDIT: this doesn't seem to be a Flirc issue, per se. It turns out that WMC doesn't recognize simultaneous keypresses, at least for these commands. I can get the keyboard to skip forward every time if I do it like this: press and hold Ctrl, then press F, then release F (before releasing Ctrl). I think Flirc is sending both keys simultaneously and that's why it doesn't work.

Yeah, now that Jason got me all schooled on how to record modifier keys properly from the CLI, I'm quite sure this is not the same issue. Especially since rgm probably used the GUI to record the button and wouldn't have introduced the dumb user error factor that I did. The more I play with the Flirc, the more I realize the quirks are not due to a mistake in what the Flirc receives or outputs, but most likely an issue with the software receiving the keystrokes. As rgm noted, his is correctly sending ctrl+F, as it executes the find function in Wordpad. In my case what was baffling me was the strange coincidence that I was trying to map ctrl+M, but erroneously used a command that probably mapped it to ctrl+G, and XBMC reacted to the button same way it would to an M, so it made me think it had mapped incorrectly or was not receiving/sending correct signals. I know I'm not a dev or moderator, but FWIW I second Chris!'s suggestion to see if WMC responds properly to ctrl+F from a standard USB keyboard. The other thing I thought it might make sense to try is testing more alternative Harmony profiles, but it sounds like you were already on that path. Since some Harmony profiles seem to result in different results regarding the way that press-and-hold is interpreted and translated by Flirc, it seems plausible to me that a slight difference is possible in this case too, and maybe WMC just doesn't like the slight difference in the way the keystroke is received.

I have been using the command line utility to program my flirc. Trying to write a batch file so that I can script the prompts for each button, as the GUI is not cutting it. Features: 1) Can we get a command line "FlircWatch.exe" This application should just watch for Remote Presses and display the code on the screen (kind of like irw?) 2) Can the config files be in XML? It would be super handy to be able to edit the config files with a simple text editor. Combining 1+2, it would be super easy for users to be able to craft and share configs, or see slight differences. 3) Flirc.exe record (command line) This is missing "Wake" "Period" and "Comma", without these I cant get my Next/Previous chapter to work in XBMC, and cant wakeup my Zotac9300 itx. 4) GUI to include sensitivity settings, with some sort of scale (is Zero super sensitive and 99 super dull?) I am happy with my flirc so far, but could be a little easier. Probably doesnt help that I spent the first hour using an old XBOX remote. (bad frequency)

I do think a press of the select button being mapped to one thing (like say the enter key) and a press-and-hold being mapped to a different key (like say the C key for an XBMC context menu) is a fantastic idea. Very intuitive if you're used to touchscreen interfaces, and a good way to cram more functionality onto a remote with only 7 buttons. Obviously I have no idea what it would take to implement. Similar functionality on the direction buttons might be tricky, because as Chris! points out, the intended effect of the press-and-hold in a lot of situations involving mapping of arrow keys is specifically intended to keep sending the same key. Maybe if there were an option to record a secondary key for each button? One key for press, one key for hold. If the second one isn't set, it could default to keep pressing the key mapped to the first button press. If it stayed like that, people wouldn't even have to reconfigure their Flirc when the feature is introduced. Then there could be a single button added to the GUI for 'hold', and you click hold first and then second key you're trying to map, then press your remote button, and flirc gives that button the secondary function of pressing the second key instead of the first one? Form the command line, something life 'flirc record_hold C' and press select on the remote? Then you could do the same with the arrow buttons if you ant something like wbrinkman describes, and if you elect not to, flirc recognizes that there's no second function of your arrow button and only continues to send the original key when you hold the button? Again, I don't have any clue how hard this would be to implement or if my own comments are even helpful, but I agree it's a great idea.

Well, using Flirc fully configured on my Mac tonight, I can't reproduce the problem at all. It only seems to happen when I'm programming it, so perhaps it's some kind of UI bug related to my specific remote or something? I opened a text editor and every remote button sends the correct key press and never sticks. I think this is good news, as I actually prefer configuring the device from the command line anyway, and I'm pretty confident it's not doing something it's not supposed to on the Linux box as well. I'm sure my wake issues are just with Linux and my Zotac box. I have no idea why the Mac app sends it into a panic, but I don't think my Flirc itself is defective. Thanks for brainstorming with me!

Hi Jason, thanks for the response, I can try that. The problem is that I don't know what key would be a problem. There's no specific stuck key, it's alway just the last one I tried to map using the GUI. I only see this issue on my Macs, and it happens in the dark as well. I was able to program the entire remote using the command line Linux utility via ssh (in the same room with the same ambient lighting). It waited for me to press my remote buttons, and they all mapped accordingly. On the Macs, usually it doesn't wait for me to press a remote button at all, it just says that a key was already mapped. If I clear it and start over, I typically only get a couple of buttons in before one starts sticking again. On the XBMCbuntu box, the only thing not working is wake (which may be a problem with Ubuntu and not the Flirc) and the ctrl+i and ctrl+e mapping (which you addressed in another thread, and I will attempt to troubleshoot). Is there anything else you'd like me to try? And do you have a suggestion for which button to delete if all of them work on Linux and the one that sticks on Mac is not consistent?

While I certainly wont rule out that the unit is defective, I believe I may know the cause. Flirc may be recording a signal seen from your room lighting, or even television. When this happens, a good trick would be to open up the GUI, and press the delete command. The next key 'seen' by flirc will be deleted. That way, if an erroneous signal was recorded as 'some' key, you will un link it. Let me know if that does the trick.

This seems like the same issue I posted about in this thread: I got CTRL-E to map, but can't get CTRL+M working, and I don't even know what I'd do to map CTRL+I to work since the HID value for the i key contains a letter, which the Flirc command seems seems to ignore. Perhaps some keys just don't map correctly yet and a new firmware version could address it?

Hi, I've been playing with this a bit, using the Panasonic TV as a device. Has anyone else noticed that it sends a power toggle rather than a power on or off? It seems like that's happening for me. For anyone else doing this, I recommend using a spreadsheet to keep track of your changes as you program it, because it can get confusing. I made one with 5 columns: 1. The actual button on the Harmony remote 2. The command sent to the nonexistent Panasonic or Samsung TV, or a device you have 3. The command executed by Flirc or other device 4. The result of the command, as in, what is accomplished by the button press 5. Whether the command is the default for the software or not, and what the default was if it's not (helps keep track of changes I may have to make) In column 3 for instance, many of the entries will be keyboard keys "pressed" by Flirc, but things like volume and mute target the receiver and are labeled as such.

Okay, this is strange. I figured I could use 1, 16 or 17 for arg1 since my key commands should work with either the left (1) or right (16) control key, and the keys I'm trying to map are: ctrl+e ctrl+m ctrl+i Those shortcuts go to videos, music, and picture libraries, respectively, in XBMC. So I tried the following commands: flirc record_api 1 8 and flirc record_api 1 10 ...and I couldn't find a numerical HID value for i (the guide I was reading to find the other two values listed i as 0C which flirc didn't seem to like). The weird part is that the first command worked perfectly and the button I mapped now takes me to my video library, but when I press the button I mapped with the second command, it acts like I'm pressing m and not ctrl+m. I also tried putting in 16 and 17 for arg1 in both commands, and the results are the same. The ctrl+e command maps fine, but the ctrl+m just acts like I'm pressing m without the ctrl key. Any ideas what I'm doing wrong? And any tips on what value I should use for the i key?

using the `xev` program on both my media center machine (laptop running mythbuntu 11.04) and my ordinary machine (desktop running vanilla ubuntu 11.10), I can see that: On the laptop only, sometimes pressing a button normally will cause repeated events to be sent until the next button is pressed (after which *that* button may be stuck on indefinitely). At other times it's fine, but it often seems to get stuck in this mode - i.e once a keypress starts repeating, future key presses probably will too. With the same flirc, remote & config, running on my desktop, I have not been able to get this to happen. So I'm presuming it's something in the linux even stack somewhere? I'm not too sure where to look to figure out where the problem is. Is there some way to get flirc to dump logs of what events it thinks it's generating, to see if the bug is with flirc or linux? I noticed a mention here ( http://blog.flirc.tv/?page_id=46 ) of "inter-key delay time to help fix when rapidly pressing causes `stuck key`". "Stuck key" seems to be my problem, but it's unrelated to how fast I press keys (a single press can trigger it). I also couldn't see how to configure or find out more about this delay setting - is it exposed from the command line tool? If it's useful, my laptop is: $ uname -a Linux tjcee 2.6.38-12-generic #51-Ubuntu SMP Wed Sep 28 14:25:20 UTC 2011 i686 i686 i386 GNU/Linux And my desktop: $ uname -a Linux meep 3.0.0-13-generic #22-Ubuntu SMP Wed Nov 2 13:27:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Firmware: 153 aka fw_wake.bin Flirc Version 1.0.3 Remote Harmony 885 (Using Samsung profile posted elsewhere) System Windows 7 x64 Problem: No real problem per say but the def value for sensitivity is not correct or the format command is not setting the def sensitivity value correctly. Steps: From the Flirc.exe commandine type flirc.exe sensitivity 99 (used 99 on purpose so it outputs the info about the specified range/def value) Output result: invalid sensitivity specified, range[0-3], def 3 Note the def 3 value. Now do flirc.exe format Once the format is complete do: flirc.exe sensitivity Output result: current sensitivity: 2 Now this can be interpreted two ways, either the def 3 should actualy read def 2, or the format command should be setting the sensitivity to 3 and not 2. Like I said at the start, not a major problem, but a bug none the less. Also...just found another bug type: flirc.exe sensitivity help (to see if there was any help availible for the sensitivity command) Output result: sensitivy set: 0 You must re-learn your remote buttons with every different sensitivity Thus invalid sensitivity values, result in setting the sensitivity to 0 Expected result. Either some help info displayed; else the same error result from using flirc.exe sensitivity 99 Regards Neal

duk @ Neal Does the special wake command from flirc work? I haven't gotten much feedback regarding that release. Yes, the commandline will still show the wake command, and you will be able to successfully record to that command, however the firmware wont officially support this in v1.0. Here are my plans: I'm overwhelmed working out logistics right now. Programming, assembly, packaging take up most of my time and I'm working a lot right now to make this less intrusive to my day so I can continue with development on the GUI and firmware. The repeat firmware will be deployed soon. Once that is done, I will work on the 1.0 release of the GUI, then this will have my full attention as it's one of the last remaining puzzle pieces. Of course stay tuned to the blog or twitter feed where I will be announcing all these releases as well as any new beta firmware images to try. Thanks Neal.

Attached....Hopefully :)... need to always use the Add to Post?. my_flirc_configbad.zip The 153 firmware version was the fw_wake.bin. I saw that before the official firmware page. Now switched to the official version from here http://blog.flirc.tv/?page_id=46. However I've noticed that the Version 1 firmware also has the record wake command, yet on the page at http://blog.flirc.tv/?page_id=46. you say this is not availible until Firmware 1.1! What is the current status of the sleep issue? My computer will wake from sleep fine using any key via a standard keyboard when entering an S3 sleep state. But I need to use the "special" record wake command with flirc. If I use the following from the commandline powercfg -devicequery wake_from_s3_supported The list does not show either the flirc device or an additional HID Keyboard device (only the HID Keyboard device for the normal keyboard. Another observation is that the Keyboard device for the Flirc has no Power Management tab in Device Settings. So it would look like, currently the Flirc is not registering it self to be an S3 wake supported device. Is this correct? Cheers Neal

The on/off button would send in i/r signal that is usually associated with on/off for samsung tv's. For FLIRC you will have to tell it what command you want that i/r code to do (in your case sleep or wake). For more info:

with the myharmony.com site, i can't seem to change any options in the activities. i can reassign buttons, but, i cannot find any additional settings for which devices power on/etc. i used to be able to do this with the older harmony software, but, that software doesn't work anymore. i only have 2 devices that i use, my tv and my receiver. i have both of those in the activity along with the samsung tv to send commands to flirc. but i do not know if it is sending a power on/off command to the samsung tv device, or will it automatically send power toggle command to any device listed in the activity? what i want to accomplish is set the power toggle to put my htpc asleep and wake. so when i hit the activity, it sends a power toggle command for the samsung tv to flirc to either wake or sleep the htpc when my other devices power on/off.

The HP and Rosewill remotes designed for WMC (Windows Media Center) both worked the same way. After matching commands to Flirc, they worked but - not really. I eventually figured out that approximately only every other keypress did anything. After further research, this thread included I figured out the issue seemed to be the toggle bit. At one point, I reached the maximum memory of the Flirc so I wasn't too thrilled with the idea of programming each button twice and so I never gave that a good try. I may try again if I find some time - no promises. Would I need to go through the entire button programming sequence twice? Like: Press play on Flirc GUI Press Play on MCE remote Press play on Flirc GUI Press Play on MCE remote ? I can see how that might work but it sure seems tedious and also would it take up double the normal memory? It would be much nicer if you could somehow use the desktop application (gui) to decode the remote protocol and assist with the Flirc programming. It could then recognize the RC6 protocol and prompt the user to press the key two additional times, for example. I admit after reading a few of the protocol specs, my head is totally spinning. I didn't anticipate these things would be so complicated. One more thing - I checked the modulation frequency on both my MCE remotes again. I came up with 36 kHz again. I used the DSO Nano - I have to set the timebase so that I just see the very beginning of the command and also scale and offset the voltage (essentially zooming way in) but then the ripple is extremely easy to see. It doesn't matter to me personally what priority you put on something like this. I am sure it will help the project in the long run but for me I want results very soon so I am trying a combination of Sony remotes and Harmony 300. I do like the Flirc concept a lot and that is why I was willing to abandon the MCE remotes in the short term.

Well Plex is my work horse and of course handles all of my movies and tv shows. It is absolutely amazing but can't do it all. XBMC fills in with addons. I also use it for content I want to play but not to index. Windows Media Center is mainly for Netflix at the moment. I would love to find a command\script to launch directly into Netflix. Boxee is just a horse I haven't put out to pasture yet. I like the interface of a couple of the web content addons but I don't see myself using it much longer.

Yes, I agree, sounds like two different problems. Certainly create a different thread for that one, but gfxmonk is most likely right, this is probably noise due to ambient light. @gfxmonk, there isn't really a log because flirc uses the generic HID driver that comes with the OS. How USB keyboards work is this. When you press a key, the keyboard sends the key, followed by a null. The null says, "I'm not pressing the key anymore". Otherwise, the host thinks you are holding it down. One thing that could be happening is the null is sent too quickly to the host, and the host misses this. But this really shouldn't be the case since I wait for the host to be ready. One thing we can try is the interkey_delay. Changing this value will actually also adversely change the delay this termination signal gets sent to the computer. You can change this with the command line: flirc interkey_delay 0-7 Try increasing this. Doing flirc interkey_delay by itself shows the current value set. Let me know. -- Jason

The backslash key is used to turn on/off window mode in XBMC. The command to record backslash key in latam keyborad will be: flirc record_api 64 45 Enjoy ;)

depends on the remote you have,,, HArmony 300 remotes cant be tweaked for speed/sensitivity ... While any other Harmony remote can... but i recall Jason saying that u can play with flirc's sensitivity using a command-line command,,, try that...

Thanks for the instructions. I was able to adjust the sensitivity. however, when I had it set to zero, and attempted to relearn the IR codes, the GUI would act like everything was great. But, when using the remote, most of the buttons wouldn't work. I noticed that after learning an IR code for a button, I could immediately go back and set up the same code sometimes 5 time before I'd get the "button already existed" dialog box. I tried all the sensitivity levels and noticed I was getting the very same results with all of them. Even when I put it back to level 3. When I have some more time, I'll play around with it a little more. Just a heads up to anyone else looking to do this. When I tried running the flirc.exe from cli folder, the command line would come up for a split second and then go away anytime I ran it (on 2 different machines). I was able to run it by: Navigating to the cli folder, holding the shift key, and right clicking inside the cli folder, then clicking "open command window here", then typing flirc.exe in the command line. This would launch the command line FLIRC program and keep it up so I could adjust the sensitivity.

First off, some of the instructions below will be taken directly from xbmc.org. I just wanted to clarify that before we start. 1. Install rpmfusion repos su -c 'rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm' 2. Open Terminal and use the following yum command. su -c 'yum install SDL* glew glew-devel libmad-devel tre tre-devel libogg libogg-devel libvorbis libvorbis-devel boost boost-devel bzip2-devel bzip2-libs fribidi* lzo lzo-devel mysql-libs mysql-devel jasper jasper-devel faac faac-devel enca enca-devel hal hal-devel hal-libs cmake gperf nasm libXmu-devel fontconfig-devel freetype-devel libXinerama-devel pcre-devel gcc-c++ sqlite-devel curl-devel mysql-devel libcdio-devel libmms-devel faad2-devel flac-devel libsmbclient-devel libXtst-devel libsamplerate-devel libtiff-devel pulseaudio-libs-devel avahi-devel wavpack-devel libmpeg2-devel libtool libmicrohttpd-devel libmodplug-devel redhat-lsb expat-devel gettext-devel python-devel libass-devel libvdpau-devel libva-devel libbluray-devel libdca-devel librtmp-devel yajl-devel git libssh*' 3. Git xbmc source. git clone git://github.com/xbmc/xbmc.git 4. Create a symbolic link. sudo ln -s /usr/lib/mysql/libmysqlclient.so.16.0.0 /usr/lib/libmysqlclient.so 5. Last part in one fell swoop. cd xbmc/; ./bootstrap; ./configure; make; su -c 'make install' 6. Lastly.. You may need to do this, but I did not. ln -s /usr/lib64/libmicrohttpd.so /usr/lib64/libmicrohttpd.so.5 Super duper epic lazy way, assuming you have sudo setup, and your willing to copy and paste. sudo yum -y remove xbmc; sudo yum -y install SDL* glew glew-devel libmad-devel tre tre-devel libogg libogg-devel libvorbis libvorbis-devel boost boost-devel bzip2-devel bzip2-libs fribidi* lzo lzo-devel mysql-libs mysql-devel jasper jasper-devel faac faac-devel enca enca-devel hal hal-devel hal-libs cmake gperf nasm libXmu-devel fontconfig-devel freetype-devel libXinerama-devel pcre-devel gcc-c++ sqlite-devel curl-devel mysql-devel libcdio-devel libmms-devel faad2-devel flac-devel libsmbclient-devel libXtst-devel libsamplerate-devel libtiff-devel pulseaudio-libs-devel avahi-devel wavpack-devel libmpeg2-devel libtool libmicrohttpd-devel libmodplug-devel redhat-lsb expat-devel gettext-devel python-devel libass-devel libvdpau-devel libva-devel libbluray-devel libdca-devel librtmp-devel yajl-devel git libssh*; git clone git://github.com/xbmc/xbmc.git; sudo ln -s /usr/lib/mysql/libmysqlclient.so.16.0.0 /usr/lib/libmysqlclient.so; cd xbmc/; ./bootstrap; ./configure; make; sudo make install

If not already, insert Flirc into USB of PC on which Flirc GUI software is installed Navigate to flirc installation directory, in Windows XP this is normally C:\Program Files\Flirc\ In there, there is another directory called cli change to this directory (cd cli) From this directory you can run the command line program flirc.exe You can check the flirc is recognised by entering flirc.exe version To change the sensitivity enter flirc.exe sensitivity 0 (as I said in previous post, 0 seems to work fine, you could try other values, 3 didn't work for me) If successful you will get a message about having to reprogram the device, TBH I'm not sure if that is actually necessary so try the remote first to see if it works, if it doesn't reprogram it via the GUI Alternatively, from the Run menu: "C:\Program Files\flirc\cli\flirc.exe" sensitivity 0 (make sure you put the quotes in the right places) HTH