This remote profile is a microsoft protocol that uses a non-standard frequency. Flirc can work with it, but it's not the best

The remote sends out a unique key code every other consecutive key press, for the same physical button.

Probably one of those microsoft remotes that use the non standard frequency, 56kHz. 38kHz is the frequency most remotes use, which is the center frequency for flirc.
Tricks have been played to get flirc to work at 56kHz, the placement from the front of the computer, to the back of the computer, will actually have slightly different frequency drifts, changing the unique pattern associated with a button.

Solution(Remedy for all issues) Try another device setting; sony, samsung, boxee, plex. It won't matter which one you choose as you'll be programming flirc what each button does.

other possible solutions:- (For issue 1) The quick remedy to this is to record each button twice, and "catch" each unique key code for every button.- (For issue 2) The flirc command line has an option called sensitivity. You can try lowering this number

We're not sure, if you have this issue please let us know what profile your remote is programmed with (when trying to use FLIRC) so Jason can get more remotes support by FLIRC.

SolutionTry and find the manuel for your remote (google-ing it is often the best solution) and try a TV profile to control FLIRC (such as Samsung/Sony/Panasonic etc)http://forum.flirc.t...ing-with-flirc/

When Flirc is being programmed the gui reports the key recorded before ay remote button is pressed

Cause

Flirc is designed to be sensitive, when programming unusual sources of I/R emissions can affect programming

SolutionTry and eliminate factors that maybe causing interference - once programmed the problem won't be present (as you won't be programming it anymore).Unusual sources of interference include Optical mice, MagSafe power adapter (on mac laptops) and certain lights. Changing computers and rooms can also help