MacBook Pro 2018 - Speakers Crackling

[amok-san]

So, the internal speakers are still crackling, right?

Yes, still crackling for me, also still the popping sound when hitting pause/play.

 

[fokmik]

Yes, still crackling for me, also still the popping sound when hitting pause/play.

the hitting pause/play where? itunes radio/youtube ?
For me macOS Mojave last night fixes 2 of my 3 issues , 1) muting issue popping sound, and 2) mail notifications randomly makes a weird sound when i was listening to music

 

[SoyCapitanSoyCapitan]

the hitting pause/play where? itunes radio/youtube ?
For me macOS Mojave last night fixes 2 of my 3 issues , 1) muting issue popping sound, and 2) mail notifications randomly makes a weird sound when i was listening to music

It's exactly the same firmware and problems as last beta they only changed default midi setting to 48 HZ. Change back to 44 HZ and you see nothing fixed.

 

[fokmik]

i wasnt on beta....so, im asking again amok-san, what he means about pause/play ? where that is happening? in itunes /youtube ?

EDIT: i always been at 48 HZ, from the start with High Sierra, and also now with macOS Mojave
But still, even with 48 HZ, i had issues overtime muting music or when receiving mails on HS
Now on Mojave they both are fixed for me...the remaining issue still, is the "time travel " on youtube

 

[tehStickMan]

I still have speaker hiss on Mojave.

 

[peterlee0127]

I still have this issue too.

MBPR 2018 13inch + macOS 10.14 (18A391)

 

[fokmik]

I still have this issue too.

MBPR 2018 13inch + macOS 10.14 (18A391)

when and where does it occur ?

 

[peterlee0127]

when and where does it occur ?

Using iTunes and other apps).
When some system sound/other sound appears, the iTunes music will crack.

 

[fokmik]

Using iTunes and other apps).
When some system sound/other sound appears, the iTunes music will crack.

i had this on High Sierra on my 2018 MBP....when i was receiving mails notification i get this
But for almost 12 hours i am testing and for me, on Mojave this is gone

 

[dven]

Just for kicks I wrote up my issues with external interfaces and filed a bug report..... Still on the fence about return/exchange.

 

[RossoNunzio]

i had this on High Sierra on my 2018 MBP....when i was receiving mails notification i get this
But for almost 12 hours i am testing and for me, on Mojave this is gone

Do you miss the problems present after closing the lid? At the reopening no KP or insipidable reboots?

 

[motomotomoto]

hello everyone... just wanted to share this information i found on the gearslutz board which seems like it could be related to this issue.

https://www.gearspace.com/board/mus...igh-sierra-mojave-coreaudio-overload-bug.html
[doublepost=1537886849][/doublepost]

hello everyone... just wanted to share this information i found on the gearslutz board which seems like it could be related to this issue.

https://www.gearspace.com/board/mus...igh-sierra-mojave-coreaudio-overload-bug.html

This is what someone says in that thread I found specifically interesting...

"I've gotten to the root of the issue and submitted an Apple Dev Bug Report. The AppleSmartBatteryManager driver is part of the IOKit framework, as is CoreAudio. The IOKit has an associated WorkLoop which is basically a que of background tasks it runs. When these are single threaded, like the polling method the Battery Manager uses for its CommandGate checks, or running the active live track in Logic, they exist on the same core, and basically get lined up to run in the WorkLoop. However, the Battery Manager gets priority based on its Command checks. It locks out the core for its cycle. So when a low latency single threaded coreaudio event happens at the same time, you get the skipped cycle error, and then the coreaudio stream can overload producing the audio dropout. You can avoid it by running a higher CoreAudio buffer sample, but if the CPU load is high enough on your audio process, it can still conflict and overload.

Apple did respond for additional diagnostic info, and I also spoke with Logic support and gave them the same details. I even spoke with RME since I initially thought it was exclusive to their driver. Hopefully it gets addressed in some form. To me moving it off the shared WorkLoop, or giving CoreAudio priority should solve it. I verified the bug by disabling the battery manager and the problem went away. Not a fix though, since you cannot get battery health status and have safe guards against overheating or overcharging."

 

[dven]

hello everyone... just wanted to share this information i found on the gearslutz board which seems like it could be related to this issue.

