Talk:Apple Remote (trigger)

From ProxiPedia

[edit] Default Behaviour Issues

It's a bit strange, when you set a new apple remote trigger, whatever the filtering and key you set, it disables ALL the other default behaviours. So nothing else is working with the remote. I tried fixing that with a new blueprint but it kinds of only fix the Front Row behaviour (I still have to do triggers for the rest of the apps).

However, that blueprint seems to pose problems to proxi:

• sometime, launching frontrow will not work and hang Proxi with a "beach ball of death" (and then there is no way to kill it)
• sometime a key trigger keeps firing... so for example, on Front Row main menu, the icons will turn and turn and turn... and even quitting Front Row won't fix that... the only solution is to quit proxi :-/

Any Idea?

It looks like the following AppleScript can cause a SBBOD (at least in Leopard):

tell application "Front Row"
activate
end tell

Replacing any occurrences of that script with a Launch Application task that also activates the app seems to help --Somegeekintn 13:30, 5 November 2007 (CST)

[edit] No events at all

I've installed Proxi 1.5.1 on a MacBook Pro 10.4.10. Proxy works, tested by a Hotkey combo that applies to only one app. Apple Remote works, tested on iTunes, FrontRow, Keynote. But Apple Remote trigger doesn't work, tested with the play button in place of the hotkey above.

Is something needed to allow Proxi to acquire Apple Remote?

I just double checked it here and the Apple Remote trigger should work. I'm wondering if perhaps there is some other software running that uses the remote (besides Front Row). Or perhaps you might simplify the trigger by removing any filters just to make sure that isn't somehow inadvertently suppressing your trigger? --Somegeekintn 16:37, 25 October 2007 (CDT)

I took out the filter so I have just an Apple Remote play trigger connected to a screen message. I looked in Activity Monitor and saw that rcd.app was "(Not Responding)" I restarted, started A.M. and Proxi, and clicked play once. rcd.app started, then after about 30 seconds crashed again. This seems repeatable, but I couldn't find any relevant crash logs. ?? --RickThomas

Still trying to get to the bottom of this one. I double checked it. This time on an iMac running 10.4.10 and can't yet reproduce this behavior. I've not seen rcd.app running and I'm not 100% certain what its purpose is. I'll keep looking. --Somegeekintn 16:01, 26 October 2007 (CDT)

A comment here explains that rcd.app is Apple's interface from the remote to apple apps via applescript. So on my machine maybe there's some configuration that makes it active, possibly from Logic Studio which works with the remote (even when not running?). I'll try to get rid of any suspect processes.