I have Remote Buddy configured exactly how I want with the EyeTV software (3.1 release) and Front Row.

I'm using the Apple remote with built in IR receiver. The only problem is that navigation in EyeTV is slow - moving through menus or channel lists in the full screen menu requires multiple key presses, its laggy, etc.

The weird thing is that navigation in Front Row is quick, as usual.

I wonder if there are some delays introduced by Remote Buddy talking to EyeTV in full screen mode.

Thanks for the help! 

For your information, I just have submitted a trouble ticket to the Elgato hotline for investigation ;)

 
Last edited: 21.01.2009 18:49:36 

I already have a working workaround, but it'll still need some further 
testing before it can be released.

Best regards, 
Felix Schwarz 

Thx a lot for your great job, Felix ;)

That's great to hear that you have a workaround. Can't wait to try it. It will render my home setup much more wife friendly :) 

can't await the update. is it possible to say a timeframe?

regards, 
Udo 

Best regards, 
Felix Schwarz 

Not so important, much less than the "come back" of power saving disconnection of my BD Remote ;)

 
Last edited: 23.01.2009 19:19:12

Last edited: 23.01.2009 19:26:58 

Best regards, 
Felix Schwarz 

MacMini C2D 2 GHz / 2 GB memory 
Mac OS X Leopard 10.5.6 
EyeTV 3.1 (latest) driving a Floppy FireDTV-C card 
Remote Buddy 1.11.5 
Sony BD Remote

If I have some time, I'll try EyeTV3.1 with RB 1.11.5 and my Sony BD Remote on my MacPro desktop

Thx for your help.

 
Last edited: 23.01.2009 19:56:32 

Did you rename EyeTV 3.1 by any chance (f.ex. from "EyeTV.app" to 
"EyeTV 3.1.app")?

AppleScript identifies applications by name (under Tiger, at least, to 
which RB 1.11.5 needs to be compatible). If you rename EyeTV, 
AppleScript can't find it and the AppleScript is likely to hang until 
it times out after two seconds.

If you renamed EyeTV.app, please change back the name to EyeTV.app and 
try again.

Best regards, 
Felix Schwarz 

To answer you, I didn't renamed the EyeTV app ;)

So, I really think EyeTV support should find a solution to the bug you pointed out some posts ago ;)

Cédric

 
Last edited: 23.01.2009 20:26:09

Last edited: 23.01.2009 20:27:03 

Since the issue only affects version 3.1, this is handled as a special 
case inside Remote Buddy and the altered handling only is used when 
version 3.1 is detected.

The version is determined at Remote Buddy startup time and by asking 
OS X to provide it with the path of EyeTV's app bundle identified by 
its identifier "com.elgato.eyetv".

If you have multiple versions/copies on your drive, this can generate 
two problems.

1) If you have multiple copies on your harddrive, the behaviour of OS 
X is undefined as to what path is returned. The path of an older 
version could be returned and the special handling might therefore not 
become active.

2) If you have only one version in startable state on your harddrive, 
but didn't restart Remote Buddy after upgrading, the new version will 
not be detected and the special handling will not be active.

If possible, please try again with only one copy of EyeTV.app on your 
harddrive (you could f.ex. zip unused versions, which conserves them 
but can't lead to confusion for OS X Launch Services regarding which 
path to return) and start Remote Buddy only after you have ensured 
only one copy of EyeTV resides on your system (=> f.ex. by using 
Spotlight to find any non-zipped duplicates).

Thanks in advance.

Best regards, 
Felix Schwarz 

I've just silently updated the 1.11.5 release. The only change: Remote 
Buddy now prints the message "EyeTV 3.1 (or later) detected" to the 
console at startup time when the special handling is being used. It's 
probably the simpliest for you to just download the updated copy from

http://www.iospirit.com/remotebuddy/download/

and check the console messages displayed by

/Applications/Utilities/Console.app

for the line

"EyeTV 3.1 (or later) detected"

to see, whether the right copy of EyeTV is used for determining the 
version and the special handling actually gets used on your system.

Thanks in advance for any feedback you can provide.

Best regards, 
Felix Schwarz 

With you patched 1.11.5, I get the right message "Eyetv 3.1 or later detected" in the console, but still the same "shoppy" behavior with my BD Remote : some times, the navigation works well, sometimes not, perhaps it is due to the speed at witch I press the buttons on the remote ? I don't know.

I'm waiting for the answer of the Elgato support, perhaps they will provide me some kind of workaround or a confirmation that this bug will be resolved in a future release ?

Thanks a ton for the RB 1.11.5 update.

The update mostly fixed the slow navigation problem for me, with one exception.

Navigation is quick except for the full screen graphical program guide in EyeTV - the screen with the time/show grid and lots of colored boxes.

Navigation there is still slower than with no RB, but quicker than before the RB 1.11.5 update. For instance, holding down the directional buttons does not seem to move the cursor in the guide predictably. I usually have to hit the directional buttons repeatedly, once per cursor move.

Is it possible that RB's check for whether EyeTV is in full screen menu mode misses the graphical full screen guide - its seems to be a slightly different mode from the other full screen menus.

thanks for the great work, Felix!

The problem is still here with the last release of EyeTV 3.1.1 and the last release of RemoteBuddy. In fullscreen or not, the eyetv general menu is very slow (everytime, now)... the navigation is very annoying with this behavior.

I did not get any help from eyetv support (they answered me to contact the IOSpirit support ... really ??).

I must leave in Eye TV 3.0 to keep the navigation fluent.

Thx for any help :(

The problem has indeed not been fixed in EyeTV 3.1.1. It will be fixed 
in the next update of EyeTV, though.

Best regards, 
Felix Schwarz