This posting is older than 6 months and can contain outdated information.
I do not argue with that as I dont have the needed low-level knowledge.
I don't want to argue, either.
This is the part i don't understand. Remote buddy is supposed "not to change anything in system". How is possible to uninstall driver only? I found only FAQ how to uninstall Remote buddy itself. Or you mean Candelair ? If so, I was experimenting with and without it and of course with restarts.
One needs to distinguish between two separate things:
- the stock Apple OS X driver for the Apple IR Receiver
- the Remote Buddy driver (also available seperately as the core part of the Candelair package) for the Apple IR Receiver
Remote Buddy doesn't need to change/remove/patch/.. any system files in order to use its own driver. And it doesn't need to hack/patch/modify/.. any part of the system at runtime to do this either. Apple provides clean, publicly documented OS X APIs for this.
As I said before: this is not a software problem. I already listed two common physical problems. You'll find more possibilities in the FAQ.
I really do not want to start arguing, but simply - I dont agree. I made A LOT of tests lately and I have conclusion, it is somehow software related. Frontrow works flawlessly for an hour of desperate clicking and waiting for any loss. Everything is rock solid. If I run remote buddy and/or Plex, I'm experiencing losses. Obviously, this can not be physical issue in any way.
It can. Please see my - really detailed, really lengthy - reply that I wrote prior to replying to your post for details.
Interesting finding is, that frontrow works flawlessly even when remote buddy is running.
That actually contributes to the conclusion that this is a physical issue. Front Row in most places doesn't distinguish between long and short presses and you're much less likely to notice any effects of a physical issue than if you're using an application that does react differently to long and short button presses. An application that doesn't distinguish won't show any different effect between two short button presses - and - one longer button press. Compared to that, the difference in an application that does will immediately be apparent because the reaction is different than you'd expect and as you *could* expect if the IR signal was received correctly in its entirety.
Maybe some problem passing the decoded IR codes to the target 3rd party applications?
All events are handled identically inside Remote Buddy and its driver. No difference is being made between EyeTV, Plex .. or Front Row. It's always the same code at work.
Or latest FrontRow uses its own driver no matter what?
No. When Remote Buddy is installed, Front Row is using Remote Buddy's driver as well. And when Remote Buddy is running, Remote Buddy actually translates the button presses it receives into cursor key strokes and sends these to Front Row.
I've the greatest interest in Remote Buddy working as perfect as possible everywhere and for everyone. So, rest assured that if anything suggested this was a software issue, I wouldn't hesitate to send you debug tools and ask for the output. I've done it in the past and I'm not going to change this.
But if, like in this case, all indicators for a physical problem are so crystal clear (to me at least, but I've also spent most days of almost the last 4 years with remote control and IR topics and the Apple Remote in particular - on a low level - if that counts) and any additional information I get actually supports that it's a physical problem following pure logic, I'm afraid I can't do more for you than to repeat myself, which doesn't really help anybody.
I've now spent several hours on this thread basically explaining the same over and over again with growing level of detail. I'm afraid I can't do more for you than that.
Best regards,
Felix Schwarz
P.S.: I recall a past thread with comparable intensive and detailed debate. It was about Bluetooth/WiFi interferences. This, too, was a physical problem and correctly identified by me as such (BT/WiFi sending over the same 2.4 GHz band). It, too, was attributed to Remote Buddy by participants of the discussion and if I recall correctly, their tendency was to not believe my argumentation that it's a physical problem. What happened since then? Months after the discussion, Apple put up a knowledge base article saying exactly the same as me and suggested the same workaround (using a 802.11n network, which operates on a 5 GHz band and doesn't conflict with 2.4 GHz Bluetooth) ..
