MacBook Pro 2018 - Speakers Crackling

[AdamA9]

I’ve got the issue with crackling as well. I also experienced a glitch with a YouTube video the other day. I was watching it (sound was normal etc), and then went to the previous page in Safari (the YouTube home page). The sound from the video I had left continued playing but it was skipping like a broken record. Only stopped when I watched a new video.

A prior phone call to Apple resulted in a PRAM reset which seemed to help at the time. At the moment the whole thing isn’t too severe though, and everything else has been ok.

Any initial call to Apple will result in the usual PRAM, VRAM, SMC reset along with macOS reinstall and then a clean wipe and start again.

A few of us have humoured Apple and gone through this process to prove none of this will fix the issue. My new machine has been delivered. I didn't even want it, I was happy to wait for a replacement, but Apple insisted it doesn't affect all machines and that the fix was a long way off so I should take it.

 

[mdnz]

This issue blatantly affects >50% of machines, easily. And/or people just don’t know what to listen for.
--- Post Merged, 23 minutes ago ---

I wouldn't be surprised at all if that was the case. But I understand Apple in this also. If people don't notice, just keep selling them. After all it's a company, money is king.

 

[AdamA9]

I wouldn't be surprised at all if that was the case. But I understand Apple in this also. If people don't notice, just keep selling them. After all it's a company, money is king.

\But some of these issues like the video skipping like a broken record is pretty hard to miss. So I don't know how they wouldn't notice them.

I wonder what will happen to mine that is going back. Presumably they'll restock it and someone else will have my issues.

 

[mdnz]

\But some of these issues like the video skipping like a broken record is pretty hard to miss. So I don't know how they wouldn't notice them.

I wonder what will happen to mine that is going back. Presumably they'll restock it and someone else will have my issues.

I'm talking about the hissing mainly. All 3 of mine had it. I guess if you're not in silent rooms it's pretty hard to spot.

 

[trickness]

I really love my machine except for this problem - got about 5 more days to decide if I am going to return it. Really wish Apple would release a patch or at least some info about the problem and when it will be fixed. Its not like they aren't aware it is an issue.

 

[AdamA9]

I'm talking about the hissing mainly. All 3 of mine had it. I guess if you're not in silent rooms it's pretty hard to spot.

Ah I get you. I can't hear that over the fan noise tbh.

 

[Wags]

Any initial call to Apple will result in the usual PRAM, VRAM, SMC reset along with macOS reinstall and then a clean wipe and start again.

A few of us have humoured Apple and gone through this process to prove none of this will fix the issue. My new machine has been delivered. I didn't even want it, I was happy to wait for a replacement, but Apple insisted it doesn't affect all machines and that the fix was a long way off so I should take it.

I always just start my call Apple that I have already done those but half the time they start asking because not listening or following prompts
[doublepost=1534948003][/doublepost]

I really love my machine except for this problem - got about 5 more days to decide if I am going to return it. Really wish Apple would release a patch or at least some info about the problem and when it will be fixed. Its not like they aren't aware it is an issue.

It will take a lot of returned machines or bad press before really acknowledge. Just like the MBP keyboard.
[doublepost=1534948665][/doublepost]What’s going on. If Apple had no problems during testing and now having problems because of manufacturing or consistent quality on parts?
[doublepost=1534949574][/doublepost]

AppleCare does transfer over to the replacement system.

I'm also thinking wholly software issue, buoyed by the following:
- USB DAC has same problem
- Audio stream popping issue identified in 2011 MBA

But I'm also not hopeful for a timely fix, considering 2011 model exhibits similar issues, and these exact issues have appeared since 2016 touchbars.

As for the speaker hiss, my 2017 had it.

Overall, my hopes are slim for ANY fixes.
[doublepost=1534376387][/doublepost]Update from Apple:

Engineers report back, they acknowledge my evidence of hissing/crackling/popping. Issued stop to any replacements for this issue on 2018 line, as they say it's software problem.

Support dude (probably my best experience with Apple support so far tbh) didn't get provided with an ETA for software fix, mentioning that Mojave is coming out.

So, let us keep trying the betas and hoping that final release of Mojave addresses these problems.

If it is a hardware issue they would want to stop replacements too. Why keep giving out machines that would be the same or only 1/10 okay.

 

[DanielEAndersson]

MacBook Pro 2018 feels pretty much dead on arrival at this point, fix a long way off and no one wants to own a laptop with these kind of issues. Hope Apple learn from this, these sort of issues could happen to a new laptop maker, but should not happen to a large established maker. It’s so sloppy.

 

[CreeptoLoser]

MacBook Pro 2018 feels pretty much dead on arrival at this point, fix a long way off and no one wants to own a laptop with these kind of issues. Hope Apple learn from this, these sort of issues could happen to a new laptop maker, but should not happen to a large established maker. It’s so sloppy.

Speak for yourself. I don’t work in Logic and don’t give a crap about Boot Camp. I’ve already earned back the cost of the machine by using it. When the patch comes out these negative comments are going to look as ridiculous as the comments in 2016 when there were 1st generation graphics driver glitches.

It just makes humans look stupid that we have such privelaged and spoilt lives that we waste hours on forums moaning about a driver. File a feedback report for each bug instead and go do something constructive. This discussion only needed 3 pages.

 

[mdnz]

It just makes humans look stupid that we have such privelaged and spoilt lives that we waste hours on forums moaning about a driver. File a feedback report for each bug instead and go do something constructive. This discussion only needed 3 pages.

Paying 3000 euros and feeling shafted does mean we get some privilege in my book. We all know you're an Apple stockholder, stop defending Apple like it's your religion.

 

[trickness]

Speak for yourself. I don’t work in Logic and don’t give a crap about Boot Camp. I’ve already earned back the cost of the machine by using it. When the patch comes out these negative comments are going to look as ridiculous as the comments in 2016 when there were 1st generation graphics driver glitches.

It just makes humans look stupid that we have such privelaged and spoilt lives that we waste hours on forums moaning about a driver. File a feedback report for each bug instead and go do something constructive. This discussion only needed 3 pages.

Thanks! Do you have an iCrystalBall to predict how and when Apple will fix problems with my new $4K machine? Because I have 5 days left to determine whether to keep or return it, and Apple Support told me they know its an issue and can't tell me why or when it will be fixed. I don't work in Logic or Boot Camp either but it is still a problem for my work flow. So please, don't hold out on us, tell us stupid humans how much longer we have to wait for our new machines to work properly, because the company that made them aren't telling anyone squat. Which also might be why we've got a 27 page thread on this, Swami.

 

[CreeptoLoser]

Thanks! Do you have an iCrystalBall to predict how and when Apple will fix problems with my new $4K machine? Because I have 5 days left to determine whether to keep or return it, and Apple Support told me they know its an issue and can't tell me why or when it will be fixed. I don't work in Logic or Boot Camp either but it is still a problem for my work flow. So please, don't hold out on us, tell us stupid humans how much longer we have to wait for our new machines to work properly, because the company that made them aren't telling anyone squat. Which also might be why we've got a 27 page thread on this, Swami.

If Apple (or anyone) sold you a machine with faulty hardware you are not stuck with it.

Thanks for keep sounding EXACTLY like the annoying people with Radeon bugs in late 2016.

 

[tehStickMan]

Que?

This is like discussing your pay with your colleagues. If no one talks, no one knows they are being shafted.

If everyone quietly submitted a bug report, no one would know. Not the public, not potential owners, not existing owners.

Numerous people have come in here saying "oh **** yeah I have this problem too!".

Talking about the issue is better than being silent and hoping someone will Do The Right Thing (tm).
[doublepost=1534985767][/doublepost]Do you not understand that potentially all 2018 models are impacted? Your options are:

1. Deal with it.
2. Deal with it, with expectation that it will be fixed.
3. Refund and buy something else.

This is why there is discussion, to work out what's the best option for everyone personally.

You seem confident it's a driver issue, easily fixable. You're not Apple. This is why there is discussion.

 

[stailey]

I just got off the phone with Apple support and I'm returning my MacBook Pro. Bought mine the day it came out and immediately had audio dropout/glitch problems. They sent me a replacement that did the exact same thing. I'm outside the 14 day return window but they're making an exception, I told them I had zero confidence that a third MacBook Pro would solve the issue.

At this point I'm just going to keep using my Mid 2012, and if Apple releases a fix, I'll probably buy the new one again. I'd rather that than lose months off my AppleCare while my new system sits uselessly on a shelf in the hopes that Apple releases a firmware update.

 

[tehStickMan]

Yeah good call. Least you have options. I've sold my 2017 already.

 

[automan98]

I've had the speakers crackle/looping issue a few times. Interesting item tonight, while it was going on I had a call come in on my cell phone. My Mac then silenced the music to alert me of the call. After I picked up the call on my iPhone the music started playing again, but this time the audio was back to normal. Anything stand out to anyone on why the silence and restart of audio would resolve the issue for the moment?

 

[Harlowgold1]

Yes I did have that. I got mine replaced but the new one whenever I play a video, for example, the video pauses, the the video continues without audio for a few seconds. On any website.

I complained of this very problem on two different 2018 MBP's. I feel terrible that it's happening to so many people. Best of luck!

 

[kimwue]

SOLUTION:

