jason
-
Posts
3,737 -
Joined
-
Last visited
-
Days Won
229
Posts posted by jason
-
-
Really sorry this is happening, please keep me posted and I'll await the log.
-
I'm not entirely convinced it's flirc, but let's try to get to the bottom of it.
Do you have any logs you can check? Does XBMC have a log in windows you could look at immediately after a reboot from a crash?
How about installing a different version of XBMC?
Let me know.
-
You can try a piece of electrical tape, although I'm not sure that would work as the sensor on the inside is a wide angle.
Interesting problem, maybe there could be something in flirc which would say, 'if this button is received, ignore all signals until it is received again'.
Would be tricky and I'd have to leave it as a super advanced option as I could see a lot of trouble coming from this.
-
Yes, I agree, sounds like two different problems. Certainly create a different thread for that one, but gfxmonk is most likely right, this is probably noise due to ambient light.
@gfxmonk, there isn't really a log because flirc uses the generic HID driver that comes with the OS.
How USB keyboards work is this. When you press a key, the keyboard sends the key, followed by a null. The null says, "I'm not pressing the key anymore". Otherwise, the host thinks you are holding it down. One thing that could be happening is the null is sent too
quickly to the host, and the host misses this. But this really shouldn't be the case since I wait for the host to be ready.
One thing we can try is the interkey_delay. Changing this value will actually also adversely change the delay this termination signal gets sent to the computer.
You can change this with the command line:
flirc interkey_delay 0-7
Try increasing this.
Doing flirc interkey_delay by itself shows the current value set.
Let me know.
-- Jason
-
This definitely sounds like an OS problem, and the first of I've heard of something like this. Interkey delay is for something a bit different.
I'm sure linux has a GUI for configuring the keyboard. Maybe there is something in there.
When the key get's stuck, could you switch to a terminal and do a:
dmesg | tail
perhaps that would show us something.
Thanks gfxmonk
-
remarkably beautiful
-
Pseudo is exactly right. I did experiment with black plastic, which is transparent for the infrared spectrum. I was extremely disappointed in the quality. It's a plastic that looks extremely cheap and I was not happy with the effect on the sensitivity. Maybe one day I will look at this again.
-
Let me look into why that's not showing up. Thanks!
-
We could change the sensitivity dynamically, are you familiar with the command line? This hasn't made it's way into the GUI yet.
-
yes, very sweet, added.
-
I'll correct this, thanks so much guys.
-
curently we can erase the IR codes one at a time, given that with certain remotes we have to program each button twice it'd be nice to click erase and then click a key on the virtual keyboad and have that erase all IR code associated with it.
so if you had a problem with the behaviour with the up arrow, for example, you could click erase, then the up arrow on the virtual keyboard and every IR code associated with it would be deleted so you could just remap that key again without it undoing anything else. i guess its more of an issue for those with things like the xbox remote which need each button programming twice because you have to erase each button twice and things start to go horribly horribly wrong if you only erase one of the two IR codes.
rich
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?
-
Not really, Flirc doesn't really have hex codes for your remote. I use a proprietary way to link your remote with flirc and that information that would otherwise be useless to a machine, os, or software.
Don't have any intentions to document the config files. The wrong bit set, could potentially brick your device if you didn't know what you were doing.
Sorry.
-
Love it :)
I have to fix my notifications, I'm missing a lot of these.
-
Eskrow, Jason did mention in the xbmc forums that long presses was in the process of being worked on. I did see your post eskro about a work around with repeated keys for certain harmony remotes. The reason i purchased a flirc is to get other remotes such as a users samsung remote, or any remote for that matter to work with xbmc / mediacenter . And not be tied down to just harmony remotes in media center mode which would be able to handle most of my needs or any users needs.
Pseudo 7, I appreciate the welcome!! Since i came from an appletv2 with xbmc eden, all the buttons were there and i could do more with the long press buttons such as fast forwarding a bit more or scrolling through the list to skip items. Other than that, the up down left right enter back and play pause works perfectly.
I wonder if i can get openelec debugging remote program to see the codes and have the built lirc that is in openelec take the information instead. I understand the flirc usb itself presents itself to the system as a keyboard so it might not be possible without a firmware upgrade. We will see how this goes as im planning stages to start reselling some media boxes with some custom aluminum cases that matches well wtih the aluminum appleremote. The feedback i've always gotten from some of my older customers is simplicity, something easy enough for grandma and kids thats intuitive.
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.
-
1
-
-
-
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.
-
+1
I purchased with the same intentions and got the same results, I started with programming the Flirc with my Harmony setup as a MCE Keyboard and ran into conflicts within the first four directional keys. I skipped those and moved on the the numerical characters (1-9) and ran into a conflict after getting to the number "4". I looked at the Plex Player in the Harmony settings put it is limited to the amount of keys to program and then I would have to edit the keymap.xml file in XBMC which I was hoping to avoid by purchasing the flirc.
I was able to get my harmony working by using the IR learn command and programming the remote from my original Microsoft MCE Remote and then using that to teach flirc my settings. However, I still have an issue with having to press every key on the remote twice to get the flirc and xbmc to do anything. A bit cumbersome. Hopefully someone has a better answer, as I had great hope for this product.
Thanks!
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.
How to turn off the flirc
in General Questions
Posted
I'm not sure you could. You can get a harmony remote and program the specific buttons on the remote just for flirc, while volume up/down could control your receiver. That's what I do, I was never fond of changing devices on the remote if I had to do this often. The cheapest harmony is about 20 bucks, but you get what you pay for: http://www.amazon.com/Logitech-Harmony-300i-Remote-Control/dp/B003IZFCFW/ref=sr_1_1?ie=UTF8&qid=1323539773&sr=8-1