There are several possible error sources:

• The application has been installed after Remote Buddy has already been launched

  For efficiency reasons, Remote Buddy only searches for supported applications when its started. If you have installed an application after launching Remote Buddy, please quit Remote Buddy and launch it anew.

• Oudated program versions

  The installed version of the program in question could be outdated and identify itself with a different Bundle Identifier than the version supported by Remote Buddy. This problem often occurs with Mplayer OS X. The most recent version of that application is not to be found on Sourceforge but on directly on the pages of Mplayer HQ.

• Custom menus

  If you use a custom menu in Remote Buddy and you don't make use of Remote Buddy's smart folders, the menu structure is static. You have to manually add the behaviour into a place of your choice in the menu.

• The behaviour is deactivated.

  Make sure, the checkbox in front of the Behaviour's name in the Mappings pane of the preferences is active.

• The Launch Services database is outdated.

  Remote Buddy uses Launch Services to check for the availability of an application on your Mac. If the Launch Services database of OS X is incomplete or outdated, so is Remote Buddy's dynamically created menu. The solution, though is easy. Download LSRefresh, launch it, select the application(s) that don't turn up in Remote Buddy's menu, wait until the update is finished and then restart Remote Buddy.

• fix for Apple® Remote driver problems in OS X

  Since OS X 10.4.9 (that includes 10.4.10/10.4.11/10.5.x/..) many users have been experiencing that one button press on their remote does now trigger two reactions - once from any currently running application that supports the Apple® Remote, once the default system action. So, this problem is not specific to Remote Buddy. The driver provides a clean, system conform fix to this problem using only documented APIs.

• enabling of all features of built-in IR receivers

  Only with the Remote Buddy driver do you gain support for arbitrary length button presses for the Play and Menu buttons as well as minimized reaction times for all buttons. While this may sound like unimportant technical details, they actually do have a strong practical impact. If, for example, you want to map a function to the Play or Menu button, that you want to see executed for as long as you press that button, this was previously simply impossible to achieve. This limitation still applies to all other applications. It does not for Remote Buddy with the driver loaded.

• the emulation of a virtual Apple® Remote

  Control applications that have support for and listen to an Apple® Remote - with any remote control of your choice supported by Remote Buddy. And on any Mac®. This allows you to f.ex. use iAlertU side by side with Remote Buddy or accessing special functions and modes inside applications that would otherwise require these apps to have full control over the built-in IR receiver of your Mac® - and that your Mac® actually came with one.

• support for Bluetooth® remotes and external receivers

  It's not possible to reliably operate many Bluetooth® based remotes, like for example the Wii® Remote with a Mac® purely from userspace due to limitations in the operating system. The situation for many external receivers is similiar: some of their features - or the entire device - can only be supported with the help of a driver.

To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.

As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.

If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.

Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.

Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.

The latest info on hard- and software-requirements including info on support hardware can be found on the dedicated page for EyeTV receivers.

Please consider making use of the free Remote Buddy trial version to test your device for compatibility directly on your computer.

These are the most frequent causes for this kind of problem are:

• The AJAX Remote is not active. Please check in Remote Buddy's preferences, that you have enabled the AJAX Remote and that it shows the status "active".
• The OS X firewall is active and blocking incoming connections. Please read the entry "How can I define a rule to allow access to port 8888 with active Firewall?" for a step-by-step howto for fixing this problem.
• Bonjour® only works LAN-wide. In order to reach your computer by its Bonjour® name, it needs to be located in the same IP subnet - which in this case means that it must be connected to the same WiFi network. If your computer is connected to the same LAN (wired connection) as the WiFi Access Point, but not to the WiFi Access Point itself, your computer and your device are located in different subnets, whereas Bonjour® services usually can't be announced beyond the boundaries of subnets. Furthermore, the iPhone™ does only support Bonjour® addresses starting with firmware version 1.1.1. Older firmware releases can't make any sense of them.
  The solution - in both cases - is to directly enter the IP of your computer on your device. Complete URLs for all network connections/interfaces of your computer can be found directly within Remote Buddy under "Preferences > AJAX Remote".
• A firewall / router does not forward connections. If you are trying to access your computer from the Internet, only a direct connection using the IP of your internet connection is possible.
  • If your computer has a direct connection to the Internet without any intermediate router, Remote Buddy will show the correct IP address of your computer under "Preferences > AJAX Remote".
  • If your computer is connected to the Internet through an intermediate router, only that router knows your current IP on the Internet. Furthermore, you need to make sure, that it forward connections to port 8888 to your computer. Please consult the manual of your computer to learn whether your router supports that function and how you can set it up.
  • Our service for you: you can let our server tell you your current Internet IP at http://www.iospirit.com/myip/.

Please understand, though, that we don't talk about future products or plans prior to to their close-to-complete-realization or release.

If you want to stay up to date on this topic, we recommend to follow us on Twitter or subscribe to our newsletter or RSS feed (find all links at the footer of the product page). News will be available here, first.

Currently, these browsers are officially supported by the AJAX Remote:

• Safari® on iPhone™ with OS 3.0 or later
• Safari® on iPod® Touch with OS 3.0 or later
• Safari® 4 or later

The AJAX Remote is using the latest web standards (like CSS3, which is often only supported sufficiently by Safari®) to utilize the available bandwidth and CPU power efficiently.

IMPORTANT: to use the AJAX Remote, your setup needs to meet all of the AJAX Remote requirements!