Support > Remote Buddy Forum > Problems with EyeTV Software // 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

05.01.2009 18:41:15

Problems with EyeTV Software

View

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

I'm trying to set up Remote Buddy to work with EyeTV and my Apple Remote. I'm running the latest EyeTV beta 3.05b53.

I've set up short presses of the left and right keys to skip forward and back in the EyeTV behavior, and long press of the menu button to exit EyeTV and enter FrontRow. Short press of menu brings up the full screen menu in EyeTV.

Up key is mapped to channel up and down key is mapped to channel down (default EyeTV behavior is for these buttons to be mapped to volume up and volume down).

So far, two big problems:

1. when I do the long press of the menu button, the machine does exit EyeTV and start frontrow. However, the recording that was playing in EyeTV keeps on playing and I can hear the sound after frontrow launches.

The option to pause players on exit in the EyeTV behavior is checked.

2. In EyeTV, when I bring up the fullscreen menu with a short press of the menu button, the full screen menu is VERY slow to respond to the navigation commands. I think that both EyeTV and RB are responding to each key press on the remote. So, when I press the up key when full screen menu is displayed, RB seems to be sending a channel up and then FR responds to the request to move up one menu item from the remote.

Any way to map the up and down keys to channel up and channel down without interfering with EyeTV's menu navigation functionality?

I definitely have the RB kernel extension installed, and I'm running OS X 10.5.6 on a mac mini core duo 1.6GHZ.

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

Driver

What is the task of the driver and what do I need it for? (FAQ015E0177)
The Setup Wizard already contains a summary on how the driver does help Remote Buddy to provide additional features and hardware support. If that summary was too short, here's some more info on each of the points:
- fix for Apple® Remote driver problems in OS X
  Since OS X 10.4.9 (that includes 10.4.10/10.4.11/10.5.x/..) many users have been experiencing that one button press on their remote does now trigger two reactions - once from any currently running application that supports the Apple® Remote, once the default system action. So, this problem is not specific to Remote Buddy. The driver provides a clean, system conform fix to this problem using only documented APIs.
- enabling of all features of built-in IR receivers
  Only with the Remote Buddy driver do you gain support for arbitrary length button presses for the Play and Menu buttons as well as minimized reaction times for all buttons. While this may sound like unimportant technical details, they actually do have a strong practical impact. If, for example, you want to map a function to the Play or Menu button, that you want to see executed for as long as you press that button, this was previously simply impossible to achieve. This limitation still applies to all other applications. It does not for Remote Buddy with the driver loaded.
- the emulation of a virtual Apple® Remote
  Control applications that have support for and listen to an Apple® Remote - with any remote control of your choice supported by Remote Buddy. And on any Mac®. This allows you to f.ex. use iAlertU side by side with Remote Buddy or accessing special functions and modes inside applications that would otherwise require these apps to have full control over the built-in IR receiver of your Mac® - and that your Mac® actually came with one.
- support for Bluetooth® remotes and external receivers
  It's not possible to reliably operate many Bluetooth® based remotes, like for example the Wii® Remote with a Mac® purely from userspace due to limitations in the operating system. The situation for many external receivers is similiar: some of their features - or the entire device - can only be supported with the help of a driver.

General

How do I navigate the Remote Buddy menu? (FAQ015E0170)
To navigate the menu, you can use the following button presses:
"Left" - up by one level in the menu
"Right" and "Play" - choose the current entry
"Left hold" - go to the main menu
"Plus" and "Minus" - scroll through the entries
"Menu hold" - jump to the first entry of the current menu
"Menu" - fade in/out the onscreen menu

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.
After updating to OS X 10.6.2, my Apple® Remote is no longer available for selection in Remote Buddy. (FAQ015E0236)
Please update your copy of Remote Buddy to version 1.15 or later.

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

07.01.2009 20:35:06

Re: Problems with EyeTV Software

View

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

Thanks for asking.

I'm running the latest EyeTV beta 3.05b53.

I can only provide you with support for official EyeTV releases, not
betas.

Please keep in mind that beta releases are beta releases because they
usually don't represent a finished state and may still have known
problems and bugs. Beta releases therefore should not be discussed
here and are generally unsupported.

1. when I do the long press of the menu button, the machine does
exit EyeTV and start frontrow.

So far, this is what you configured ..

However, the recording that was playing in EyeTV keeps on playing
and I can hear the sound after frontrow launches.
The option to pause players on exit in the EyeTV behavior is checked.

... but this obviously is a bug. I've looked into it and fixed it. The
fix will be part of the next scheduled release.

2. In EyeTV, when I bring up the fullscreen menu with a short press
of the menu button, the full screen menu is VERY slow to respond to
the navigation commands.

Are you using the Apple Remote with an Apple built-in IR receiver or
via an EyeTV hardware IR receiver (and if you do, which model)?

Due to the way that EyeTV handles EyeTV IR receiver hardware,
reactions to these will always be a bit laggier than those of the
Apple built-in IR receiver.

I think that both EyeTV and RB are responding to each key press on
the remote. So, when I press the up key when full screen menu is
displayed, RB seems to be sending a channel up and then FR responds
to the request to move up one menu item from the remote.

Remote Buddy takes care of all of this not happening and events taking
the fastest route available:

1) It automatically detects, when Front Row is active and routes
button presses directly to it.

2) When EyeTV is the active application, it'll route events to the
EyeTV Behaviour and execute the mapped actions except ..

3) .. when EyeTV's onscreen / fullscreen menu is active (Remote Buddy
will detect this automatically), in which case it will simply ignore
whatever mapping you have set for EyeTV and provide a smooth and
intuitive navigation experience.

Best regards,
Felix Schwarz

User

08.01.2009 01:57:09

Re: Problems with EyeTV Software

View

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

Thanks for the quick reply on this. I'll await the next version of RB.

Also, perhaps RB doesn't work well with full screen menus in the beta version (3.05b53) of EyeMenu. EyeTV definitely does not seem to be capturing the remote's commands properly in fullscreen mode. When I quit RB, EyeTV's fullscreen menu navigation is completely different (much more responsive).

I'll try again with the release version and report back.

BTW, I'm using an apple remote, not EyeTV remote.

Last edited: 08.01.2009 01:57:31

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