Path to return) and start Remote Buddy only after you have ensured zip unused versions, which conserves themīut can't lead to confusion for OS X Launch Services regarding which If possible, please try again with only one copy of EyeTV.app on your Not be detected and the special handling will not be active. Version could be returned and the special handling might therefore notĢ) If you have only one version in startable state on your harddrive,īut didn't restart Remote Buddy after upgrading, the new version will
X is undefined as to what path is returned. If you have multiple versions/copies on your drive, this can generateġ) If you have multiple copies on your harddrive, the behaviour of OS OS X to provide it with the path of EyeTV's app bundle identified by The version is determined at Remote Buddy startup time and by asking Since the issue only affects version 3.1, this is handled as a specialĬase inside Remote Buddy and the altered handling only is used when 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. 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's located elsewhere and can also only be solved there.Īlthough our products can't cause any such issues, we're regularly contacted about such issues and asked for help. Instead, the cause of the issue exists independently of Remote Buddy. Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. 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. 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. 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. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.Īs long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions.
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver.
0 kommentar(er)
