Support > Remote Buddy Forum > Wiimote & Behaviour questions/problems // 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

08.11.2007 16:02:52

Wiimote & Behaviour questions/problems

View

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

Hi,
im using RB quite some time now and i really love most of it.
but there are questions& some things i just cant get to work.

1) Wiimote/ implementation keypress
On press button (e.g.) 1 (and hold down) another keypress triggers a release for button 1.
i would really love to see this changed if possible.
that makes some use of the wiimote impossible for me.

2) Wiimote/ global configuration
on default button B is for showing/hiding the RB menu.
if i remove this in the global menu and want to make it the home button to show/hide the RB menu it comes up, but to hide the menu only button B works... even if B has no global action.

3) some things are not available as behaviour action,
for example the airtunes choice. it would be nice to switch to another expressstation from the mainmenu without going to & activating iTunes behaviour.
same thing with the eyetv fullscreenmenu. it would be nice to enter it straight from the mainmenu / not from the eyetvbehaviour.

4) predefined behaviours
is it possible to add an action on "deactivation" of an existing behaviour? / like it is possible in options of the Behaviour factory
most apps i dont need running all the time so an option on automatically quit on activation of an other behaviour would be nice.

ok so thats it. with these things (mostly no1+4) RB would be perfect for me, but of course i see there are a lot of other things going on here and must be done.

thanks in advance for any help
Heiko

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

Behaviours

The installed application XY, for which a behaviour exists, does not turn up in Remote Buddy's menu. What should I do? (FAQ015E0160)
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.

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 - EyeTV Receiver

Which receivers are supported? (FAQ015E0211)
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.

User

10.11.2007 02:02:10

Re: Wiimote & Behaviour questions/problems

View

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

Hi,

1) This limitation is owed to the way remote controls work outside of
a gaming context. I.e. imagine pressing "right+up". While it makes
sense in games, it might result in combinations of "first page" and
"next page" actions as well as the mix-up of emulated keystrokes
leading to combinations that could lead to undesirable effects in a
boatload of applications. That's why currently, only one button can be
pressed at a time. I continue to think of and refine a solution to
this general problem, though.

2) The home button tells Remote Buddy to enter a special menu
navigation mode. In that mode, the menu button (== B on the Wiimote)
is always assigned to closing the menu. This way, you can map Remote
Buddy's menu to any buttons - even those critical to navigation - and
still leave the menu at any time.

3) There, too, is a reason why things are the way they are: many
actions require the application they are targeting to be active and
frontmost to operate properly due to the way they work.

4) Good point. I've thought of this some time ago, already, but have
not come around to implement it, yet.

Best regards,
Felix

User

13.11.2007 17:40:22

Re: Wiimote & Behaviour questions/problems

View

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

Don't know if this will help, but on #4 I had similar thoughts until I changed how I view RB and behaviors. At first I thought starting an app meant I HAD to start a behavior. Instead I switched to having custom actions start/stop everything and let the behaviors auto-enable to follow. So now in the Main Menu I have "Watch TV", "Listen to Music", "Watch DVD", etc. These are Applescripts that launch/setup the proper apps and shutdown others that would get in the way. For some of the simpler launching situations I think you can skip AS and just use the custom action commands. I do a lot of tweaking of the apps so I find AS works better for me.
That solved #4 for me, and it turned out better than if I had behaviors stop other behaviors.

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