Happy New Year to all colleagues. Help advice. MacBook 16, Logic latest version. When playing a project in 44.1 popping, if a project in 48 is not. Core Audio Driver At the maximum value of the buffer, the crack becomes less frequent but does not disappear. Clicks remain during playback through iTunes, Garageband. When closing the logic, there are no clicks in the iTunes. External Apollo works flawlessly. I hope for your help.

 

This issue is happening since the 2016 MacBook Pro. I'm having it on my 2017 MacBook Pro too.
Here's the fix: https://github.com/mttrb/antipopd
Make sure it's installed correctly -> you'll see antipopd running in your activity monitor.

 

In the evening I’ll try and write about the result. thanks
If it does not help, I will change it under warranty. The prefix PRO they need to be removed in the name of the computer

 

What specs do you have? How many vst plugins can you load without problems?

 

Are you connecting your interface through USB? It might be the T2 chip, a known flaw with Apple computers for the last few years. Louis Rossman made a video about it:

.

It's pretty scary. I'm in the need for a new Mac (I need it for backwards compatibility at work and have an extremely extensive project upcoming next month and no time to consider switching OS) and I'm terrified to pull the trigger on a new machine.

 

Apple: it is a feature, not an issue.

 

from the yt comment: "Apple has abandoned creatives for the deconstructed latte hipster Instagram crowd."

I know you don't get much help from this but for others who have plans to buy new MBP16.
In my opinion the mac disappeared with the 2013/2015 model.
Tim Cook needs to leave apple as soon as possible, until it's too late.

 

Last edited by a moderator: Jan 3, 2020

And most importantly, whether they fix it or not in subsequent updates is unknown. I do not want to take risks, I will return...
What do you advise, leave the computer or carry change? It is possible that in the new Mas that they will give me, the very problem will remain

 

Last edited: Jan 3, 2020

This happened to me when i first hooked up a large external hard drive and apple runs its indexing process. The indexing process puts the audio core drive as a secondary priority to indexing speed. All you need to do is force close the coreaudiod process and it should clear the issue. Doesn't cause any problems when using an audio interface which is 90% of the time when working.