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

23.04.2010 08:38:46
Re: Tried RemoteBuddy- now I can't use my remote. help!

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

1) Short answer: 
Your issue is and can't be caused by Remote Buddy. It is caused by another application that you installed.

You can use our free Remote Control Diagnostics tool to find and locate the application that's causing you this issue: 
http://www.iospirit.com/labs/remotecontroldiagnostics/

2) Long answer from the FAQ - including some technical background 
-- FAQ -- 
Q: After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)

A: 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 (http://www.iospirit.com/labs/remotecontroldiagnostics/). 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. 
-- / FAQ --

Don't hesitate to ask if you need further help.

Best regards, 
Felix Schwarz 

Thread-display::