macOS uses SBC over AAC on AAC enabled speaker?

Question

macOS uses SBC over AAC on AAC enabled speaker?

Hi there,

I was looking around the internet for this but just simply can't figure it out. I use a Marshall ACTON speaker which supports AAC as codec, AAC is enable on macOS settings and yet, the Marshall keeps getting SBC only.

I enabled AAC and aptX with the bluetooth explorer, the bluetooth guideline verification shows that the acton "Supports AAC with variable bit rate".

I reset the bluetooth module multiple times, reset SMC and NVRAM multiple times and re-paired the speaker multiple times as well...

Any input will be greatly appreciated! Thanks community :)

sudo defaults read bluetoothaudiod                                        ~
{
    "AAC Bitrate" = 320;
    "AAC max packet size" = 644;
    "Apple Bitpool Max (editable)" = 80;
    "Apple Initial Bitpool (editable)" = 80;
    "Apple Initial Bitpool Max (editable)" = 80;
    "Apple Initial Bitpool Min (editable)" = 64;
    "Disable AAC codec" = 0;
    "Disable HFP" = 1;
    "Enable AAC codec" = 1;
    "Enable AptX codec" = 1;
    "Negotiated Bitpool" = 80;
    "Negotiated Bitpool Max" = 80;
    "Negotiated Bitpool Min" = 80;
    "Negotiated Bitpool Min (editable)" = 80;
}

MacBook Pro 13", 10.14

Posted on Feb 3, 2019 10:23 AM

Reply

Answer 1

Feb 4, 2019 10:04 AM in response to John Lockwood

The problem isn't so much enabling AAC (see above, bluetoothaudiod clearly shows it is enabled) but macOS refusing to use it. However - I jus connected a different loudspeaker (Teufel Bamster) and I instantly get a AAC connection, so despite Marshall telling me that "(t)he audio source device, in this case your Mac device, chooses the Codec. Please follow up with Apple Support to see if they can help." it seems to be some sort of issue on Marshall's side. Or on both sides, I don't know really, but it is annoying. One of those "once you've seen it..."

Reply

Answer 2

Feb 4, 2019 12:53 PM in response to xDemianSmithx

Okay, so, as it turns out, despite initially being advised differently, the Acton just simply doesn't support either aptX or ACC but only "The Acton Bluetooth offers Standard Bluetooth V4.0 + EDR". Which is kind of good because at least nothing is broken.

Reply

Answer 3

dialabrain

Level 10

136,385 points

Feb 3, 2019 10:37 AM in response to xDemianSmithx

https://support.marshallheadphones.com/hc/en-us/categories/115000810729-Contact-Customer-Support

Reply

Answer 4

Feb 3, 2019 11:01 AM in response to dialabrain

Sorry, that’s true - I thought contacting them would naturally be the first step so failed to mention it... I have no idea what is going on there, I might just contact them again, just in case...

Reply

Answer 5

dialabrain

Level 10

136,385 points

Feb 4, 2019 7:37 AM in response to John Lockwood

You can let Apple know they are doing it wrong. Feedback - macOS - Apple

Reply

Answer 6

Feb 3, 2019 10:45 AM in response to dialabrain

Thanks for the input, I was in contact with them, obviously, but all they can tell you is "we don't support aptX but do support AAC", the way macOS connects und which codec is activated would be n the macOS side, not on the speaker's side...

Reply

Answer 7

dialabrain

Level 10

136,385 points

Feb 3, 2019 11:59 AM in response to xDemianSmithx

I see. Do you happen to have access to any Windows or Linux computers you can use to compare the sound?

Personally I've only tried Bluetooth audio once to connect Spotify to my AV receiver and it was ok, not great. Certainly not as good as running through a DAC. If Marshall can't help, maybe someone else will reply here.

Reply

Answer 8

dialabrain

Level 10

136,385 points

Feb 4, 2019 6:24 AM in response to John Lockwood

I really don't understand Apple in this area, it certainly does not qualify as the famous 'It Just Works'.

FWIW, perhaps it's because the catch phrase wasn't "'It Just Works' with every device currently made or will be made".

Reply

Answer 9

Feb 4, 2019 7:35 AM in response to dialabrain

I really don't understand Apple in this area, it certainly does not qualify as the famous 'It Just Works'.

FWIW, perhaps it's because the catch phrase wasn't "'It Just Works' with every device currently made or will be made".

Of course not. However clearly in this case the Mac supports all the most common Bluetooth codecs but Apple have made using some of them unnecessarily hard. I have no issue with for example the fact that AptX HD is not built-in and hence obviously a device only using that would not work, but failing to enable AAC which is supported on iOS in the 'It Just Works' manner and is possible on Mac but via an unnecessarily complex process is simply wrong.

Reply

Answer 10

dialabrain

Level 10

136,385 points

Feb 3, 2019 10:49 AM in response to xDemianSmithx

Well, it wasn't obvious to me what you have already done. But I don't understand their response. They are basically saying, we don't know how our speaker connects to Macs.

Reply

Answer 11

Feb 3, 2019 11:51 AM in response to dialabrain

It does play fine, just with lower quality than expected ¯\_(ツ)_/¯

Reply

Answer 12

dialabrain

Level 10

136,385 points

Feb 4, 2019 1:34 PM in response to xDemianSmithx

Glad it's sorted.

Reply

Answer 13

Feb 4, 2019 6:19 AM in response to xDemianSmithx

I really don't understand Apple in this area, it certainly does not qualify as the famous 'It Just Works'.

Apparently iPhones and iPads default to AAC over Bluetooth whereas Macs as standard only support AptX even though apparently they can also do AAC. There seems no logical reason why AAC is not also enabled as standard even if it is not the default choice. :(

Anyway see this article - https://9to5mac.com/2018/08/31/mac-how-to-force-aptx-aac-on-your-supported-bluetooth-headphones/

If needed you can register for a free Apple Developer account.

Reply