https://www.gearspace.com/board/mus...igh-sierra-mojave-coreaudio-overload-bug.html
SNIP...

It might be a related manifestation where the USB stream is interrupted by the battery polling? It must be really pervasive interrupt since I have dropouts with extremely low CPU - just playing a youtube vid for example. Though my dropouts don't seem to be on any regular schedule, so I'm not sure about the polling being the cause.

 

[sangui2]

Does your issues guys occur only on speakers or on external devices also?
Sometimes I have little crack when using volume up/down (with audio feedback), sometimes on 'youtube time traveling' sometimes all working fine. Eh.. it is horrbile.

One more thing: I experiencing issues only while watching video on youtube - for spotify, itunes everything works fine...

 

[peterlee0127]

Does your issues guys occur only on speakers or on external devices also?
Sometimes I have little crack when using volume up/down (with audio feedback), sometimes on 'youtube time traveling' sometimes all working fine. Eh.. it is horrbile.

One more thing: I experiencing issues only while watching video on youtube - for spotify, itunes everything works fine...

I only have this issue with the internal speaker and earphone (build in 3.5mm).
When I use the chord mojo(the external DAC) every thing is ok.
10.14 didn't fix it.... I decided to exchange to the new one (within 14 day).

 

[fokmik]

Do you miss the problems present after closing the lid? At the reopening no KP or insipidable reboots?

No, no KP or reboots
[doublepost=1537891197][/doublepost]

Does your issues guys occur only on speakers or on external devices also?
Sometimes I have little crack when using volume up/down (with audio feedback), sometimes on 'youtube time traveling' sometimes all working fine. Eh.. it is horrbile.

One more thing: I experiencing issues only while watching video on youtube - for spotify, itunes everything works fine...

yes, the watching youtube, from time to time when skip ahead etc, still does makes that sound

 

[soiramk]

I only have this issue with the internal speaker and earphone (build in 3.5mm).
When I use the chord mojo(the external DAC) every thing is ok.
10.14 didn't fix it.... I decided to exchange to the new one (within 14 day).

I'm messed up... Does your newly (exchanged) MacBook have those issues as your previous one?

 

[crazyjuice]

I wonder if apple is sending new macs with preinstalled mojave?!?!

I had already 2 macbook pros from 2018 and send ‘em back due to poppin’ n cracklin’ speakers, after yesterday release maybe things has changed so i can order once again

 

[dven]

Ok guys, interfaces: mine - focusrite 2i2 2nd gen, also tested with komplete audio - same issue, though, I've written to Jon Sine (noted producer vlogger on youtube) and he has no issues with arturia interface (which is also usb)
About the adapters, apple's original adapter is the best so far, I do notice some problems with hub/adapter from aukey so i just use it for controllers and dedicated usb port/adapter on the other side from hub with all controllers connected.

P.S. Did you notice that with this T2 latency went down significantly? yes, it does this stutter sometimes, but actually it's faster then before, you can measure that with just placing cable from output to input and measuring offset (latency numbers in DAW were never realistic until now with usb devices) offset will be 0!!! (or 1) instead of 20-30 or smth. Tested with 13" 2016 non touchbar laptop. couldn't do the same with 2016 which i had before but I'd dare it would have offset as well.
So there are some benefits but seems like this T2 just isn't performing as it was supposed to.

Out of curiosity, when you tried the Komplete, had you updated the firmware? NI lists a firmware update from 7/23/2018. I'm about to test one today, as well as swapping out for a genuine apple c<->a adapter.

 

[8SlaiN8]

Out of curiosity, when you tried the Komplete, had you updated the firmware? NI lists a firmware update from 7/23/2018. I'm about to test one today, as well as swapping out for a genuine apple c<->a adapter.

thanks for mentioning, no, i've just plugged it in, as if I'd use my focusrite, lemme

hello everyone... just wanted to share this information i found on the gearslutz board which seems like it could be related to this issue.

https://www.gearspace.com/board/mus...igh-sierra-mojave-coreaudio-overload-bug.html
[doublepost=1537886849][/doublepost]

This is what someone says in that thread I found specifically interesting...

