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

15.05.2007 14:47:32
MediaCentral 2 and screensaver problem
View

This posting is older than 6 months and can contain outdated information.
I 've experienced the following minor Problem using RB and the Keyspan RF remote to control MediaCentral 2:

Whenever I press a Button on the remote in order to deactivate the screensaver during the use of MediaCentral, the triggered action does not belong to the "MediaCentral" behaviour but to the "Audio & CD / DVD" behaviour. (i.e. the "left" button triggers the eject action") 
By the time the screensaver is deactivated the MediaCentral behaviour is active again.

This problem does not occur for example during the use of the "virtual mouse" behaviour. Is there something I can do about this?

 

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

Hardware - Apple® Remote
User

17.05.2007 18:43:01
Re: MediaCentral 2 and screensaver problem
View

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

What is happening here is that the Default Behaviour (which is pre- 
mapped to actions from the Audio & CD / DVD Behaviour) is 
automatically chosen because MC2 is no longer the front most 
application (the screen saver is now).

If you want your selected Behaviour to stick until you explicitely 
deactivate it - and no matter which application is active / front 
most - you have to turn on

"Manually activated Behaviours stay active until they are 
explicitely deactivated"

in

Preferences > General > Advanced…

It was the default once, but the concept of auto-switching and manual 
switching turned out to be confusing for too many.

Virtual Mouse & Co. make Remote Buddy API calls to ensure the 
"stickyness" of this selection. You can also achieve this through 
AppleScript for any other Behaviour.

Best regards, 
Felix 

User

17.05.2007 19:54:34
Re: MediaCentral 2 and screensaver problem
View

This posting is older than 6 months and can contain outdated information.
Thank you for your quick reply, Felix. 
As You suggested I switched on the "Manually activated Behaviours stay active until they are explicitely deactivated" option. 
The result is, that all triggered actions during screensaver activity belong to the "MediaCentral" behaviour but will no longer terminate the screensaver, even though the option "Button presses create activity" is switched on. A restart of RB did not change this. Any suggestions? 
User

17.05.2007 20:43:02
Re: Re: MediaCentral 2 and screensaver problem
View

This posting is older than 6 months and can contain outdated information.
Are you using the latest version of Remote Buddy?

There was an issue in RC1 that could sometimes render the option to 
create inactivity ineffective (mainly, if you activated the screen 
saver by placing the mouse on any of the left hand corners of the 
screen).

As this was fixed with RC2, this option should work just fine.

Best regards, 
Felix 

User

18.05.2007 01:16:14
Re: MediaCentral 2 and screensaver problem
View

This posting is older than 6 months and can contain outdated information.
I'm using Version 1.0 Preview 15b (RC2) - the current version. The screensaver is set to start after a few minutes of inactivity (no active corners).

Just in case it helps you to find the problem:

- I'm using Mac OS X 10.4.9 on a Mac Mini G4 1,25 GHz 
- attached only to a TV (as media center) 
- neither mouse nor keyboard is connected

Best regards,

Michael 

User

21.05.2007 16:51:01
Re: Re: MediaCentral 2 and screensaver problem
View

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

thanks for the info.

I found the bug - it's actually very subtle ;-)

Will be fixed with the next release.

Best regards, 
Felix