Author | Thread |
User 24.04.2007 06:15:28 | A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hi Felix! RB is getting cooler and cooler! Thanks for all the great development. I just had a couple of issues: 1. For some reason the app insists on showing up in both the menubar and the dock, regardless of the fact I have selected for it to be in the menubar only. This was a bug you had squashed in a previous version, coming back to haunt us again I suppose... :D 2. My Front Row, which was installed using Andrew Escobar's enabler will not work with RB anymore. It use to just perfectly and if I quit RB and use the standard key command launch for Front Row it works just fine. RC1 never had an issue with this either, just the new version. 3. Lastly, this is not an issue, a question actually. I noticed in the notes for the update it said one could pair the Apple Remote. I may have misunderstood, does this mean those of us using a KeySpan IR and an Apple Remote can now pair it??? I have long for this to be a feature, since I have to keep RB inactive most of the time, due to have other Apple Remote devices in the room that kicked on the RC1 all the time. So is pairing now possible?? If so, where or how does one do it? If not...keep that one on the list...I have faith you will find a way on a future release! :D Thanks again Felix, you have done such a great job on this app, it has been so cool to watch your wonderful work develop.
| These entries from the FAQ may be relevant to this topic: General If you switched from Tiger (OS 10.4) to Leopard (OS 10.5) and you have not updated your copy via the Online Updater since, it is possible that you are still running a copy of Remote Buddy with modified Info.plist file, which can lead to the described problem.
Solution:
- Quit Remote Buddy.
- Download a fresh copy of Remote Buddy ( http://www.iospirit.com/remotebuddy/download/ )
- Replace your existing copy of Remote Buddy with the fresh copy of Remote Buddy.
- Start the new copy of Remote Buddy.
Hardware
- Please make sure you have the latest version of Remote Buddy installed. If in doubt, download the latest version, quit Remote Buddy, delete it, empty your trash, then copy the downloaded version of Remote Buddy to your harddrive and start it from there.
- Please make sure, that you have installed the latest version of the Remote Buddy drivers. You can install the drivers using the Setup Wizard (=> access it via the Remote Buddy pulldown menu).
- Check your Remote Buddy settings in the Hardware category. Your remote control should be listed there and the lamp next to it should be green. If you don't find your remote control there, either the Remote Buddy drivers were not installed or installed in an outdated version - or - there is a general problem with the device. For USB devices, plugging the device to another port or resetting the PMU and/or SMC-unit of your Mac® (=> find guides on how to do this for your Mac® in the support area of apple.com) may help. If you can't find it under "USB" in the System Profiler (=> /Applications/Utilities) either, a hardware defect is as well possible.
- Check the batteries of your remote control.
- If your remote control has an on/off switch: make sure that your remote control is switched on.
- If your remote control requires additional receiver hardware: make sure that it is correctly attached to your computer and that it turns up in System Profiler.
- If you use an Apple® Remote, you should also check your system settings. Quit Remote Buddy, then open System Preferences.app > Security. Please make sure that the option to disable the infrared receiver is NOT active and click on "Unpair" should you have paired your Apple® Remote with your Mac®. After that, start Remote Buddy. If your Apple® Remote still doesn't work with Remote Buddy, please also check its preferences for the Apple® Remote. They can be found at Preferences > Hardware > Built-in IR receiver. If support for multiple remote controls is enabled there, ensure that your remote control is checked in the right table (=> you can find the correct entry for your remote control by pressing a button on it).
- If you are using a Keyspan™ RF Remote for Front Row, re-pair its remote control and receiver by simultaneously pressing the small knob on the back of the remote control and the knob on the receiver stick (the knob looks like the blinking LED, except it does not blink).
Hardware - Apple® Remote
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.
Please update your copy of Remote Buddy to version 1.15 or later.
| User 24.04.2007 06:45:32 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. I am also having the dock + menubar issue. This is since the RC2 update. Another bug I have noticed is on my startup. I have the iTunes® behavior as my default but I uncheck the option to have iTunes start as well. Since the update iTunes always starts on login. 3. I check the pref to keep a behavior active unless manually changed but this is not working in RC2. When I switch apps, the behavior also changes. Before and after the update I was having the 10.4.9 issue of FrontRow starting with the remote but your mentioned deactivate/activate fix worked. Thanks for the great app! PS: I also have a feature request. My F1 &F2 keys will dim my display. Is it possible to make this a behavior in RB? Last edited: 24.04.2007 07:35:17
| User 24.04.2007 10:17:42 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hi Felix! Me too for the dock + menubar issue. I would test the new functions later.
| User 24.04.2007 11:47:02 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hello Erick, thanks for the feedback. 1. Fixed. I actually had forgotten to update the Cocoa bindings for this element to the changed settings name. The version distributed last night does bind to the old name, which does nothing in this release. I take all the blame ;-) Please redownload Remote Buddy from http://www.iospirit.com/remotebuddy/download/ for an updated archive. 2. Did you install the kernel extension in the new release? I ask because it adds the ability to emulate ab Apple® Remote and as far as I know, Front Row is looking for this. I don't know what Andrew Escobar's patches change, but if then requires Front Row to not find an Apple® Remote, this might be the problem. A clean install via Pacifist or a reinstall with the latest patch from Mr. Escobar might help. 3. Actually I wanted to do this for RC2 as well. However, the Apple Design Awards submission deadline was the limiting factor. Right now, the most extensive support for the Apple® Remote in the world is only available for machines with a built-in IR receiver. Sorry. Best regards, Felix
| User 24.04.2007 11:47:02 | Re: Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hello Matthew, thanks for the feedback. The dock & menu bar issue can be easily solved by redownloading the update. Selecting the iTunes® Behaviour as default in the Preferences should also always start up iTunes. To fix the problem, click on "Advanced.." in the Preferences and select "None (recommended)". iTunes should no longer start on Remote Buddy startup then. Regarding your feature request: this functionality is already around for a few releases as part of the menu. I plan to make it accessible as mappable actions in a future release as well. Best regards, Felix
| User 24.04.2007 17:12:30 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hey Felix, Yup, the first issue is all fixed with the new version I downloaded....THANKS! Concerning the second issue, that one does not seem to fix. (scratches head) I went ahead and downloaded the 10.4.9 combo update, which replaces Andrew Escobar's 2 patched files that make Front Row work. Here is what he lists on his site: "What Mac OS X system files are being patched by Enabler? To unlock Mac OS X’s built-in support for Front Row, Enabler patches the following two system files: /System/Library/LoginPlugins/BezelServices.loginPlugin/Contents/MacOS/BezelServices /System/Library/PrivateFrameworks/BezelServices.framework/Versions/A/BezelServices" Those 2 files are replaced in the 10.4.9 Combo Update, so I reinstalled it and then tried installing the new FR Enabler. No luck, same as before. If I quit RB, Front Row is fine, if I open RB and try to activate it through that or the keyboard command, no dice. I can actually say, this is the first time I have ever had this issue with any version of RB you have done. Any additional thoughts?? Concern the feature request....I assumed you had it on the list and I understand having to put it off for the design awards (good luck BTW) just wanted to make sure it was still on the list/possible, etc. Thanks again Felix!
| User 24.04.2007 17:37:02 | Re: Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hello Erick, hmm, do you have the Remote Buddy kernel extension installed? If so, please try without the Remote Buddy kernel extension installed. Remote Buddy installs the Apple® Remote Emulation through the kernel extension on start, and removes it on exit. It's not active all of the time. You can easily remove, load or just testdrive the kernel extension through the Setup Wizard, which you can also reach via the menu item on top of the screen. If removal fails, it's usually just unloading that fails because some app on the system still holds a reference to it. A reboot does then fix the problem. Thanks for wishing me luck :-) Best regards, Felix
| User 24.04.2007 18:12:27 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Thanks for the quick reply Felix! The menu/dock issue is resolved. As to the other problem, I have had iTunes as the default behavior for months now and I assure you that it did not start up with remote buddy. I'm not sure what changed but that is what is happening now and it is a loss of functionality for me. I primarily use the controller for iTunes and having to manually activate the behavior is annoying. I guess adding that option would be a feature request. Thanks. Hello Matthew, thanks for the feedback. The dock & menu bar issue can be easily solved by redownloading the update. Selecting the iTunes® Behaviour as default in the Preferences should also always start up iTunes. To fix the problem, click on "Advanced.." in the Preferences and select "None (recommended)". iTunes should no longer start on Remote Buddy startup then. Regarding your feature request: this functionality is already around for a few releases as part of the menu. I plan to make it accessible as mappable actions in a future release as well. Best regards, Felix Last edited: 24.04.2007 18:16:55 | User 24.04.2007 22:21:37 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Another issue I've observed with RC2 is that changes made to the default application behaviors don't "stick" after updating. For instance, I changed the QuickTime right and left buttons. The default is frame advancing, which is terribly slow. Instead, I'm using a few Applescripts I found on MacOSXHints to jump ahead/back x seconds. After updating, these were all reset to their defaults.
| User 26.04.2007 01:38:03 | Re: Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hello Matthew, my apologies .. you're absolutely right, I just forgot about that detail. You can go back to what you are used to by deactivating the checkbox to bring iTunes® to front in the Preferences > Behaviours > iTunes. Best regards, Felix
| User 26.04.2007 01:49:02 | Re: Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hello Rob, thanks for letting me know. Which remote control are you using? If it's the Wiimote or you're using an eHome receiver, you can bring back your old options by renaming the respective com.iospirit.remotebuddy.....plist file to the respectively new identifier. You can easily retrieve the correct name by having a look at the date of the files. The change of identifiers was necessary to bring everything down to a common namespace. Best regards, Felix
| User 26.04.2007 19:48:57 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hi Felix, The iTunes problem seems to have fixed itself with the reinstall that also fixed dock/menu bar issue. This is a great app and I appreciate your attentiveness to resolving these issue. Cheers, Matt
| User 27.04.2007 20:17:02 | Re: Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hello Matthew, thanks for letting me know! Best regards, Felix
| User 27.04.2007 20:51:38 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Which remote control are you using? If it's the Wiimote or you're using an eHome receiver, you can bring back your old options by renaming the respective com.iospirit.remotebuddy.....plist file to the respectively new identifier. You can easily retrieve the correct name by having a look at the date of the files. The change of identifiers was necessary to bring everything down to a common namespace. Felix, I'm not really sure what you're explaining. I use the Apple Remote on an Intel Mini Core Duo with built-in IR receiver. But no matter, the bug I described only occurred when I upgraded from RC1 to RC2. When you updated RC2 from Preview 13 (I think?) to the latest P15, I did not see my settings reset anymore. A-OK!
| User 28.04.2007 14:44:01 | Re: Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Oh, it shouldn't happen for the Apple Remote with a built-in receiver at all. The internal identifier (also used to name the prefs file your mapping for that remote are stored in) didn't ever change. Best regards, Felix
| User 30.04.2007 17:09:50 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. I just downloaded the 15b version and the double dock/menu bar issue has returned.
| User 02.05.2007 12:44:02 | Re: Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Hello James, thanks for the feedback. The relauncher / installer after the Remote Buddy update should actually preserve the NSUIElement setting in the Info.plist. If this failed - or Launch Services refused to update despite the relauncher / installer explicitly telling it to do so, setting the option to something different and then back to the desired setting should solve the problem for good. Best regards, Felix
| User 02.05.2007 14:01:53 | Re: A couple of issues with RC2 | |
This posting is older than 6 months and can contain outdated information. Yup, that fixed it. Thanks. Interesting that just restarting didn't do it (which I'd tried), you have to change the setting.
|
|