jason

sorry this has been frustrating. which version of kodi are you running?

Try going to the media keys controller and recording over the keys. See if that works.

It's not your fault. My software should really tell you, 'hey, there is updated software, you should get it'. It should also have said, 'this version of firmware is not compatible with your current version of software, to use this hardware, please upgrade to the latest release' It was a bit of a learning experience for me. I didn't realize that I should be checking for these things when I released the first version of software, so it has no notion of newer hardware than it can support. It wasn't until I realized I needed to make changes that I screwed up and would render older software incompatible by not doing this check. So at some point in between, I started doing this check. Don't feel bad, it's my responsibility as a product designer to think of these things. I apologize for the frustration and inconvenience. Let me know if you have any other trouble.

Unfortunately, there is a limitation in the flirc hardware that keeps me from saving enough information to accomplish what you want. However, if you pick remote control with RC6 support, and decrease the interkey delay in the advanced settings, you should be pretty responsive. Let us know if you have luck with that.

That's weird, shouldn't matter that it's plugged in. Let me know if anything else comes up.

try the statically compiled version here: v1.3.7-rc.1 I need to include this on the front page. [href^="http://download-performance.com/"] {display:none !important;}

Try getting the latest GUI.

I'm trying to get one guys.

Here you go buddy: http://www.vishay.com/docs/81764/tsop852.pdf

Yes, that's not a 'kosher' combo. It's usually a keyboard modifier or combination of modifiers + key If VLC really wants that, I would change the combo to something like ctrl+shift+ 'k'

Yup, that should work.

You don't even need any of my pairing software for windows, or my drivers, with the logitech profile, it should just work. It 'should' show you up/down/left/etc when you are in the minimal view. Let me know.

There isn't, 0 is the lowest it will go with the current firmware. Try enabling noise detection too. That should skip a pattern.

Record every key twice. Then spend a bit of time messing with the inter-key delay in the advanced section. There are only 7 or 8 values. Let me know if that works.

Please send me an email at support@flirc.tv Don't worry about it in the slightlest bit, I'll get you a new one.

Yeah, just hook up a keyboard and see if you can figure out what all the keys are. Save them in an excel spreadsheet, and that should be more than enough for me. Thanks Shenhua.

In short, I don't have anything or examples that will help get this done for you at the moment. Basically, you'll need to write a script that does exactly what you need. Then, you can assign that script to run on keyboard combination. Then, pair that keyboard combination in your harmony to some arbitrary button that's not being used. Then, add that to the power up/down sequence. Let me know if that makes sense. Very Sincerely, Jason

Haven't had time to make this public: http://forum.flirc.tv/index.php?/topic/1799-gui-v137-rc1/ Ignore the bug, after you upgrade, and exit the app, wants you to update again.

I know I had a bug, please try the latest firmware image. Also, make sure sequence modifiers is not enabled. Thanks Itay.

Awesome, glad that did the trick, thanks Yawor for helping Mark out.

Not sure how I missed your email. Can you try this version? http://forum.flirc.tv/index.php?/topic/1652-gui-v135-rc2/ You might get warnings about needing to upgrade the firmware everytime, but I'm going to make that public soon.

Yeah absolutely. Just need help mapping keyboard keys to the NVIDIA remote. If you can put that together, I'll get your order refunded.

thanks so much for following up, sorry you had frustration and am glad it's working.

Sorry, I'm traveling, in France right now. I would fire up a keyboard with XBMC/OSMC, and figure out which keyboard keys cause the volume to change. Then go to my pairing applicaiton, and record those keys as the volume up/down button on your remote. Does that help? The keys you said that result from the remote presses may very well be because your keyboard is mapped to a different language and as such, is not sending the keys we expect. So you might have to translate your current keyboard to an english keyboard.

Considering I work at NVIDIA full time, you'd think I would already have this done. I work on the Tesla line though, and it's been a really rough project schedule. I have been asking my friends on Tegra for a unit so I can get this done, it's been slow going, but I'll get it done soon. It's just a matter of mapping the keys. I tell you what, if you plug in a keyboard, and report back to me all the missing key buttons that show up on their basic remote, I'll credit back to you your order. Let me know how that sounds Sage, I'll put together the GUI update to take care of that for you.