Support > Remote Buddy Forum > Button Pushed/Key Test Function // 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

30.05.2012 23:13:43

Button Pushed/Key Test Function

View

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

While the pictures in the mapping screen are useful for users with the exact remote that RemoteBuddy assumes you're using, it's pretty useless for anyone that has any other remote, and unless the button positioning matches 100% it can be all but impossible to determine what name RemoteBuddy calls a particular button on your remote.

To work around such issues it would be useful if RemoteBuddy included a screen where users could press a button and RB would highlight the key it detected (by name, with a picture -- I'm not picky about the interface). That would both allow users with non-standard remotes to figure out what key mapping they need, and it would provide a key function test, so users can detect stuck/busted keys, or even just determine the RemoteBuddy is receiving keystrokes at all (for example, to test the range for BT remotes, to test line-of-sight for IR remotes, to determine if a remote is just dead, etc.)

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.

User

06.06.2012 21:53:33

Re: Button Pushed/Key Test Function

View

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

I agree, this would be fantastic. Actually, I'd be happy if I had a log file that tells which button was pressed on one of the configured remotes.

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