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.
I recently ran into an odd little problem while working with a copy of Adobe Acrobat Pro (installed as part of a CS6 suite) in Windows. In this case both the problem and the solution were specific to when I had installed Acrobat and the platform that I was using at the time. This particular instance of Windows 8.1 wasn’t very old – all of the data had recently been transferred from a Windows 7 system.
Sometime last week, while attempting to view a PDF file from within Outlook, the installed copy of Acrobat X simply quit working. It didn’t fail with an error. It simply didn’t launch. My other Adobe CS6 applications continued to work just fine. This sudden change in behavior was a bit alarming at first but it didn’t take me very long to identify the problem.
It seems that, for whatever reason, Acrobat encountered a problem when it had passed the initial 30-day trial period. This is even more of an oddity considering that I had never set it up to act as a trial – the product key was correctly entered when I originally installed the software.
While searching for a solution I stumbled upon an Adobe support document (possibly linked from a forum post somewhere) that describes the problem I was having and it also offers a file to fix the problem. In my case Solution 1 worked perfectly. Acrobat Pro now opens once again. The link to the support document is included below: