Some content won't produce it, some will. There are sometimes mitigations that reduce the issue, but then it comes back in the next update. Create a series of standard tests that always reproduces popping. If people post anecdotes without evidence then it's a waste of time for everyone.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Any one notices the cracking/popping sound of new 16 inch MBP?
- Thread starter MengkeMary
- Start date
- Sort by reaction score
Some content won't produce it, some will. There are sometimes mitigations that reduce the issue, but then it comes back in the next update. Create a series of standard tests that always reproduces popping. If people post anecdotes without evidence then it's a waste of time for everyone.
I've tried the command q test on quite a few demo units with pretty mixed results, but it exist on all T2 models I tried. I guess my biggest contention is that given the quicktime fix workaround, I find it hard to believe that it couldn't be fixed by firmware updates.
Last edited:
We had around 20 firmware updates since T2 based MacBook Pro came out. Each OS update since High Sierra has had a firmware update and each interim beta also had firmware updates.
If its in principle impossible then why does the quicktime fix work? It's possible Apple is just not very good at making software and didnt feel this had enough attention to warrent fixing.
That's not really a fix and doesn't work for every example where the audio is corrupted. This 'fix' shouldn't be used during professional audio workflows.
Sure I just meant that the software can at least mitigate it so we don't have enough info to say for sure whether a firmware update could fix it.
Last edited:
you can have 1000 firmware updates for something else...but if none is for this particulary issue, is irrelevant...Apple is aware of this now, after more than 1 year...so lets see from now on
18 months of Apple being aware. 18 months of Mac faithful praying to the Apple Gods to deliver them to the promised land. Then the T3 MacBooks will come out and the same Mac faithful will just buy the new machine without fixing the previous model. Great business model for Apple. Not so good for your long term life savings.
I think the T3 will probably just introduce new headaches and am okay with this potentially not getting fixed provided the demo units are a good gauge of the problem.
18 months?? Get real.. apple didnt know until now..or didn’t care because the reports were slim with the 2018 models
Dont trust those who told you 18 months ago that apple is aware..probably those are the ones who want not to return or not to buy the mac because of this issue
[automerge]1576745136[/automerge]
T3 if it will come..is far away..since even the mac pro has the t2 now and i wonder if the MP has this with the built in speaker
The error: Every-time I need water or not and use the valve to control it, it makes a horrible sound.
The quick time fix: "Start Quicktime so you always need water", qucktime fixes the issue because the valve is never touched and always on and you're using a lot of water.
When ever I use the quicktime fix non stop for a day or two, the audio starts to **** up in other ways, like out of sync. It properly cycles it when no audio is needed, to reset the audio controller.
Funny.
I've just tried "command q" on my old solid MBP 15" from 2013. There is a POP! Exactly the same as on my 16" (I have it only with cmd Q - no problems with YouTube or FPX after 10.15.2 update on my 16 MBP)
The command + q method is a killer 
it works nearly on every mac laptop. Dont forget the hissing sound when you start playing audio. Press pause and listen careful for 10 to 15 seconds. I had this problem since 2016 but nobody was interested. Nobody of the apple staff in Germany was "aware" of this problem.
it works nearly on every mac laptop. Dont forget the hissing sound when you start playing audio. Press pause and listen careful for 10 to 15 seconds. I had this problem since 2016 but nobody was interested. Nobody of the apple staff in Germany was "aware" of this problem.I've just made a topic about that... is there a fix?The command + q method is a killer
Strange that you said that because I have just read a very very very long discussion topic about the popping and crackling sounds and you were in that thread for 18 months. Throughout the whole thread, lasting 18 months, many people said they were sending feedback and bug reports to Apple and were receiving replies from Apple Support. You were in that thread posting many times, and now today after 18 months you're saying Apple didn't know.
A reminder in case you forgot the last 18 months...
MacBook Pro 2018 - Speakers Crackling
Anyone else noticed their speakers randomly crackling on the new MacBook Pro 2018? It happens every so often for me. Only saw one other report so far here: https://discussions.apple.com/thread/8466796 =============== Edit by Weaselboy Moderator Note: Also see the discussion in the news...
forums.macrumors.com
Please note, if this is how you are going to behave as a user, consumer and customer, you will get what you deserve from the company you religiously trust too much. If you want make excuses for broken hardware that forces you to buy new hardware then that's exactly what will happen to you....again....and again...and again.
Until you have no money left when you retire and the wealthiest Apple shareholders will be laughing.
That is a thread,forum ....that doesnt mean APPLE knew about it...
At least now, they publicaly said they heard about the issue and Apple is investigating...even to the resellers sent a letter regarding the audio popping sound
Apple support.......that doesnt mean apples engineers or something OFFICIALLY...again that sending back report is just for you to keep the mac and not return it. Even I, tested for the so called apple support all night...and still nothing. So dont trust what apple support is telling you..
At least now, they publicaly said they heard about the issue and Apple is investigating...even to the resellers sent a letter regarding the audio popping sound
Apple support.......that doesnt mean apples engineers or something OFFICIALLY...again that sending back report is just for you to keep the mac and not return it. Even I, tested for the so called apple support all night...and still nothing. So dont trust what apple support is telling you..
Last edited:
Actually Apple didn’t make any “official” statement about this. That was just an internal memo to resellers so that they stop replacing these machines.
Again, my senior advisor knew about this almost 6 months ago. The only reason that this issue is more popular now is that the popping is significantly louder on the 16 inch model due to speaker redesign.
No clue so far can exclude or either point to the T2 chip as the main cause. With more information coming into light every day i can say that T2 is the main suspect here.
And last but not least. We don’t even know if Apple is actually trying to fix this. Maybe that 10.15.2 update is considered as a “fix” by Apple. Let’s not forget that it’s the same company that marked those machines as “ready to ship” without even testing them so i wouldn’t be surprised if the story ends here with that semi-fix.
Again, my senior advisor knew about this almost 6 months ago. The only reason that this issue is more popular now is that the popping is significantly louder on the 16 inch model due to speaker redesign.
No clue so far can exclude or either point to the T2 chip as the main cause. With more information coming into light every day i can say that T2 is the main suspect here.
And last but not least. We don’t even know if Apple is actually trying to fix this. Maybe that 10.15.2 update is considered as a “fix” by Apple. Let’s not forget that it’s the same company that marked those machines as “ready to ship” without even testing them so i wouldn’t be surprised if the story ends here with that semi-fix.
I'm not sure what you're getting at. I'm not saying the quicktime fix is optimal just that it indicates this very well could be a software issue and not an unfixable hardware issue like the butterfly keyboard.
Interesting. What info is coming to light to make it look like the T2 chip?
There's no reason to think this issue has been a priority for Apple until now.
As for the association with the T2 chip, there's conflicting information about that, but even if it's true, it doesn't imply it's a hardware issue, as there is plenty of software connected with the T2.
Haven't seen complaints about Bridge OS crashes lately, so that rather works against your point.
Given that it took 4 years for apple to release a laptop with a non broken keyboard design, I think this is probably a software issue they've been incompetent to fix.
Quicktime doesn't fix anything, it avoids the issue by forcing the audio system to be continuously on.
18 months, about 20 firmware updates and three operating systems later.
Article from summer 2018
'Apple did not respond to a request for comment.'
Some 2018 MacBook Pro Owners Experiencing Crackling Speakers
Following the release of 2018 MacBook Pro models last month, some customers have turned to the MacRumors Forums, Apple Support Communities, Reddit,...
www.macrumors.com
61 page thread prior to this thread we are in...
MacBook Pro 2018 - Speakers Crackling
macOS is now reinstalled and there was also a supplementary update available for me (assume this was the throttling update). I'm pleased to say that under conditions where the crackling would occur, they've not since I've done this. Stress testing for the last hour and so far so good.
forums.macrumors.com
But keep putting on the blinders, make excuses, shuffle words around, make distracting replies, and pray to the Apple gods.
Actually when someone suggests that T2 may cause these audio issues this doesn’t necessarily mean that it’s a hardware problem.
Since T2 takes care of multiple tasks it could be related to both Bridge OS and the design of T2. It’s a new element (and a very complicated one) that has been recently introduced and almost every piece of data passes though it, including audio.
I still believe that this has to do with the original speculation that we all had in the beginning: the audio interface is being switched on and off to to save power.
But in the same time i believe that a simple issue like this, that 3 years ago could be resolved with a few lines of code (again, this happened with a script called AntiPop), is now harder to address since there is a new stage added to the audio path.
I guess we will never know what’s happening inside T2 since it’s a security chip and Apple is planning to use this in many different ways. Louis Rossmann has some valid points regarding T2 (i trust him more than Apple technicians by the way).
One way or another if this gains even more attention and stays unresolved i can see an official statement like "we did this to protect your privacy" coming. Nah i still regret my purchase.
Last edited: