Hello, is it anyone here ( or on this planet ) that can help with this issue on Catalina Mac OS 10.15.5 Beta 3 (19F72f).
I am using MacBook Pro 16 inches. 😟
How to Fix Cracking and Popping Sound ?
This error is also reported in the community forums: https://origin-discussions-us.apple.com/thread/253681560
I'm getting the same error in the console when my 2021 M1 14" Macbook Pro 32GB RAM goes above ~25GB RAM usage. This error is from the coreaudiod process and libAudioStatistics.dylib library:
"HAL_client_IO_duration" = 106833;
HostApplicationDisplayID = "com.spotify.client";
cause = PageFaultsOffIOThread;
deadline = 69794966;
"input_device_source_list" = "";
"input_device_transport_list" = "";
"input_device_uid_list" = "";
"io_buffer_size" = 512;
"io_cycle" = 136317;
"io_cycle_budget" = 12358250;
"io_page_faults" = 0;
"is_prewarming" = 0;
"is_recovering" = 0;
"issue_type" = overload;
lateness = 174;
"other_page_faults" = 29;
"output_device_source_list" = "Internal Speaker";
"output_device_transport_list" = BuiltIn;
"output_device_uid_list" = BuiltInSpeakerDevice;
"safety_violation" = 0;
"sample_rate" = 44100;
"scheduler_latency" = 15497916;
"smallest_buffer_frame_size" = 512;
}: (
2632814952562
)
Just milliseconds before it the Spotify process issued this console error message from the CoreAudio library:
HALC_ProxyIOContext::IOWorkLoop: skipping cycle due to overload
This is definitely a bug related to memory usage. I've reported it as so and linked both community and dev forum posts. I suggest everyone reading this does the same so that it will sometime in the next decade be fixed. Link to report Macbook Pro bug: https://www.apple.com/feedback/macbookpro.html
I've been experiencing the same issue on my 2022 M1 MacBook Pro (with OS 12.3.1, 12.2, and previous versions). Based on this thread, I started searching Console for "CAReportingClient", and an entry like this appears consistently every time I hear the glitch. I've noticed it on Spotify and Music.app. It seems to happen most often when I close a Chrome tab.
CAReportingClient.mm:508 message {
"HAL_client_IO_duration" = 1087958;
HostApplicationDisplayID = "com.spotify.client";
cause = PageFaultsOnIOThread;
deadline = 124749382;
"input_device_source_list" = "";
"input_device_transport_list" = "";
"input_device_uid_list" = "";
"io_buffer_size" = 512;
"io_cycle" = 9713;
"io_cycle_budget" = 12358250;
"io_page_faults" = 1;
"is_prewarming" = 0;
"is_recovering" = 0;
"issue_type" = overload;
lateness = 8;
"other_page_faults" = 34;
"output_device_source_list" = Headphones;
"output_device_transport_list" = BuiltIn;
"output_device_uid_list" = BuiltInHeadphoneOutputDevice;
"safety_violation" = 1;
"sample_rate" = 44100;
"scheduler_latency" = 11093791;
"smallest_buffer_frame_size" = 512;
}: (
1782411428173
)
Nothing changed, my MacBook Pro 16 2021 gave back to Apple to change the speaker and battery, the cklicking still exist, but sometimes, depends if you open a browser with a sound content etc. thought at beginning it is a hardware issue, because the crackling sound appears even when booting up, before booting up, before loading the MacOS, i still think this has nothing to with the MacOS version, even not with speaker, because they changed it, so the problem is really somewhere else. just my personal advise, use it as it is, don’t focus on sound, otherwise you will get crazy, and hope that the next versions of Hardware are much better. still we have to accept the other way, this MacBooks are the ***** of the technology these days and nothing can beat them, I do any tasks you imagine in within few seconds compare to the much expensive Windows crap machines.
I have the same problem with my MacBook 16 inch 2021 with M1 Pro. It is very annoying when you hear this popping sound when playing music or watching a movie. And it has only been 2 weeks since I bought this machine. Is there any solution to this problem?
On MacBook Pro (16-inch, 2021), Apple M1 Pro, I've found that resetting the PRAM resolves the issue for a day or two. Then the problem increases by time.
As explained a few days ago on Reddit, it seems that Intel processes which are "non-native" for Macs running on M1 processors seem to be the culprit here.
Check the Activity Monitor for any processes in the CPU view listed as type "Intel". The type column might be hidden, so you need to unhide it. I've noticed that if I avoid running any applications which spawn Intel type processes, I don't get any distortions or issues. However, even music players like Qobuz still run as an Intel process, and one or two processes is generally fine. However I get too many of those Intel processes running, the popping etc starts happening immediately.
I guess it might be something to do with how the Rosetta 2 translator handles those kind of processes and too much CPU and/or memory consumption starts causing problems.
I have updated Java, node etc. to run natively as Apple processes. Unfortunately many apps I need for work still run non-natively on M1 Macs and thus causing problems with audio.
I'm running a MBP 16-inch M1 and have ONLY "Apple" processes running, and still get the audio cracking, so unfortunately the prior comment from valjento is not the full story. I do think it's more of a memory pressure issue. It's obviously maddening as hell, so hopefully it gets fixed within the next 10 years.
I can't take it anymore, it's pathetic. I have to reboot regularly a 3000 euros professional machine from a company that makes both hardware and software because i have buzzing/clicking sounds in my headphones or speakers connected to a proper amplifier.
Nowadays it comes to a point when I have it connected to my monitor with usb-c, even from scrolling or loading some pages on browser make the buzzing sound appears all the damn time. I hate it. I don't live to a country with an Apple store, nobody will take this to give me a new one here, but it's not uncommon as far I see here or on reddit.
Absolutely insane, a shame. My 4y old 850 euros Xiaomi hobbist hackintosh, experimenting as student without much money, had clearer audio output.
I got a reply on my submittion at Feedback Assistant, I replied back sending a .ktrace file but I haven't heard back for whole 2 months. Rip. We may hope that new os version update will fix it but I doubt at this point.
For anyone that is still looking for a fix for this - on my new Macbook 14" M1 Pro the solution was the following:
- Open up a terminal window
cd /Library/Preferences/Audio
sudo rm com.apple.audio.*
- Breath easy and listen to music without annoying AF pops and crackles
I have this issue!
My Mac is few months old and it just started yesterday! Why does this happen? First time was on YouTube, I and was 100% sure, that my 6.000$+ laptop didn't make this sound, I went a little back in the video - and thank god it was still there - then I tried going back again, just to be sure - and now NO SOUNDS!!! What the danm Apple! I think it is when the machine is under heavy load, but yeah this laptop Apple M1 Max with full specs, so expensive - but I was sure I wouldn't do such a thing!
The actual problem is right here:
I'm sorry, but I don't know how to do anything about it - if you do, please tell me what to gather of other informations!
default 00:52:29.068202+0200 coreaudiod index: 1, start: 0x4ed87457e7, duration: 0x57, fault address: 0x170a60000, fault pc: 0x1071a6e94, faulting TID: 0x22161, fault type: 0x1, PID: 0x1829
default 00:52:29.068643+0200 coreaudiod index: 2, start: 0x4ef420a99d, duration: 0x67, fault address: 0x170ae8000, fault pc: 0x1071f3ae4, faulting TID: 0x22166, fault type: 0x1, PID: 0x1829
default 00:52:29.068830+0200 coreaudiod index: 3, start: 0x4ef420aa27, duration: 0x19, fault address: 0x170aec000, fault pc: 0x1071a6e94, faulting TID: 0x22166, fault type: 0x1, PID: 0x1829
default 00:52:29.069006+0200 coreaudiod index: 4, start: 0x4f0fe02c13, duration: 0x1b6, fault address: 0x131830000, fault pc: 0x184f7ae8c, faulting TID: 0x22166, fault type: 0x1, PID: 0x1829
default 00:52:29.069175+0200 coreaudiod index: 5, start: 0x4f0fe02df9, duration: 0x3f, fault address: 0x131834000, fault pc: 0x184f7ae8c, faulting TID: 0x22166, fault type: 0x1, PID: 0x1829
default 00:52:29.069413+0200 coreaudiod index: 6, start: 0x4f1946d84f, duration: 0x21d, fault address: 0x131838000, fault pc: 0x184f7ae8c, faulting TID: 0x22166, fault type: 0x1, PID: 0x1829
default 00:52:29.069598+0200 coreaudiod index: 7, start: 0x4f1946dac1, duration: 0x53, fault address: 0x13183c000, fault pc: 0x184f7ae8c, faulting TID: 0x22166, fault type: 0x1, PID: 0x1829
error 00:52:29.069854+0200 coreaudiod 3331 HALS_OverloadMessage.cpp:218 HALS_OverloadMessage: Overload due to HAL client proc exceeding io cycle budget
default 00:52:29.074139+0200 coreaudiod Audio IO Overload thread: 22166 inputs: '<private>' outputs: '<private>' cause: 'Unknown' prewarming: no recovering: no
default 00:52:29.074431+0200 coreaudiod CAReportingClient.mm:508 message {
"HAL_client_IO_duration" = 32055166;
HostApplicationDisplayID = "com.ColossalOrder.CitiesSkylines";
cause = ClientHALIODurationExceededBudget;
deadline = 3541862;
"input_device_source_list" = "";
"input_device_transport_list" = "";
"input_device_uid_list" = "";
"io_buffer_size" = 1024;
"io_cycle" = 112;
"io_cycle_budget" = 21354125;
"io_page_faults" = 0;
"is_prewarming" = 0;
"is_recovering" = 0;
"issue_type" = overload;
lateness = 557;
"other_page_faults" = 8;
"output_device_source_list" = "Internal Speaker";
"output_device_transport_list" = BuiltIn;
"output_device_uid_list" = BuiltInSpeakerDevice;
"safety_violation" = 1;
"sample_rate" = 48000;
"scheduler_latency" = 18083;
"smallest_buffer_frame_size" = 512;
}: (
26564372725762
)
From my side, since last macOS update, and since I have deleted this
sudo rm com.apple.audio.*
and staying careful to not have "any" intel process, I feel like it's a bit better.
Each time I got crackling I had a Intel process type in the list (like Loom, Skitch, etc.)
.
Can some ones of you confirm you all have always active these 2 onces as Intel process ? :
- Core Audio Driver (Speaker Audio Recorder.driver)
- CarbonComponentScannerXPC
Same problem with 14" MacBook Pro (M1 Pro). It seems that the sound experience starts degrading quickly after a reboot. I'm a developer and I can clearly see that launching a java or node process impacts negatively. First my USB DAC (FiiO K3) starts getting sound cuts. Then my Kanto TUK (connected via USB as well) start to crack some hours after. Then even the sound directly from the mac is getting impacted.
This has been happening for months, and no fix seems to be available. Restarting coreaudiod doesn't fix much, it starts happening again quickly.
All this equipment works FLAWLESSLY on my Windows desktop. This is rather annoying since the laptop is three times more expensive. Also, image retention problems in my external screen that doesn't happen on my desktop. Clearly the OS needs some polish in these areas.