| Author | Thread |
User 30.05.2011 02:55:33 | Behaviour not working in fullscreen (Google Chrome) | |
This posting is older than 6 months and can contain outdated information. I set up a behaviour for Google Chrome with several actions: toggle fullscreen, play/pause Netflix, enter fullscreen on Netflix, and exit Netflix fullscreen on my Harmony One remote. These work perfectly when Google Chrome is windowed, but don't work when Chrome is in fullscreen. When I try to play/pause Netflix when it's already in fullscreen, for instance, I get the standard mac error sound as if I'm trying to use an application that isn't active. Under Application specific options under Implementation, I have tried it with all combinations of "activate application and bring it to front" and "send event directly to this application" both checked and unchecked, but it makes no difference. When I test the action to exit fullscreen with the "run actor in 3 seconds option", it does correctly take Netflix out of fullscreen mode, but once I try it with the remote, it doesn't work. Is there anything else I can do? Edit: The same thing happens in Safari. Works in windowed mode, but not fullscreen. Edit 2: Toggle fullscreen (cmd shift F) works perfectly with the remote. It's only once I'm on the Netflix site and play/pause (spacebar) in fullscreen or exit fullscreen (escape) that it doesn't work. Last edited: 30.05.2011 18:30:06
| These entries from the FAQ may be relevant to this topic: 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.
| User 10.06.2011 21:35:01 | Re: Behaviour not working in fullscreen (Google Chrome) | |
This posting is older than 6 months and can contain outdated information. Thanks for asking. I could not reproduce the issue with Chrome 12.0.742.91. If you're using Flash content in fullscreen, chances are this is the root of the problem as it may be executed in a separate process that doesn't identify as Chrome. This in turn would trigger Remote Buddy to switch away from the Google Chrome Behaviour to another Behaviour - which may not have anything mapped for the buttons you press - and you'll get a standard mac error sound. You could possibly get around this by telling Remote Buddy to make the selection of this particular Behaviour sticky - until you explicitly deactivate it. You can do this via AppleScript to make the current Behaviour (yours) "stick": -- cut --
tell application "Remote Buddy"
behaviourcore accessor "setSticky" with stickyValue
end tell
-- cut -- Another possibility would be that when you send the keystroke, the respective window (from Flash and/or Chrome) doesn't have keyboard focus and that the keystroke you send creates the standard mac error sound. For this, I can't offer a solution, sorry. Best regards,
Felix Schwarz
| User 11.06.2011 08:14:15 | Re: Behaviour not working in fullscreen (Google Chrome) | |
This posting is older than 6 months and can contain outdated information. Thanks for your suggestions. I tried making the current behaviour stick, but it didn't change anything. I finally got it working by changing the mapping. Instead of mapping the button presses to the activities I created, I mapped them to the virtual keyboard commands for spacebar (play/pause) and escape (exit fullscreen on netflix.com). I don't know why this way works better in fullscreen on netflix, but it does. Last edited: 11.06.2011 08:15:14
| User 03.05.2012 14:15:28 | Re: Behaviour not working in fullscreen (Google Chrome) | |
This posting is older than 6 months and can contain outdated information. the problem is when you run on fullscreen mode, the application runing is Silverlight plugin, not Safari, then the behaviour reject the key. I tried diferent names without success on the behaviour bundle fields in both application recognition and application specific options. I tried these names: com.microsoft.silverlightplugin and com.microsoft.silverlight, but didnt work. Fixing this, we can use remote buddy to control other apps that runs under safari or firefox or chrome.
| User 05.05.2012 15:58:02 | Re: Behaviour not working in fullscreen (Google Chrome) | |
This posting is older than 6 months and can contain outdated information. Thanks for asking. Google Chrome, like Safari, uses a separate process to sandbox plugins. When plugins implement a full screen mode, it's these separate processes that become the active application. Beginning with version 1.20, Remote Buddy also detects these separate processes and doesn't switch to another Behaviour. I've just (re-)tested this successfully with Remote Buddy 1.21, the respectively latest versions of Chrome and Safari and a YouTube video in full screen mode. If you add custom actions to the Safari or Chrome Behaviours, please be sure not to target specific applications with your action, as both Safari and Chrome aren't the right addressees when a plugin runs in full screen mode. Instead, you'd need to send any key presses to com.apple.WebKit.PluginProcess (Safari) or com.google.Chrome.helper.EH (Chrome) respectively. You increase chances of your action to work in both full screen and non full screen mode when you don't use the option to send key presses directly to an application (so it's posted as regular keypress event that goes to whatever application is currently front most). Best regards,
Felix Schwarz
| User 13.10.2012 20:45:43 | Re: Behaviour not working in fullscreen (Google Chrome) | |
This posting is older than 6 months and can contain outdated information. Hello Felix (and Penney), Just a couple of comments. First off, thanks again Felix for your dedication and support for Remote Buddy. I sometimes have a little trouble figuring it out, but it always seems to work in the end. I use Netflix to stream movies from my Mac to my HDTV. I tried using the instructions from JoseC's April 5 post (forumentry_id=16112) to create my behavior workflow. I created two behaviors, SafariNetflixWindowed & SafariNetflixFullscreen. The com.google.Safari bundle identifier worked fine for windowed actions, but not com.apple.WebKit.PluginProcess. Next, I installed Google Chrome, which worked. Both bundle identifiers (com.google.Chrome & com.google.Chrome.helper.EH) worked fine. I had a little trouble during test compiling. Sometimes when a behavior/activation did not work, I had to rebuild/re-compile it (had to make sure to physically drag the application to the different bundle identifier fields, not just enter the text). After rebuilding correctly, Remote Buddy does a great job of identifying Chrome & its Netflix helper app when Netflix is switched between windowed and fullscreen modes (don't need to manually activate each behavior, Remote Buddy does that automatically). Observation: I often multi-task on a second monitor, while watching streamed Netflix content, which changes the selected application away from Chrome/Netflix a lot. I have found it useful to check the box next to "Send event directly to this application" for actions in the ChromeNetflixWindowed behavior. However, I have noticed that actions in ChromeNetflixFullscreen do not seem to work unless I keep this box unchecked. My advice to anyone reading this post who's trying to get their behaviors to work properly is to be patient. Once you figure out how to use the Behavior Construction Kit, it becomes a lot easier. Don't get frustrated, just try rebuilding your behavior, carefully. Thanks again for the great software! Chapin
chapinbk@hotmail.com
MacBook Pro Retina (mid-2012), OS X 10.8.2, Remote Buddy 1.22
|
|
