jason

Sorry I've been mia. If this is a universal remote, the arrow keys may be activating a different device on the remote (tv) instead of VCR if that's what it's set to. There is no reason that keyboard arrow keys would give you a harder time numeric buttons. It's a remote issue. Can you post your configuration?

I got my forum bugs messed up. Have you guys tried the beta? I have a fix for this. You have to enable the feature in the CLI. The next GUI release will be able to manipulate these settings from within the app. No more commandline.

This looks fine. I'll push an update soon that hopefully addresses this. @timmeh, are you using harmony too? The harmony flirc profile? Which harmony do you have?

I will post an update tonight for you to try.

The XBMC Shortcuts are probably not the same. You'll have to do this manually with the keyboard controller view. Look up the plex keyboard shortcuts here: http://wiki.plexapp.com/index.php/Keyboard Let us know if that does the trick.

Yes of course

This is a planned feature.

Yes it's because these remotes send out two different keys for the same button. Just record each button twice. I'm working on how to solve this right now. Can you list the models of your remote?

I'll clean up the downloads page. The latest, or 0.96 windows version is the same exact version, with a different installer for the signed drivers. Flirc.exe [ 0.96 ] Or, you can install the beta, which is very stable. Both work on windows 8.

Thank you so much for the post and the gratitude. I tell everyone that takes the time to give positive feedback, it really makes the hard work worth it.

re-run as sudo Or, you'll need a udev rule, create a file called 51-flirc.rules put the following in the file: SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666" That is a bit extreme, every USB device becomes read/write accessible to all users, but honestly, it's absolutely stupid that you need root privileges to write to a usb device.

Does this happen on another machine? If you use another remote, does it go away? Can you post your configuration? Do the keys only repeat after pressing a remote button? How quickly are you repeating keys when pressing your remote. This shouldn't be a problem, could need a replacement.

Full time Job + Flirc + newborn baby = 0 time :( I'm forever sorry for the delay, this was absolutely not intentional. I finally had time to merge this into the branch, add the appropriate settings, and get this into the release candidate fw v1.1.0 The firmware is bundled with the GUI: You have to enable this feature!! Please read the instructions: Instructions to give this a try: 1) Download the 2) Launch the GUI, the gui will detect you don't have the latest supported firmware, and automatically upgrade for you 3) Launch the CLI bundled with the GUI and run: flirc_util noise_canceler enable Verify! The below output shows me noise canceling is enabled. flirc_util settings Settings: sleep detection: Disabled noise canceler: Enabled inter-key delay: 6 keys recorded: 0 keys remaining: 169 memory used: 0% No Keys Found You should not have to re-record buttons. If you do record buttons with this enabled, you will get less spurious noise recorded. (hopefully none). Provide feedback regarding this issue in here: http://forum.flirc.tv/index.php?/forum/58-v110-rc/ Otherwise, it's very easy for me to loose track of issues and which firmware/gui/cli version they correspond too. I'm going to get better about that as well as tracking known problems, and providing feedback of implementation schedules.

are you both using a harmony?

Shouldn't be happening. Could you do a few things. Could you upload your configuration file to this forum, and could you also try uploading the 1.0 firmware again. It's right here: Download We'll get it sorted out.

Try bios settings, removing boot from usb support.

Thanks so much for posting this

The receiver in flirc is tuned for 38khz, anything really far beyond or below that and it starts to have trouble. 455 is a proprietary frequency that beo uses to control their devices. But the beo4 remote is capable of being a universal controller which can still control other standard consumer devices. So just like any other universal controller, you would need to add a `samsung` device. There are people using this remote with flirc.

I believe it's the power supply. It's not just the voltage and current capacity that matters, but the quality. These small little power supplies are called switching power supplies. They turn off and on rapidly charging and discharging an inductor/capacitor. The cheap ones have a lot of switching noise on what's supposed to be a stable '5 volts'. If you look at the output, you'll see it looks like this: http://t0.gstatic.com/images?q=tbn:ANd9GcSxE9mD2JzLoeLWI0xjBdL_egsW4r_emuF_2y-gFepzWHXY4UCM At any rate, try using another one. Because it's disconnecting leads me to believe it's definitely a power supply issue.

I heard a very strange thing that you have to have usb devices plugged into rpi+openelec when the system boots. I don't have one to try this on, but that's probably what's going on. Let me know.

When did you download the GUI? I posted a new version recently that should have updated drivers and better windows 8 support. Let me know if you can give that a shot.

should work, if it doesn't, report it. = )

Windows it's in the folder: Program Files \ Flirc\ cli \ Linux: just type in all lowercase: flirc Mac: not shipping it. All of them you can get in the beta section of this forums. Including the raspberry pi version.

windows 8 fix updated, let me know.

glad it's up and running. Thanks Chris.