https://apple.stackexchange.com/questions/16842/restarting-sound-service

In short: restart audio service in Terminal using:
sudo kill -9 `ps ax|grep 'coreaudio[a-z]' | awk '{print $1}'`

 

[CreeptoLoser]

SOLUTION:

https://apple.stackexchange.com/questions/16842/restarting-sound-service

In short: restart audio service in Terminal using:
sudo kill -9 `ps ax|grep 'coreaudio[a-z]' | awk '{print $1}'`

Or just right click and restart coreaudiod in the Activity Monitor.

These must be or people who think first gen drivers for new chipsets should be 100% perfect (I wish it was that easy). The rest of us know what to expect when new hardware comes out. We have back up machines, we keep working, we don’t post 500 varied speculative theories, and we hit the bug report button.

 

[Harlowgold1]

SOLUTION:

https://apple.stackexchange.com/questions/16842/restarting-sound-service

In short: restart audio service in Terminal using:
sudo kill -9 `ps ax|grep 'coreaudio[a-z]' | awk '{print $1}'`

Thank you for sharing this!

 

[dmichaelis]

Or just right click and restart coreaudiod in the Activity Monitor.

These must be people who think first gen drivers for new chipsets should be 100% perfect (I wish it was that easy). The rest of us know what to expect when new hardware comes out. We have back up machines, we keep working, we don’t post 500 varied speculative theories, and we hit the bug report button.

I send mine back, as a private I would not risk it to be a hardware issue. If apple can fix it, I may buy it again.
[doublepost=1535036220][/doublepost]

SOLUTION:

https://apple.stackexchange.com/questions/16842/restarting-sound-service

In short: restart audio service in Terminal using:
sudo kill -9 `ps ax|grep 'coreaudio[a-z]' | awk '{print $1}'`

Is there a similar solution for bootcamp?

 

[fokmik]

If apple can fix it, I may buy it again.
]

Same here...its clear, on the long run can damage even the hardware speakers, like the 2016 did under bootcamp with proper audio drivers

 

[Painter2002]

These must be or people who think first gen drivers for new chipsets should be 100% perfect (I wish it was that easy). The rest of us know what to expect when new hardware comes out. We have back up machines, we keep working, we don’t post 500 varied speculative theories, and we hit the bug report button.

I haven't been part of this discussion as I don't own a 2018 MBP, but I have to agree with your point here.

I think in today's time people have gotten spoiled with how everything works with such immediacy. People tend to forget that with new technology, there are always bugs, not because of sloppiness in the QC department, but sometimes because technology is so complex these days it is near impossible for the engineering and QC departments to consider every single possible user issue. Sometimes (like the 2016-17 MBP keyboard issues) there are legit poor design issues that should have been caught, but often software issues get through because there is so much to look at and troubleshoot on new designs.

It is good for users to post and report their issues to Apple to make sure their voices are heard, that there is a bug needing to be fixed, because without a lot of people reporting the issue it won't get fixed. But it's important to remember that being angry or impatient isn't going to help resolve issues any faster. Patience and level-headiness doesn't seem to be much of a virtue anymore.

 

[CreeptoLoser]

I haven't been part of this discussion as I don't own a 2018 MBP, but I have to agree with your point here.

I think in today's time people have gotten spoiled with how everything works with such immediacy. People tend to forget that with new technology, there are always bugs, not because of sloppiness in the QC department, but sometimes because technology is so complex these days it is near impossible for the engineering and QC departments to consider every single possible user issue. Sometimes (like the 2016-17 MBP keyboard issues) there are legit poor design issues that should have been caught, but often software issues get through because there is so much to look at and troubleshoot on new designs.

It is good for users to post and report their issues to Apple to make sure their voices are heard, that there is a bug needing to be fixed, because without a lot of people reporting the issue it won't get fixed. But it's important to remember that being angry or impatient isn't going to help resolve issues any faster. Patience and level-headiness doesn't seem to be much of a virtue anymore.

That’s right. When we try to explain from a long time user perspective that new hardware, new chipsets or new operating systems usually have a few bugs, many don’t want to listen and they need to rant and get attention. We try to calm them and give advice but it doesn’t always work because we are all strangers. They don’t know how many years you been a computer enthusiast. So they think your opinion is no more valid than theirs.

The golden rule has always been - be an early adopter only if you have a back up system and expect bugs. If you’re a new customer with no back up system, be patient. Hardware designers aren’t stupid (sound chip design is a concluded matter many years ago) and firmware isn’t easy to get right immediately. My PC has add 8 bios updates his year.

 

[Tusskan]

guys it is clearly that the issue occurs when it's 44100, want a temp fix switch it to 48000 and wait for software update from apple, software takes long time to be produced.