A couple of months ago I had the idea to see if there was a simple way to play iTunes music from the built-in iMac speakers while also playing it through a Bluetooth speaker (in this case a JBL speaker). My goal was to have the music playing from the computer in one room and also playing from a Bluetooth speaker in the dining room. Sure enough, OS X has a way to do this (I’m running 10.9 so I don’t know how widely this feature is supported across older versions of OS X).
Thanks to user Eric Ross in the Apple Support Communities I didn’t have to do much searching to find the answer. As detailed in his response, the solution is to open the Audio Midi Setup application located in the Utilities folder and then simply create a Multi-Output Device that has both speaker types selected. Note that in order for this to work the Bluetooth speaker needs to already be connected to the Mac.
At this point we’ve only created the multi-output device. One additional step is required – setting it as the current output device (System Preferences -> Sound -> Output) :
I originally did this with my iMac but the screenshots in this post were created using my MacBook Air.
And that should work. The Bluetooth audio (at least with the settings I used) will have a slight delay in comparison to the system speakers. Bluetooth has a relatively short range so the practical applications of this method may be limited by obstructions within one’s home and the receiving capability of the Bluetooth device that is used.
SSD Hard Drive
MacBook Pro (Late 2013, 13.3″ with Retina Display)
SSD Hard Drive
For the more literal folks, I apologize. I realize that a Mac is actually a PC but for the sake of simplicity I added it to the title so everyone would understand what I was trying to do.
I recently needed to transfer a Windows 7 install from a Lenovo notebook over to a MacBook Pro Bootcamp partition. I need to make it clear that this project was not a success. However, I have learned a few things that others will find useful. In addition, had I followed some advice available in a blog post it’s possible that it would have worked. After all, I did succeed in migrating the partition over and it did attempt to boot…
This particular transfer was a bit more challenging due to the fact that both systems use SSD drives. As a result, I couldn’t simply pull a drive and execute more direct partition clones.
Should you be considering such a move then a good place to begin is a blog post by twocanoes titled Migrating a Real PC to Boot Camp with Winclone 4. Basically, this is the advice I did not follow. Now, my reason for not following it wasn’t irrational. I was very concerned that I’d run Sysprep before cloning, only to then discover that it simply wouldn’t work. Perhaps if I hadn’t been trying to do this quickly I could have attempted this while also having a good fallback clone of the partition made BEFORE running Sysprep or any other changes (and it did not turn out quickly – I spent more time trying to make this work than I did simply starting with a fresh Windows 7 Bootcamp install).
So, once again, I’m confident that I could have succeeded in this endeavor had I followed the advice from twocanoes. However, even though I wasted a lot of time I did learn a few valuable things along the way.
I don’t think this issue is limited only to newer MacBook Pro Retina systems. A day after upgrading my wife’s 13″ MacBook Pro, which is a 2010 or 2011 model (and doesn’t have a Retina Display), we experienced a similar problem. She was trying to use her laptop but the mouse cursor did not follow the movements on the trackpad. It seemed to stop responding for brief moments and then move off in a slightly different direction when it did work. I witnessed this problem myself and even checked to see if something had gotten on the trackpad that was throwing it off. Nothing had.
Because I had yet to learn of this problem I happened on the solution by accident. My wife had become frustrated so she closed her laptop and let it sleep. I grabbed it, opened the display, but it wouldn’t fully wake up (an issue that itself isn’t exactly rare). Rather than power the laptop off, not knowing what she may have left open and unsaved, I simply closed the lid and waited until the LED pulsed to indicate that the system was sleeping. Then I opened it back up. This time the system woke up properly and, once again, the trackpad behaved normally.
It’s certainly possible that something else was the cause but the problem hasn’t recurred so I doubt it’s a hardware issue. This has never happened before. In addition, a friend of mine mentioned that he also had a similar problem with an older MacBook Pro. So, if you have an older MacBook Pro that behaves this way try the solution for new MacBook Pro systems.
Updated 12/10/2013: Jon Stacey has identified a fix, which involves restoring a copy of racoon from Mountain Lion. I followed his advice and was able to successfully establish an L2TP VPN connection again. Please visit the ‘OS X 10.9 Mavericks fix’ section of his page for more information.
Updated 07/06/2014: The VPN continues to function just fine. I’ve installed several server updates since my previous updates so at this point I’m no longer certain if the previous fix is still in place or if Apple provided a proper fix via update. Regardless, I haven’t had any new problems.
Despite having updated various software packages to avoid software problems with compatibility under Mavericks I hit a wall that I simply haven’t been able to get past. The built-in VPN server in Mavericks (with and without OS X Server) is broken.
I had it working just fine under Mountain Lion, which I managed using iVPN. After upgrading it stopped working. Not long after I added OS X Server and it still wouldn’t work (I purchased OS X Server for its Time Machine capabilities, not for VPN support so I didn’t purchase it expecting it to fix this problem).
Prior to upgrading I had an L2TP VPN server working. Since upgrading I’ve been unable to get L2TP or PPTP working, though I’ve seen more activity with PPTP during connection attempts than with L2TP.
I have hunted across many forum threads and I have been unable to find a solution that works. Some users have reported success though the apparent causes and solutions are extremely varied. The majority of posts are from users that cannot find a solution. This weekend I spent several hours trying to find a solution without success.
At this point there appears to be nothing more that I can do. I’ll simply have to wait until Apple issues an update that fixes the problem. Until then I’ll have to use a service such as LogMeIn to access my desktop, though it’s only a partial solution and doesn’t provide the full access to my network that I need from a VPN server.