Skip to main content

Fixing Bluetooth headset audio quality issues on Mac.

The issue is that, although a headset might have implemented the AptX codec with great quality sound otherwise, because it is a headset, and it needs to be able to work with A2DP for the Microphone to work with all phones etc. The moment it does this, the sound output quality drops as well.

The easy way to fix this is to switch your Input from Bluetooth to Internal Microphone. To do this, Hold in Option, and click on the Sound icon in the menu bar (or go to the Sound Preferences).



But it is annoying to do this every time...

To fix this some people have devised scripts to detect this, and switch it back, but this would require automation software and some fiddling. Which you either may not want to do, or are unable to do.

I may have found another way to fix this without using scripts or apps.

Open the standard "Audio MIDI Setup.app" utility, and click the + at the bottom to create an "Aggregate Device". Then select the Internal Microphone as the only component in this aggregate device and select that as the default input.



For some reason this prevents Mac OS X from selecting the Bluetooth Microphone from now on and it will stay on the internal (via the aggregate) one when you reconnect.

Let me know if this works consistently for you... so far it's been working fine for me. You can also rename your "Aggregate Device" to "Microphone" for extra points.

Comments

Post a Comment

Popular posts from this blog

Firefox: Open diverted links in new background tab instead of new window

This has frustrated me for a long time... something I really liked about Opera. Go to 'about:config' url and set: browser.tabs.loadInBackground to true (should be already) browser.tabs.showSingleWindowModePrefs to true browser.tabs.loadDivertedInBac kground to true Then in advanced preferences is a new option: 'Force links that open a new window to:' can be used for immesdiate effect.
2 comments
Read more

Why torrent low-ratio banning is killing the network and is generally a bad idea.

It seems a growing trend for people to get banned for low share ratios. Now I can understand how this would appeal to some people`s sense of (in)justice as there are people out there who do not understand that not sharing while you download will ultimately make you download yours slower as you supply bits to other people who would otherwise been supplied by the seeder, making it possible for you to download from open slots at the seeder. These are typlically low-intellect `kiddies` who don`t do math and then download hacked clients because they are just stupid. I agree that these people are evil. But putting a share-ratio of 0.9 and higher as mandatory is just insane. (IMHO 0.1 is the absolute maximum) Take the following example (using mathematical induction and taking values to extremes) if I limited my download to 1k/s and my upload to 25k/s (I have a 256/256 connection) my share ratio inexorably tends to go to sub-1.0. In fact, I find that only the T1 people seems to...
3 comments
Read more

Creating a SSH tunnel to the internet.

Ever been at a client with Orwellian access restrictions on the internet? Why not use what they provide you to the max without cracking their security. What you will need: 1. Access/login to a linux machine with ssh running on port 80 (or 443) (See UnixShell - They're grrreat!) 2. The proxytunnel client program . Creating the tunnel: Firstly you will need to create a TCPIP tunnel through your proxy server. For my example I'm running OS X (on my shiny MacBook Pro). To do this, add the following (2 lines) to your ~/.ssh/config file: Host shell.my-host.com ProxyCommand /Users/teuton/bin/proxytunnel -N -p "local-proxy:8080" -u "proxy-user" -s "proxy-pass" -d "shell.my-host.com:443" Great! We are all set! You may need to tweak these settings depending on your local proxy server type and configuration (NTML auth etc) Now the easy part. Creating the proxy: To ssh into your machine simply type: > ssh teuton@shell.my-host.com To make...
2 comments
Read more