![]() ![]() Each Device needs to be running at iOS 5.0 or higher.Here is what you’ll need for it all to work. To enable it, double press the Home button twice to bring up the list of recently used apps. Swipe that menu from the left to the right. On the iPhone you might need to swipe a couple of times to see the following AirPlay icon. Tap on the icon and then Apple TV and toggle Mirroring On. With Apple TV Version 3 and a post 2011 MacBook Pro with Mountain Lion OS, you can stream your desktop to the TV via Apple TV dekka1948 said: ok I think they have sorted this problem And if you are an Android device user, you can follow the same process again by downloading Kodi from the app store followed by the Mirroring360 App, which will serve the same. You’ll also need to make sure that AirPlay is enabled on your Apple TV. There you go! Now you can watch video from the YouTube app on your HDTV and whatever else you want to display from your device.ĪirPlay Mirroring is a feature built into OS X Mountain Lion - provided you have a 2011 Mac or higher. If you want to add the feature to an older Mac or a Windows machine, check out AirParrot. Case closed.Here’s a short video I captured showing AirPlay in action on my Apple TV. In the meantime, at least I have my camera back. To see if anything happens here, we’ll likely have to wait for OS X 10.9.3. Apple would not comment regarding a possible future fix in OS X. However, Squirrels promised to investigate further to see if they might somehow resolve the AirParrot problem on their end. There’s not much we can do about that-the fix has to come from Apple.” As such, similar software from other vendors (such asĪir Display) may also exhibit the conflict. Squirrels further claimed that the problem “is likely caused by an instability in Apple’s own drivers. I confirmed that reinstalling AirParrot without the drivers allows the software’s mirroring to work without blocking the camera. They acknowledged the issue, noting that it appears limited to AirParrot’s “Extend Desktop” feature, which is the only aspect that requires kext files. I contacted Squirrels, the developers of AirParrot, for comment. After a restart, my camera returned to life. Success! I’m not sure what key file the utility removed, but it worked. For this reason, I had AirParrot installed on my Mac Pro but not my other Macs. Older Macs that are not compatible with AirPlay mirroring. The cause turned out to beĪirParrot-a program that mirrors a Mac’s display to Apple TV via AirPlay. It reported that AirPlay mirroring no longer worked for some users after updating to OS X 10.9.2. OneĪpple Support Communities thread especially grabbed my attention. While waiting for Apple’s return call, I did some further digging into problems with OS X 10.9.2. ![]() ![]() He promised Apple would get back to me in a few days, after analyzing the results. The support person next had me download an app called Capture Data which collects and sends data from your computer to Apple. They had me perform one additional diagnostic test: remove third-party kext files from the /System/Library/Extensions folder. AirParrot, AirPlay mirroring, and the missing camera solutionĪdmitting defeat, I called Apple Technical Support. At this point, I searched the web andįound a report that claimed deleting .plist from /System/Library/LaunchDaemons would stop the crashing but (as I expected) not restore the camera. Surprisingly, neither the killall command in Terminal nor a Force Quit from Activity Monitor could terminate the process. This meant that killing the process might stop the crashes but would not bring back the camera. I figured that, while this VDCAssistant file was likely involved in the missing camera mystery, it was not the root cause. It revealed that a process called VDCAssistant was crashing at a rate of about ten times a second! I located this OS X file buried in /System/Library/Frameworks/amework/Versions/A/Resources/VDC.plugin/Contents/Resources.Ĭonsole’s system.log shows a steady stream of VDCAssistant crashes. If anything, checking the logs only succeeded in raising my anxiety. Perhaps OS X’s Console logs could identify the culprit file? Nope.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |