Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

pavvel

macrumors regular
Original poster
Jul 18, 2013
197
329
Yes incredibly annoying. Can’t believe they have left this and no fix yet!
 

mikeka

macrumors member
Jan 31, 2013
60
40
So all up to date with Catalina and just updated to Logic Pro 10.5, I thought maybe, just maybe they might have fixed something but no thump is still there. Have attached a video with the new drum synth. Should just be a single kick but as you can hear a horrible thumping, pulse sound after. I despair... :(


Working here. 2018 Mini, Catalina 10.15.5, LPX 10.5
 

randomgeeza

macrumors 6502a
Aug 12, 2014
624
460
United Kingdom
Working here. 2018 Mini, Catalina 10.15.5, LPX 10.5

I have to agree, have been trying this morning and it does seem to be working with me too... Will keep trying.

MBP 16" 2.3 i9 32G 10.15.5 LPX 10.5

Update: Left LPX open for 30 minutes and sure as **** the sound issue is there... Sigh!

NOT FIXED!

Update 2: I tried it in GarageBand, yes the erroneous sound is present but only if you sustain your key press, which differs from LPX.
 
Last edited:

primarycolors

macrumors 6502
Oct 17, 2015
328
527
CA
I'm suffering the exact same thing and I'm not entirely sure what to do either.

I've had an absolute plethora of issues with the 16" MacBook Pro including an actual hardware speaker issue. I sent it in for repair and they replaced the logic board as well as speakers, and that obviously fixed the hardware issues, but the thumping issue remains (and is not limited to Logic... it affects the entire OS when it persists but seems to be often triggered by Logic). And since I'm taking a music production class right now, this issue is really impairing my work ability. Switching the MIDI bit rate to 48,000 seems to work... but then it resets itself automatically.

I called again today and scheduled another mail-in repair, but reading all these forum posts about it, is it worth pursuing?

My return window for refund closes in two days... so I'm stuck a dilemma. Not sure if I should:
  • Miss the return window, send it in anyway, and hope it gets fixed. Either from sending it in or through a future software update.
  • Return it and buy the next gen MBP when it comes out.
 
Last edited:

pavvel

macrumors regular
Original poster
Jul 18, 2013
197
329
It is software. Finally got someone good at Apple and they say they will be fixing in software update.
 
  • Love
Reactions: primarycolors

primarycolors

macrumors 6502
Oct 17, 2015
328
527
CA
Decided to send it in and asked me for more info on how to reproduce the issue. They could not reproduce the issue and sent it back.

I got it back, booted it up, and issue was right there.

This is agonizing :(
 

robes1

macrumors member
May 20, 2016
70
32
Decided to send it in and asked me for more info on how to reproduce the issue. They could not reproduce the issue and sent it back.

I got it back, booted it up, and issue was right there.

This is agonizing :(

Do you get the issue only through your internal speaker, or does it come through headphones, monitors, etc?
 

primarycolors

macrumors 6502
Oct 17, 2015
328
527
CA
Update: 10.15.6 does not fix the issue. It's so frustrating that this issue seems to have no end in sight. :(
 
Last edited:

primarycolors

macrumors 6502
Oct 17, 2015
328
527
CA
Update.. MacOS Big Sur public beta does not resolve this issue either. I'm gonna cry!
 
Last edited:

ClyLunt

macrumors newbie
Oct 27, 2020
1
1
Hello...same issue here, makes watching instructional exercises as I code exceptionally troublesome lol. The issue is by all accounts conflicting and can some of the time be fixed with a restart. Any sound originating from any application is incredibly mutilated while Xcode is open; it begins when I run the see or test system in with SwiftUI.
 
  • Like
Reactions: primarycolors

primarycolors

macrumors 6502
Oct 17, 2015
328
527
CA
BIG update on this.

I continued kindly pressing Apple Support and getting transferred higher and higher, and from department to department. I stressed how unfair it is, that owners of $2.3k+ MacBook Pros have no clear solution in sight, no end of the tunnel, just the unsatisfying hope of a "possible software fix somewhere down the road."

Long story short, after a lot of phone calls and diagnostics and submitting data, the problem now has its own official engineering case between the the software team and hardware teams (it's a combination issue, I've heard). They've been finally working together to fix it, and it's been finally (mostly) fixed in the current Big Sur beta since I pressed them about it. Fingers crossed it'll be all gone in the final :)
 
Last edited:
  • Like
Reactions: pavvel

pavvel

macrumors regular
Original poster
Jul 18, 2013
197
329
BIG update on this.

I continued kindly pressing Apple Support and getting transferred higher and higher, and from department to department. I stressed how unfair it is, that owners of $2.3k+ MacBook Pros have no clear solution in sight, no end of the tunnel, just the unsatisfying hope of a "possible software fix somewhere down the road."

Long story short, after a lot of phone calls and diagnostics and submitting data, the problem now has its own official engineering case between the the software team and hardware teams (it's a combination issue, I've heard). They've been finally working together to fix it, and it's been finally (mostly) fixed in the current Big Sur beta since I pressed them about it. Fingers crossed it'll be all gone in the final :)
Ah that's great to know. I have been down pretty much the same patch as you for months and have been told the engineering team is fully aware of this and working it. I haven't tried any Big Sur Beta but looking forward to installing on release and hopefully this issue being fixed.

Thanks for your update :)
 
  • Love
Reactions: primarycolors

mattyjoe

macrumors newbie
Oct 12, 2020
20
107
Los Angeles, CA
If anyone else with the 16inch notices an improvement with this issue, and the latest version of Big Sur, please keep us posted. This is giving me hope right now.
 
  • Like
Reactions: pavvel

aizarged

macrumors newbie
May 28, 2020
17
4
Anybody knows if Big Sur fixed it? I know it worked for a few, but would like to have more people confirm it before thinking of upgrading.
 

eotunes

macrumors newbie
Mar 4, 2021
2
1
Here is a workaround for getting my MacBook Pro 16-inch running Catalina 10.15.7 working with Logic Pro X 10.6.1 to play on the internal speakers without the crackling, grumbling, grating sound.

As others have said, there is no problem with the signal delivered to the earphone jack. And also, as others have said, using a 48K sample rate makes it go away on the MacBook speakers.

In Logic:
1. If you are working on a project that was recorded in 44.1K, open the bin, select all, and use the local Audio File menu / Copy/Convert files to set 48K for all of them. Save.

2. Set your Project sample rate to 48K instead of 44.1K. Save.

3. For convenience, I now use Logic templates, pre-saved with 48K set in the project as the sampling frequency.

MacOS:
Setting the project’s sample rate to 48K normally sets the operating system to use 48K too. You can verify in the Audio MIDI Setup app. You also use this app to set the system audio to 48K.
If there is a 44.1K/48K mismatch between the file you play and the operating system sampling frequency, tunes will have the wrong pitch.

Hope this helps some of you until Apple gets its act together. I have heard some claim it's a software problem, and others swear it's because of a new security chip (hardware). I wonder if it has something to do with feedback (speakers and mics so close).
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.