"I've gotten to the root of the issue and submitted an Apple Dev Bug Report. The AppleSmartBatteryManager driver is part of the IOKit framework, as is CoreAudio. The IOKit has an associated WorkLoop which is basically a que of background tasks it runs. When these are single threaded, like the polling method the Battery Manager uses for its CommandGate checks, or running the active live track in Logic, they exist on the same core, and basically get lined up to run in the WorkLoop. However, the Battery Manager gets priority based on its Command checks. It locks out the core for its cycle. So when a low latency single threaded coreaudio event happens at the same time, you get the skipped cycle error, and then the coreaudio stream can overload producing the audio dropout. You can avoid it by running a higher CoreAudio buffer sample, but if the CPU load is high enough on your audio process, it can still conflict and overload.

Apple did respond for additional diagnostic info, and I also spoke with Logic support and gave them the same details. I even spoke with RME since I initially thought it was exclusive to their driver. Hopefully it gets addressed in some form. To me moving it off the shared WorkLoop, or giving CoreAudio priority should solve it. I verified the bug by disabling the battery manager and the problem went away. Not a fix though, since you cannot get battery health status and have safe guards against overheating or overcharging."

THANK YOU! Honestly, I was of the same idea but unfortunately my knowledge wasn't enough to proof it in such a clear way. I've got to that conclusion after trying out thunderbolt audio interface today and it also had these issues occurring sometimes.

 

[dven]

thanks for mentioning, no, i've just plugged it in, as if I'd use my focusrite, lemme


THANK YOU! Honestly, I was of the same idea but unfortunately my knowledge wasn't enough to proof it in such a clear way. I've got to that conclusion after trying out thunderbolt audio interface today and it also had these issues occurring sometimes.

So your dropouts are regular - every minute? Mine are completely random and don't tie to the battery polling. And that's unfortunate that the TB interface also had the issue. That's the first non-USB interface report I've seen, so I was hoping TB was the ultimate solution if need be.

Edit - What TB interface did you try?

 

[8SlaiN8]

So your dropouts are regular - every minute? Mine are completely random and don't tie to the battery polling. And that's unfortunate that the TB interface also had the issue. That's the first non-USB interface report I've seen, so I was hoping TB was the ultimate solution if need be.

Yes, they also have completely random nature, though, that tread on gearslutz was made 4 weeks ago and the issue was much more sever before for me, so, probably they addressed this one. Though, I have to admire it's very rare, but it happened during normal iTunes playback. I'll try now to jump between these two and see.

Edit
Zoom tac 2r

 

[dven]

So. I did some more digging and here are some error logs (attached) which point to Apples audio handler.

I don't see anything before this that points to a different culprit that might be a different root cause for the issue, though there are a ton of log entries related to launchservicesd right before the audio glitch error log. For example.

info 08:15:46.157063 -0400 launchservicesd CLIENT: 0x7fb041f04760/29001 Received message on connection from our client: <private>
info 08:15:46.157087 -0400 launchservicesd CLIENT: 0x7fb041f04760/29001 Mapped requested session to session id 100008

I'm not sure what those are about at this point.

 

[peterlee0127]

I am curious about does anyone get the new replacement without this issue ?

I do the test with three MBPR 2018 13 inch.
Doing the same test, listen to the Apple Music and use same apps (with system sound or effects)

Mine: a 3-5 second sound crack. (send from factory in 9/12)
Friend 1: 1 second sound crack. (send from factory in 9/2)
Friend 2: No any issue. (send from factory in 9/10)

So, I already send my MBPR to Apple for replacement for the new one.

I am afraid this issue is hardware design.

 

[fokmik]

I am curious about does anyone get the new replacement without this issue ?

I do the test with three MBPR 2018 13 inch.
Doing the same test, listen to the Apple Music and use same apps (with system sound or effects)

Mine: a 3-5 second sound crack. (send from factory in 9/12)
Friend 1: 1 second sound crack. (send from factory in 9/2)
Friend 2: No any issue. (send from factory in 9/10)

So, I already send my MBPR to Apple for replacement for the new one.

I am afraid this issue is hardware design.

so while you are listening to itunes radio you go in system preferences and use system sound effects and you get sound cracks?
Are you on Mojave or High Sierra? are you on 44hz or 48?