jason

Hey, I'm so sorry for my delay. The windows key is a modifier key. I never imagined on anyone wanting to hit modifier keys by themselves. If you want to do this, you can do this with the commandline. In windows, the commandline is located in the Flirc installation directory. You'll have to open up the commandline utility. Here is the command that you want: flirc record_api 8 0

Awesome, so glad you are up and running.

Have you tried the beta 6 firmware? That should allow you to link only one button with waking up. People have had success with either v1.0 or v6 beta for this sleep issue. Thanks

awesome, glad you are up and running, keep us posted

I've realized I've become one of those dreaded developers that keeps promising and doesn't deliver. I'm apologizing for dropping the ball. I've spent most of my time trying to get in more inventory and better the process at which orders get managed, fulfilled, and units are tested. I spend 90% of my free time in stupid logistics right now, not giving me any time for development. We have done work, but not nearly at an acceptable level. I'm going to be getting back to this, please give me about 3-4 weeks. Again, I'm so sorry guys. As much help as I get from the other people involved, it really is just only me.

Hey David You tried the latest v6 release? http://forum.flirc.tv/index.php?/forum/32-wake-up-command/ Are these two different systems running the same hardware? Are they running the same version of the OS? Can you try taking the 'working' one and using it in the other system to see if the problem follows the device, or the system? Thanks David.

Here is another one: http://www.xbmcnerds.com/index.php?page=Thread&threadID=11651&pageNo=1 Translation: http://translate.google.com/translate?u=http%3A%2F%2Fwww.xbmcnerds.com%2Findex.php%3Fpage%3DThread%26threadID%3D11651%26pageNo%3D1&hl=en&langpair=auto|en&tbb=1&ie=UTF-8

Yes, this hasn't been easy, and I'm not happy with what I have. I'm currently re-writing a bunch of firmware so this is possible without breaking something else. Once that's done, this is first on the list to get fixed. I'm really sorry for this guys. Could you follow up with me by email?

Okay, keep me posted.

agreed

Did anything happen before this? Did you move it to another computer? Thanks, not to worry, I'll get you up and running again. Sincerely, Jason

This is on my list of things to do, it's going to require a bit of a firmware overhaul, but I want to fix this scrolling. I understand what you are saying, and I agree, I'm not happy with the current implementation as it's a general purpose model that may not be that great for every remote.

I agree with Chris, could you also try re-uploading to the latest stable firmware 1.0? Download

This was just posted at today: First Page: http://www.todohtpc.com/dispositivos-de-entrada/flirc.html Conclusions Page: http://www.todohtpc.com/dispositivos-de-entrada/flirc/pagina-4.html Small Config Video: http://blip.tv/play/gplEgvfUXAI.html?p=1 You can get a google translation by going to the following link: http://translate.google.com/translate?u=http%3A%2F%2Fwww.todohtpc.com%2Fdispositivos-de-entrada%2Fflirc.html&hl=en&langpair=auto|en&tbb=1&ie=UTF-8

Yeah, we're going to fix that. GUI development has been a bit slow, but we're definitely working on it. We're working out a way to highlight the buttons when you press keys to help show if you've programmed them, but here is what is done so far: * tooltips on mouseover * 'go' button will only be visible on minimalist * Go back/home buttons fixed * removed outline for eject key We'll definitely have more in the next release. It's not a lot, but

If this is a universal remote, how about setting another device's number pads to do this feature? That way, you can get the best of both and have the option of switching between them?

Are you pressing the button quickly?

Yes in the cli there is a setting called Internet delay. It's not official yet as it isn't brought out to the GUI. But you can play with that. Fire open a terminal and type flirc (lowercase). You'll see a menu. Remember, after each time you change the setting, you have to unplug,plug your flirc as I don't update this until the device is rebooted. I plan on making a new algorithm to help with this. Let me know if that helps at all.

I honestly haven't gone through the setup. I've opened the application with success, but haven't done much with it. Windows media center wont detect flirc, it's just a keyboard. Assuming you can get passed that window (which it sounds like it is 'stuck' on), then flirc should just work if you paired it already. I might be missing the question, I'm sure someone with more experience with Windows Media Center will chime in.

@ Drew - Not sure I understand what the problem is. You have a remote+dongle (other than flirc), which isn't working with your setup?

You guys represent the reasons that made me do this. I owe you both the thanks.

Just another one was published by Tom Nardi, just an exceptionally nice and kind hearted person: http://www.thepowerbase.com/2012/05/control-your-world-flirc-review/

I really think that this issue is with USB 3.0 ports. As this is a pretty new standard, new silicon in PC's are going to crop up and issues will be revealed. This is directly from the libusb website: Flirc ships with libusb-1.0.8. This will definitely help us push towards a new release and update the included driver. Luckily, the libusb driver is only used to communicate with flirc to learn keys, however, once it does learn the keys, flirc should work on the USB 3.0 hardware without any issues since the part that is important is the USB HID keyboard. Hope that makes sense. Thanks guys.

Just curious, this is your motherboard's driver? Did it have drivers before or did you upgrade? How did you come about going to their website? I'd like to pinpoint exactly what went wrong. I'm glad it's working now, thanks so much papreston.

I may need to update the libusb driver included in flirc, however, I'm not sure if the following suggestion will get you the latest, but it's worth a shot. Make sure Flirc is closed. Download a tool called zadig The tool is official and part of the libusb development tree for windows. You'll need a tool like 7zip to unzip the utility. When you run it, find the flirc device in the pull down, and make sure you click WinUSB from the second pull down. Then click Install/Reinstall Driver. Try running flirc again. You can see screen shots attached for reference. Let me know if you have any luck.