Support > Remote Buddy Forum > Help: Auto activate behaviour // 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

21.05.2009 18:17:24

Help: Auto activate behaviour

View

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

I updated RB and reconfigured.

Since then something does not work the way it was working before:

When I switch to another app I was used to the corresponding behaviour automatically be activated.

Now, it seems that I switch to another application and the bevaviour does not switch, I have to do it manually.

What is wrong here?!

(I do the app switching between EyeTV + Plex via some Applescript that pauses Eyetv etc.. It really worked well before)

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

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

25.05.2009 11:15:17

Re: Help: Auto activate behaviour

View

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

Thanks for your email.

No changes have been made to these routines in what must be well over
a year now.

But since you mention Plex:

I recall some old version of Plex did only close its window, but did
not quit and did not return focus, so it was still the front-most
application. This bug was eventually fixed by the Plex team.

This bug then resurfaced in Plex with IIRC Plex 0.7.14 (you'll find
quite a lot of discussion of this bug in the Plex forums). It was
supposed to be fixed by the Plex team in 0.7.15 and in fact I can't
reproduce it with that release.

While I'm not familiar with the code of Plex and what caused this Plex
bug in the first place and how it was eventually addressed, chances
are this bug was not fixed for everyone, since I by now have 3 reports
that since Plex version 0.7.14+, there's a problem with Plex quitting.

Since the problem wasn't there with previous releases of Plex, Remote
Buddy did not change (so that the only change between working state
and non-working state is the Plex version), the problem was already
acknowledged to have reappeared with Plex 0.7.14 and the history of
Plex/Remote Buddy issues (in which all issues have always been caused
by bugs in Plex, but never in Remote Buddy and that again, this
problem seems to be limited purely to Plex with not a single other
applications affected by what would have to be a general problem if
its cause was within Remote Buddy), my conclusion can only be that
this is purely a problem in Plex and not Remote Buddy and consequently
also needs to and can only be fixed in Plex.

I'll send Elan an email and am sure he'll take a look.

In the meantime, collecting some more info on the problem may be of
help:

What is your system configuration?

Does Plex actually quit on your system? (please check in Activity
Monitor.app)

If it does actually quit: how long does it take to quit? (again,
please use Activity Monitor.app to monitor when it actually quits)

Thanks in advance.

Best regards,
Felix Schwarz

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