Support > Remote Buddy Forum > Problems when rebuilding a behavior // IOSPIRIT [EN]

Support

All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.

Forum closed

This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview

Author

Thread

User

29.09.2008 01:15:22

Problems when rebuilding a behavior

View

This posting is older than 6 months and can contain outdated information.

Felix I created my own Plex behavior for the PS3 remote and I'm running into issues whenever I want to update it. Today I tried changing the action for the play and pause button and then I rebuilt the behavior and installed it, but the action did not appear by default as I have it in the "Default Mapping". I then tried removing the play and pause actions in "Actions in Behavior" and re-adding them. But it got worse, now when I rebuild and install, none of the default actions are mapped to my PS3 remote.

This is the second time that this has happened. The first time that I tried updating the behavior I ended up deleting it entirely and creating a new one. But having so many buttons on the PS3, I can't do this every time I need to make a change.

Please advice, thanks.

These entries from the FAQ may be relevant to this topic:

Configuration

How do I add a new action to a Behaviour - f.ex. an emulated key press or AppleScript? (FAQ015E0153)
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.

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
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.

Hardware - Sony® BD Remote Control

I'm having problems with the Sony® PS3 BD Remote under OS X® 10.8/10.9. (FAQ015E0246)
There's a bug in the Bluetooth®-stack of OS X® 10.8/10.9 in the context of pairing a Sony® PS3 BD Remote. OS X® 10.8/10.9 will ask you to enter a PIN code when you try to connect your remote control. This problem is known by Apple®.

If you pair your Sony® PS3 BD Remote with your Mac® for the first time
1. Use Remote Buddy's Setup Wizard to pair your remote control
2. Restart your Mac® directly after the pairing was successful, while the remote is still connected.
3. The remote should now work without problems.
If you've already paired the Sony® PS3 BD Remote with your Mac®
1. 10.9 only: Try entering 0000 as PIN and reboot. If you're lucky, that was all you needed to do. If this does not solve your issue, please continue with the steps that follow.
2. First, we'll need to remove the Link Key of your Mac® from the memory of your remote control. Since this remote control can only store one Link Key, it's as easy as pairing the remote control with another Mac®. To do so, open System Preferences > Bluetooth on another Mac® and pair your remote with it.
3. All steps that follow should be performed on the Mac® that you want to use your remote control with.
4. Remove - if it exists - the entry of your remote control at Remote Buddy > Preferences > Hardware ® Bluetooth Receiver. The entry usually is titled "BD Remote".
5. If existant, remove the device "BD Remote" from System Preferences > Bluetooth.
6. Delete the Bluetooth preferences files by entering the following in Terminal.app and hitting return (Warning: this deletes all information about all paired Bluetooth® devices):
```
sudo rm /Library/Preferences/com.apple.Bluetooth.plist
sudo rm ~/Library/Preferences/com.apple.Bluetooth.plist
sudo rm ~/Library/Preferences/ByHost/com.apple.Bluetooth.*.plist
```
  Please enter your admin password when requested. Then restart your Mac®.
7. Use Remote Buddy's Setup Wizard to pair your remote control
8. Restart your Mac® directly after the pairing was successful, while the remote is still connected.
9. The remote should now work without problems.

User

29.09.2008 11:41:16

Re: Problems when rebuilding a behavior

View

This posting is older than 6 months and can contain outdated information.

Thanks for asking.

What you specify in the "Default Mapping" tab will be the defaults to
be used in Prefs > Mapping > YourBehaviourName > YourRemote. If you
manually made changes to your settings there, though, these will
override what you previously defined in "Default Mapping" in the BCK.

To return your remote's mapping to what you have listed in "Default
Mapping" in BCK, go to Prefs > Mapping > YourBehaviourName, select
your remote control in the mapping table list, then click on "Reset to
defaults".

Please note that, when you add your own Behaviour for an app that's
already supported by a Behaviour that ships with Remote Buddy itself,
which of the Behaviours will be picked to control the app is undefined.

You'll definately want to make sure that:

- you uncheck the checkbox in front of Remote Buddy's *own* Behaviour
in Remote Buddy > Prefs > Behaviour (so it's no longer used by Remote
Buddy).

- you do have only one copy of your Behaviour lying around in ~/
Library/Application Support/Remote Buddy/Behaviours

- your Behaviours do have different identifiers (=> see the forum
topic "2 behaviour sets" for more info)

- you do select "Compile, testdrive and permanently install" at BCK >
Behaviour Factory for your Behaviour. Just exporting a Behaviour will
really just export it and have no effect at all until Remote Buddy is
restarted - even if you replace an older copy. By using the formerly
mentioned option instead of just exporting, your Behaviour is
compiled, exported and loaded into Remote Buddy in one go.

Best regards,
Felix Schwarz

User

30.09.2008 19:43:39

Re: Problems when rebuilding a behavior

View

This posting is older than 6 months and can contain outdated information.

Alright let me research this a bit and I'll get back to you. Thanks

User

10.10.2008 07:22:26

Re: Problems when rebuilding a behavior

View

This posting is older than 6 months and can contain outdated information.

OK, yes the issue was that I had to "reset to defaults". Thanks again for the help.

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs