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 

AuthorThread
User

24.11.2014 10:12:37
Remote Buddy Express resets to 'default behavior'
View

This posting is older than 6 months and can contain outdated information.
Hi, im a long time user but first time poster.

I use Remote Buddy express to control eyeTV and switch to Plex/ Xbmc for movies etc, but since a recent update the remote buddy express program seems to resetting back to default behavior. This happens when exiting Plex to restore eyeTV (always running in the background, muted), or when left on eyeTV for prolonged periods and often requires me to activate eyeTV behavior a few times before it properly activates..

Just wondering if anybody else is experiencing the same issues? 

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

Hardware - EyeTV Receiver
User

01.12.2014 22:38:01
Re: Remote Buddy Express resets to 'default behavior'
View

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

Remote Buddy will choose the active Behaviour based on what application OS X reports to be the active application.

That is not always the application whose name you can read in the menu bar. Background/Helper applications running as "UI Element" can become the active application without OS X updating the menu bar or indicating this change visually.

Since the code that selects Behaviours has not been touched for years, chances are you've installed some software in the meantime that runs as "UI Element" and becomes the active application reported by OS X at the time you experience this issue.

If that active "UI element" app is not supported by a Remote Buddy Behaviour, Remote Buddy will pick the "Default Behaviour" since the active app is unknown to it.