M1 MacBook Pro audio glitch

Just received new M3 iMac, same audio issue. Randomly all audio cut outs for a moment. Does not matter what the audio source is. Very disappointed and frustrated.

I'm having the same problem. I'm loosing audio from all the outputs of the macbook (through USB, hdmi, or even the macbook speakers themselves). Very annoying when you're having a call...

One solution that works (for 5min :') ), type this in a terminal:

sudo killall coreaudiod

It's not an audio/speaker problem, it's a M1 hardware problem. If I could turn back time I would never have bought the M1. It's only a year old and is a piece of junk. I have sent it to Apple and back again, run through numerous trouble shooting help, tried all the online advice, and it always comes back.

I am a music producer and I have to restart my computer at least twice or more times a day to stop the popping and glitching. The more programs you have running the worse it gets, until things are so slow you can't even load a page.

I have been a Mac user for years, but this has seriously made me consider never buying Apple again. They've lost the plot.

Greetings grumpbus,

Ensuring you're getting the audio quality that's expected from your Mac is important and it sounds like you've walked through great steps thus far. If you haven't already, you'll want to complete the steps listed below. These steps are specific to troubleshooting speaker related issues on your Mac.

1. "From the Apple menu , choose System Preferences.
2. Click Sound.
3. Click the Output tab, then select the built-in speakers. If you don’t see built-in speakers as an option in the Output window, contact Apple Support.
4. If the Output volume slider is set low, move the slider to the right and test again.
5. If the Mute checkbox is selected, deselect it and test again.
6. If you still don’t hear any sound, contact Apple Support."

If the internal speakers on your Mac aren't working

If you continue to have issues after completing the steps, you'll want to reach out to Apple next so they can look in to this issue further. You can find their contact details via the link below.

Contact - Official Apple Support

Take care!

I've been trying to deal with this problem for more than a year, and honestly, it's absurd that a machine with a price tag of over $3,000 can't play audio correctly. It's even more frustrating because I genuinely enjoy working with Apple devices, but this issue renders them practically unusable as workstations for developers like me.

I don't believe there's just one issue at play here. At times, it's the memory pressure, the core audio daemon, or even "insulated cables" (seriously?) - Apple's response in this thread to "check your audio settings" is practically offensive. You'd likely receive an equally unhelpful response by visiting any Apple Store. They're well aware of the problem but feign ignorance to avoid massive recalls.

Super frustrated, Apple, do something!

Very true. I have the M1 Max 16-inch Pro. The audio glitches every few minutes. It really interrupts the listening experience. I'm listening through Apple music so it's not a software compatibility issue. If Apple's own software can't play perfectly, I don't know what else can. Actually, as I just clicked on the Post button for posting this comment, the audio popped.

I am wondering if this is related to what I am observing.

It seems that every time an alert is fired off. ie Doing something wrong in Finder, triggering an alert sound (which you can't turn off like you can other notification sounds, you can only turn it down), I get an interrupted audio stream in Apple Music for example.

Even worse, it will cause ProToolsUltimate to stop playing or recording and throw an error, regardless of buffer size etc.

Also affects the playback in Logic Pro X.

I am using a Mac Studio Ultra that is otherwise not breaking a sweat, so it seems that it is something to do with that trigger fires off the sound.

I have an RME UCX II and Ableton Live. I was getting an audio cut out about every 30 seconds to a minute. I then closed Safari, and haven't heard the issue since. I've been running Firefox, and haven't had the issue with it.

Update: I just upgraded to Ventura, hoping, by some miracle, it would fix this horrible audio glitch problem.

If possible, it has actually made it worse!

It's nearly impossible to record on Logic without the glitch stopping a recording mid-track. This is now a major issue.

I'm looking for ways to move my logic off this terrible M1 and go backwards instead of forwards.

Worst decision to buy an M1.

Apple, in my opinion, has gone down the toilet.

:(

This is extremely frustrating. We deserve at least an official response. This is supposed to be profesional hardware.

This ONLY happens to me on my work 14" MBP with an M1 Pro chip. My personal M1 MB Air works fine.

I like listening to lossless audio and have a DAC hooked up with monitor speakers, so this problem is pretty irritating. It does not happen when I use my Airpods Pro, but I'd really like to not have earbuds in my whole workday.

Any fixes would be appreciated.

Yes, unfortunately, this problem has returned on my systems again. Initially OS 13.3 was working extremely well, but has since deteriorated once again.

I am having to use CPUsetter to "re-nice" Logic to -20, to prioritise its audio. (I do the same with Pro Tools when using that too.

I am clutching at straws here, but I did get some temporary relief by force quitting a process I observed in the activity monitor when there was severe audio glitching happening.. It repopulated shortly after force quitting, but just an idea. (screensharingd)

I’ve fixed the problem!

I ditched my $3000+ 2022 M1 MacBook and went back to my older 2017 intel mac. I updated and loaded Ventura, LogicProX and all the updated plugins and it all runs like a dream.

I’ll only use the M1 for menial work, that all it’s good for.

[Edited by Moderator]

I experience the issue when playing music through my Sound BlasterX G6 usb DAC. The sound cuts around every 10 seconds. But when I switch to internal speakers, all is good. It was not the case by the past on my Intel MBP