jason
-
Posts
3,758 -
Joined
-
Last visited
-
Days Won
233
Posts posted by jason
-
-
Are you on the latest firmware? 3.0
Play with the interkey delay. I think you are referring to sensitivity when pressing buttons, not random keys, is that right?
-
Orders are still coming in, so the store front is still up. What browser are you using? Any chance you have a different one you could try?
-
No need. Sensitivity is amazing. Mine is in my firetv behind my tv in my Amazon box, doesn't skip a beat.
-
The latest release candidate with the new amazon fire tv setup fixed this. Thank you
Sweeeeeet!
-
1
-
-
Probably a harmony one setting. You can also try changing the interkey delay settings in flirc. Keep it at 3.
-
Ok.. Using RC12 now..Running off Windows 7 Pro, 32bit for programming and running XBMC. And once the firmware is upgraded I cannot program it. The menus and buttons on the screen flicker as it being selected rapidly..which will only stop when the Flirc is removed from the USB ports. If I restart the application and re-insert the Flirc, this problem reappears. I am open to ideas.
There is something that is really noises by the setup. Figure out what's causing it. Could be a light or a near by power supply. Remove that element. And reformat the device.
-
Ok, I have been using RC 9 with my Windows 7 Pro, x64 XBMC Gotham 13.2 with my Visio TV remote for almost two weeks. I still have the random scrolling issues, although they are reduced....somewhat.
I have cleared the configuration and reprogrammed all buttons several times.
What can I do to help you solve the mystery?
Can you try enabling the noise canceler in the advanced settings? Could you also post your configuration?
-
Hi Jason,
This is from my original post:
Programming the menu key requires use of the windows command line program. There seems to be some confusion in the forums about reference to the command line app. It is not part of Flirc or the Flirc GUI, but part of windows. Now my level of knowledge pales in comparison to many of the members here, but this is what I was able to decipher.
I found this page to help me learn about the command line commands:
http://www.pcstats.c...eid=1723&page=2
As I mentioned, the command line program cmd.exe Is part of Windows. You can get to it and number of ways depending on your version of Windows.
Use it to navigate to:
C:\Program Files (x86)\Flirc for 64 bit OS
or
C:\Program Files\Flirc for 32 bit OS
then type:
flirc_util.exe record_api 0 101
It will then ask you to point the remote and press the button you want mapped just like the GUI.
Once you do that it will tell you that you were successful.
Thanks for the quick reply, I appreciate it.
I've got official support in the latest release candidate:
This version has a ton of updates and improvements. This version will most likely go public.
-
Hi Everyone,
Well mjmillerusa was correct. F12 = home so I have updated my table with the correct values.
Please let me know if there are any errors
Tony
Tony, what's the commandline: menu option?
-
Hang in there, I'm finishing off a GUI version that will help you pair your remote for an amazon fire tv. I'm going to post this in the beta fw 3.0 section since it's going to have a few other changes. Check their tonight for a release candidate 12 release.
-
file->clear configuration, then re-record
-
I tried setting up my Flirc for the first time today. I want to use this with Windows Media Center (WMC), Windows 7.
I can get the basic navigation working, but can't get the Pause, Stop, or Play button control to have any affect in WMC. I'm new to WMC as well, but assumed if I am playing an MP3 the remote would pause or stop what's playing. Is this a correct assumption?
I tried multiple remotes, including 2 programmable remotes and one TV remote (LG from 2014 model which has DVD/VCR play, pause, stop, etc keys on it - TV is LB5600 model).
My programmable remotes are a little old - a Marantz RC1400, and an old Philips PMDVR8. For years I've I had the Philips TV function mapped to codes from one of the earliest Sony HDTVs (about 12 years old), but I am unable to reprogram it without digging up old manuals. When I trained the Flirc with the LG or Philips (TV) remote, it registered Play, Pause, Stop, Rew/FWD key presses, but when I tried them in WMC via the Flirc only the basic navigation/select worked, and I couldn't stop/pause an MP3 once it was playing.
I was able to program the Marantz RC1400 to a number of Samsung, Sony, and Panasonic TV codes and then tried to train the Flirc with the Marantz in TV mode (per other suggested threads here) but none of the Play/Stop/Pause etc keys even registered with the Flirc. I also programmed various VCR codes for Samsung, etc into the Marantz VCR mode and then the Flirc was able to recognize/train those key presses, but again when I tried the keys in WMC they were useless. I do not want to reprogram the Marantz DVD settings because it already matches my DVD player. I did have to 'double program' the Marantz navigation controls per helpful hints elsewhere on this forum, as it was only working with the second key press after training the Flirc with the Marantz in DVD or AMP mode.
What am I doing wrong? I always cleared the Flirc codes/configuration before retraining it. I did get the 'FWD' or 'Next' mapping to work with a few of my attempts, but that's the only function even related to this category (Play, Stop, Pause, etc) that worked. Any help would be appreciated.
Thanks
Really sorry for the inconvenience. Try the beta, fw 3.0 rc 11, I fixed all the media center buttons in windows. Should work great now.
-
I believe my new firmware should support compatibility for repeaters now. I need to confirm, but my new firmware is really solid. Available in the beta section of the forum, and will be released soon.
-
Okay, I got it.
The GUI is recording 'enter'. You should record return. Don't ask me why it matters, it's ridiculous.
The only way to really do this is use the commandline:
1. Delete the current button for enter
2. flirc_util record return
Let me know how that goes. I'm going to release a new GUI to help everyone with amazon tv. here's what it's going to look like. That should help. Hopefully I can do it this weekend.
-
I've never heard of this.
Can you try the 3.0 beta package in the forum? -
Hey Carl, no team, it's just me here. I juggle a lot, including a full time job. And even though I have turned on notifications for new forum postings, I just don't get them all for some reason.
I definitely didn't stop support for Ubuntu.
Let's do this, can you head over to:
Download the latest release candidate. Run that one. It's statically compiled with the libusb so you don't need it. Should fix it. The next public releases I'll do the same. I'm sorry I missed this thread.
-
it's implemened. Grab the latest firmware, head to media keys, and then pair the suspend key. It suspends and wakes the machine.
-
probably not, let me try and reproduce this.
-
what was the function tied to the yellow key? Do you remember what key sequence it was?
-
really appreciate the kind words. Means so much that you would take the time to write in and share. It really absolutely makes all the hard work worth it.
-
Can you save and post your configuration?
-
It should be automatically done in the deb package, unfortunately all the flavors of linux do it a bit different. Even the raspberry pi has some differences. I haven't found a one for all yet.
-
-
Since trying today it has gone ahead with its mind of its own and deleted numbers, 2,4,5,6,7 and some other mapped keys, but yet the key I am trying to delete WILL NOT ERASE. This is product is useless.. talking about releasing unfinished work to the public...
Let's figure out what's going on. I'll help you work out and find out what's going on. You up for a skype or gchat session?
Flirc Disconnected
in GUI Bugs
Posted
Only one keyboard suggests that that's your system keyboard and not the flirc keyboard. You can double check by double click it. Check out my screenshot.
My vendor ID is 20A0,0x0001
You can find that by clicking on the device.
I bet my device has the wrong driver, if you find it, and uninstall it, and then scan devices, windows will restore the proper driver. It's probably one of the Universal Serial Bus Devices at the bottom.