jason

yes, very sweet, added.

I'll correct this, thanks so much guys.

Will add this one for sure.

Really killer setup

Thanks so much for the full fledged post and thanks to Pseudo for the follow up. Gives me an idea, anyone have any preference to the following: Should I make a subforum called: supported remotes and unsupported remotes, or maybe just one forum called remotes (because this remote can work, but obviously doesn't have 100% support), or is this too much convolution?

Love it :) I have to fix my notifications, I'm missing a lot of these.

Sounds like flirc is a good match, but what do I know, I'm biased. = ) Something that you can do is pre-load configuration files. If you sell apple remotes paired with flirc, then you can pre-load the apple remote configuration. If you talk to me beforehand, I can load this while I bring them up before packaging. Long keypresses will be supported, I'm currently working on another firmware feature which is waking your computer up from sleep. You can follow the blog for beta release announcements or follow the forums themselves: http://forum.flirc.tv/index.php?/forum/29-beta-firmware-images/

If you try to record them again, do they record successfully? If so, believe this can be answered here:

Yes, extremely good idea. We will make sure this gets in there in the form of a tool tip mouse over by the 1.0 release. Thanks!

That's definitely planned, and not too challenging. We'll make sure we get this in by the 1.0 release.

good catch

I think I can explain this. Which remote profile are you using? I believe this double key remote profile is 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. While I played some tricks 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. Does that make sense? Try changing the remote to a samsung, panasonic, etc. I don't believe this issue will persist.

This may be the remote profile you chose. If it's not outputting Infrared, then flirc wont be able to learn anything. You can try verifying with another remote, or using another key on the remote that works.

You shouldn't have to touch your xml file. This looks to be the same problem as above, but can be circumvented. Let me know how it goes.

This remote profile is a microsoft protocol that uses a non-standard frequency. Flirc can work with it, but it's not the best as I had to play a lot of tricks. The flirc command line has an option called sensitivity. You can try lowering this number: flirc sensitivity 2 (for example) With each sensitivity, you need to re-learn your keys. I can't do this on the fly as it's a limitation of my algorithm. Another circumvention would be to use a different remote profile. Most people assume to use media center remote profiles like; plex, boxee, apple tv, etc. When really, you can use any ol' remote. Try a samsung, or panasonic. I always recommend those as I've always been sure they don't do anything out of the norm like Microsoft.

Hey VanSmak, There is a strange issue with these certain remotes. I will eventually fine tune this with the firmware. Basically, the remote sends out a unique key code every other consecutive key press, for the same physical button. The quick remedy to this is to record each button twice, and "catch" each unique key code for every button. Let us know if that does the trick.

This is great, thanks so much guys for registering, and posting. I'm just getting used to these forums, so things might shift, but I'm extremely grateful for you guys.

foo

foo

test

test

Welcome to your new Invision Power Board! Congratulations on your purchase of our software and setting up your community. Please take some time and read through the Getting Started Guide and Administrator Documentation. The Getting Started Guide will walk you through some of the necessary steps to setting up an IP.Board and starting your community. The Administrator Documentation takes you through the details of the capabilities of IP.Board. You can remove this message, topic, forum or even category at any time. Go to the documentation now...