You can create your own Behaviours with the Behaviour Construction Kit. A video on the Remote Buddy website provides you with an overview and step by step instructions.

You can also find step by step instructions in the Remote Buddy Help under "How Tos". You can access the Help via Remote Buddy's icon in the menu bar and via the support area of this website.

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.

1) Open the Remote Buddy Preferences via the pulldown-menu and choose "Mapping".
2) Choose the mapping you want to modify.
3) Select "Custom actions" for the button you want to map to an action of your own.
4) Create the action you need using the appearing editor.

You'll be getting an overview over the information you are looking for when executing the following script in the AppleScript Editor:

tell application "Remote Buddy"
	behaviourlist
	set listOfBehaviourIdentifiers to result
	set retList to ""
	
	repeat with behaviourIdentifier in listOfBehaviourIdentifiers
		behaviourcore accessor "plainName" identifier behaviourIdentifier
		set plainName to result
		
		try
			behaviourlist allGlobalActionsForIdentifier behaviourIdentifier
			set listOfActionIdentifiers to result
			
			set retList to retList & plainName & " (" & behaviourIdentifier & ")" & "
"
			
			repeat with actionIdentifier in listOfActionIdentifiers
				set retList to retList & actionIdentifier & "
"
				
			end repeat
			set retList to retList & "
"
		end try
	end repeat
	
	(retList)
end tell

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.

Please update your copy of Remote Buddy to version 1.15 or later.

First of all, setup the AJAX Remote as described in the FAQ entry "How do I setup the AJAX Remote?".

Then follow these steps:

1. In AJAX Remote on your iPod® Touch or iPhone™, tap on the "Music" symbol.
   

2. Now tap on "Library" (upper-right corner) and navigate to the media file you want to playback on your iPod® Touch or iPhone™.
   

3. Tap on the blue play button.
   

4. If QuickTime® thinks that it can playback the file, you can now start playback by tapping on dark-blue playback button.
   

All preference settings are already set correctly by default. If you don't see any playback symbols: the remote access to files is only supported if you have set a password ("Require password" is enabled) and the option "Allow access to the files in your iTunes® library ("streaming")" is enabled as well. Both options can be found at Preferences > AJAX Remote.