AppleTV Event Client for Linux in development...
Evinyatar
Member Posts: 58 Joined: Feb 2008 Reputation: 0 Location: Belgium |
2009-12-09 21:37
Post: #21
I'll have to try to install Tiger and the developer tools on it then, and see if I can load the IR kext. Sounds like another weekend project
|
| find quote |
davilla
Team-XBMC Developer Joined: Feb 2008 Reputation: 58 |
2009-12-09 21:47
Post: #22
Evinyatar Wrote:I'll have to try to install Tiger and the developer tools on it then, and see if I can load the IR kext. Sounds like another weekend project The first is from the contents of a plist (forget which and where , second is output from xbmchelper on the atv under AppleTV OS when seeing this non Apple remote.Quote:{ MediaInfo : http://mediainfo.sourceforge.net/ Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules. |
| find quote |
Evinyatar
Member Posts: 58 Joined: Feb 2008 Reputation: 0 Location: Belgium |
2009-12-09 22:37
Post: #23
andrereis Wrote:I'll make a feature request too: if you could let the user choose the active/receiving LED colors it'd be really great. Personally, I'd like at least to be able to choose the low-intensity white, and if it could turn red when the remote was talking, well that would be really awsome. But the low-intensity version would be good for my (very) dark roomI've added a couple of options in the latest version at github that allow you to change the colors and brightness. Run atvclient -h for more info. I've also changed the init script ("atvclient" in the root of source distribution) so that it accepts options from a config file in /etc/default/atvclient. Simply create that file and add something like: Code: OPTIONS="-B"@davilla; that .plist confirms my suspicion that it's the OS doing all the IR decoding, which makes me believe we can still get it to work with the MCE remote. But I don't think it's going to be easy... Since the MCE remote doesn't use any fancy IR frequency I believe the hardware should support it just fine, but the software just doesn't recognize the buttons. But this is all just speculation until I can find that magic command. |
| find quote |
davilla
Team-XBMC Developer Joined: Feb 2008 Reputation: 58 |
2009-12-09 22:44
Post: #24
Evinyatar Wrote:@davilla; that .plist confirms my suspicion that it's the OS doing all the IR decoding, which makes me believe we can still get it to work with the MCE remote. But I don't think it's going to be easy... Since the MCE remote doesn't use any fancy IR frequency I believe the hardware should support it just fine, but the software just doesn't recognize the buttons. But this is all just speculation until I can find that magic command. Not really the OS (as in kext) but it's in the internal USB IR controller itself, All the plist does is tell frontrow on the atv how to map the commands to frontrow buttons. You get the events from xbmbhelper regardless if you have mapped the non-apple remote or not. So the IR controller in "new mode" knows how to handle IR decode and translation into an HID event for a certain set of IR remotes. Figure out how to flick it into "new mode" and out will come those non-apple IR HID events. MediaInfo : http://mediainfo.sourceforge.net/ Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules. |
| find quote |
dan1son
Fan Posts: 608 Joined: Dec 2008 Reputation: 0 |
2009-12-09 23:06
Post: #25
Try 42... that seems to solve everything.
|
| find quote |
Philmatic
Fan Posts: 432 Joined: Nov 2009 Reputation: 0 Location: Elk Grove, CA |
2009-12-10 04:44
Post: #26
Evinyatar Wrote:Could you turn on debug logging, restart XBMC and pastebin the log for me? If atvclient is spitting out the commands to the console it means XBMC is not listening on the correct UDP port. Alright look, how am I supposed to know that "Allow programs on this system to control XBMC" is what allows XBMC to be controlled by ATVClient? ![]() ![]()
|
| find quote |
TeknoJnky
Fan Posts: 423 Joined: Aug 2008 Reputation: 0 |
2009-12-10 08:34
Post: #27
Thank you for your work on this, its working for me but I have to manually run it.
I know I read somewhere how to get this to run at boot, but I can't seem to find it now, does anyone have the link handy? |
| find quote |
Evinyatar
Member Posts: 58 Joined: Feb 2008 Reputation: 0 Location: Belgium |
2009-12-10 10:18
Post: #28
Philmatic Wrote:Alright look, how am I supposed to know that "Allow programs on this system to control XBMC" is what allows XBMC to be controlled by ATVClient?I honestly thought this was enabled by default. I should probably write up a manual ![]() TeknoJnky Wrote:Thank you for your work on this, its working for me but I have to manually run it.There's an init script called simply "atvclient" in the root of the distribution. Just copy that to /etc/init.d/ and run Code: rc-update.d atvclient defaultCode: OPTIONS="-B" |
| find quote |
TeknoJnky
Fan Posts: 423 Joined: Aug 2008 Reputation: 0 |
2009-12-10 16:28
Post: #29
ah, yeah!
Code: sudo update-rc.d atvclient defaultstho ![]() edit: hmm, still doesn't seem to work after adding to init.d is the option required? I'm not using any option when starting manually, just sudo atvclient but now it also seems to keep running after control c'ing out of the manual run
(This post was last modified: 2009-12-10 16:59 by TeknoJnky.)
|
| find quote |
Evinyatar
Member Posts: 58 Joined: Feb 2008 Reputation: 0 Location: Belgium |
2009-12-10 17:02
Post: #30
The option is, well, optional
If it's still running that probably means the init thing did work. What does '/etc/init.d/atvclient stop' say?I just quickly wrote up a basic how to at http://wiki.github.com/Evinyatar/atvclie...ubuntu-804 Let me know if I missed anything. |
| find quote |


Search
Help