As someone who uses a T2 Mac just for music listening, the 1-3 dropouts I get a day are not that big a deal. However, I don't know how anyone could use it for audio production.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacBook Pro 2018 - Speakers Crackling
- Thread starter jaack
- Start date
- Sort by reaction score
it can become a nightmare. especially if you're doing some recording or mastering.
yes I have been experiencing problems with my Mac, considering I only bought it less than a month ago. when I play any audio weather that be music or even when watching a movie, they are fine for about half an hour - three quarters of an hour but afterwards they begin to skip and crackle!
I have contacted apple about the problem and they just told me too update the software to the new MAC MOJAVE update and the reset the NVRAM and the PRAM, however this didn't not seem to work.
I don't know if anyone else has tried to do this but it is getting to the point where I feel like apple are trying to fob me off because they seem to have a lot of users contacting them about this problem?
@ everyone... were you guys using a usb interface? I plan to do some pro audio with a UAD thunderbolt interface. So far I haven’t experienced any crackling with my 2.6 15 inches using internal speakers or headphones. Bluetooth is off
Mine is USB, I also tried to get on amazon zoom tac 2r (thunderbolt) and it still had problems, but it was long time ago, returned it a week after testing.
though, I've heard quite some folks that thunderbolt 3 interfaces (uad arrow or 8x new lineup) are rock steady, also a couple of folks with tb2 Antelope Zen Tour interface don't have any problems.
P.S. If you're really considering what you do "PRO" then the best thing you could do is set-up a separate user for work, especially recordings, and disable all the internet stuff, bluetooth and other networking features as they somehow correlate with USB. But I have this issue SO rarely and even while it happened to output couple if times while recording, the recording itself wasn't damaged and all it was just a superquick milisecond "crk" once. So apart of that it's rock stable and doesn't bother me anymore as it was in the beginning (horrible, I wanted to smash this laptop against the wall)
It was just simple. If it was fixed in mojave, it was software bug and if it was not fixed, it was hardware problem.
Anyone know how iphone been manufactured ? The company would request some of oem manufacturers to give their prices, later apple would choosed oem manufacturer willing to give lowest price. Maybe they also do same way for macbook pro.
They have selling cheap product in hight price. So don't hope you got hight quality product.
Anyone know how iphone been manufactured ? The company would request some of oem manufacturers to give their prices, later apple would choosed oem manufacturer willing to give lowest price. Maybe they also do same way for macbook pro.
They have selling cheap product in hight price. So don't hope you got hight quality product.
Well, unfortunately this is what happened to me today... I was using Spectrasonics Keyscape (A high CPU Virtual instrument) in Logic Pro X @ 64 samples Buffer on the internal audio through the MBP Speakers. I went on Youtube to get some info about something and then... The crackling began, electrical noise style really loud crackling occured. So I though I was not touched by this plague but it just feels like I am now. Tomorrow is my last day for returning the MBP.
Wifi was on and I had an external SSD via USB-C to USB3 adapter plugged in that's it. So dissapointed.
Wifi was on and I had an external SSD via USB-C to USB3 adapter plugged in that's it. So dissapointed.
well, feel free 2 do what u want, but on 64 buffer launching cpu intensive plugin and then pretending it will run flawless with other stuff going on is kinda suicidal move, dude.
Idk, maybe you're new to that maybe not, but believe me t2 doesn't matter here at all, it's just plain cpu overload. go do the same on windows machines or other macbooks without t2 (i had 2016 for example)
though, AFAIK, keyscape is more sample based rather than cpu based...
Yes I've been able to reproduce it. Just on the macbook speakers and headphones, (internal audio) Load up a Virtual Instrument in 64 buffer size in Logic pro X. Record 1 track, let it play.
Open Firefox, Chrome or Safari and Browse Facebook or Youtube etc...Play with your trackpad... It messes up the sample rate and starts making LOUD electrical bursts and noises. Almost blew up my headphones and then speakers.
@8SlaiN8, I don't see this as normal CPU spikes since I've tested it on my 12 core 5,1 Mac Pro with Metric Halo ULN-2 FW400 interface with the same Keyscape preset and buffer size and in no way my CPU is overloading nor I hear noises or crackling.
I see the Overloading Core audio messages in the Console.
I did not test with an external TB interface, but the point of owning a laptop for me is to compose and edit on the road on tour or on the couch at home, so I'd like to keep the setup as compact and portable as possible.
Wanted to post an update...
I cloned my pre-Security Update backup to my internal disk. I have not had any crackling since Saturday...
(This includes a few 5-6 hour DAW sessions, one in Logic, one in Live.)
If you didn't experience the issue right away I'd consider either cloning a backup you made with CCC to an external disk or new partition/volume then booting from it to see if it sorts the issue out for you... (Leave your old volume there until you confirm it does or doesn't help. More on that below...)
If you don't use CCC another thing you might try is creating a new partition or container volume on your internal disk, then restoring to the new partition/volume from a TM backup made before you noticed distortion. Then set the restored volume as the startup disk and stress test it for a few days to see if it works. If it seems to do the trick you'll then need to clone the volume back using CCC, PLEASE READ BELOW, and email Bombich before you do...
Do not wipe your current internal Macintosh HD volume if using Time Machine.
Clean installing the OS from a bootable drive doesn't work the way it did on previous Macs, some people have not been able to boot after trying to clean install... It's related to some kind of security feature of the T2 that I don't fully understand yet... Also, just using recovery to internet restore will most likely reinstall the updates that seem to trigger the issue...
(I don't know for sure if the updates are the only source of the issue, I just know they were for me... That said it would explain all of the discussion about bridgeOS since Security Update 2018-002 had a ton of bridgeOS updates, some coreaudio and IO updates, as well as some OS specific firmware...)
Unfortunately if you bought the machine with Mojave and had the issue from the get go I don't know a solution yet due to the clean install issues mentioned above... And since I'm still on HS (and don't plan on going near Mojave anytime soon) I don't know if Security Updates 2018-002 and 2018-003 came bundled from the factory with Mojave installs...
Anyway fingers crossed... Hoping this works for others as well!
[doublepost=1547200527][/doublepost]One other thing...
If you use CCC you should have local snapshots of your clones unless you've disabled this feature. (They're on by default.) Assuming you do, you can mount the oldest snapshot while booted to your current volume, then clone the mounted snapshot to an empty partition/volume and boot from it for stress testing...
Again, leave your old volume behind until you confirm it does or doesn't work...
Another thing you may not be aware of in CCC is the ability to restore only the OS from a local snapshot.
I tried this and it didn't work for me however I'm pretty damn sure this was strictly because of my SafetyNet settings...
In that case email Bombich and ask them how to clone the current volume to a new volume first, then fully restore only the OS from the older snapshot to the cloned volume, with SafetyNet turned off ... (SafetyNet won't overwrite modified files unless it's fully disabled. Since the Security Updates modified some of the OS's files SafetyNet leaves the updated files alone, leaving the problem hanging around... I didn't find an article about this until I'd already cloned back... Luckily it went ok.. In hindsight I would have played it safe.)
As long as you leave your current volume intact you have nothing to lose other than the few minutes it takes to clone to a new volume... Then just set it as the startup volume and test...
I cloned my pre-Security Update backup to my internal disk. I have not had any crackling since Saturday...
(This includes a few 5-6 hour DAW sessions, one in Logic, one in Live.)
If you didn't experience the issue right away I'd consider either cloning a backup you made with CCC to an external disk or new partition/volume then booting from it to see if it sorts the issue out for you... (Leave your old volume there until you confirm it does or doesn't help. More on that below...)
If you don't use CCC another thing you might try is creating a new partition or container volume on your internal disk, then restoring to the new partition/volume from a TM backup made before you noticed distortion. Then set the restored volume as the startup disk and stress test it for a few days to see if it works. If it seems to do the trick you'll then need to clone the volume back using CCC, PLEASE READ BELOW, and email Bombich before you do...
Do not wipe your current internal Macintosh HD volume if using Time Machine.
Clean installing the OS from a bootable drive doesn't work the way it did on previous Macs, some people have not been able to boot after trying to clean install... It's related to some kind of security feature of the T2 that I don't fully understand yet... Also, just using recovery to internet restore will most likely reinstall the updates that seem to trigger the issue...
(I don't know for sure if the updates are the only source of the issue, I just know they were for me... That said it would explain all of the discussion about bridgeOS since Security Update 2018-002 had a ton of bridgeOS updates, some coreaudio and IO updates, as well as some OS specific firmware...)
Unfortunately if you bought the machine with Mojave and had the issue from the get go I don't know a solution yet due to the clean install issues mentioned above... And since I'm still on HS (and don't plan on going near Mojave anytime soon) I don't know if Security Updates 2018-002 and 2018-003 came bundled from the factory with Mojave installs...
Anyway fingers crossed... Hoping this works for others as well!
[doublepost=1547200527][/doublepost]One other thing...
If you use CCC you should have local snapshots of your clones unless you've disabled this feature. (They're on by default.) Assuming you do, you can mount the oldest snapshot while booted to your current volume, then clone the mounted snapshot to an empty partition/volume and boot from it for stress testing...
Again, leave your old volume behind until you confirm it does or doesn't work...
Another thing you may not be aware of in CCC is the ability to restore only the OS from a local snapshot.
I tried this and it didn't work for me however I'm pretty damn sure this was strictly because of my SafetyNet settings...
In that case email Bombich and ask them how to clone the current volume to a new volume first, then fully restore only the OS from the older snapshot to the cloned volume, with SafetyNet turned off ... (SafetyNet won't overwrite modified files unless it's fully disabled. Since the Security Updates modified some of the OS's files SafetyNet leaves the updated files alone, leaving the problem hanging around... I didn't find an article about this until I'd already cloned back... Luckily it went ok.. In hindsight I would have played it safe.)
As long as you leave your current volume intact you have nothing to lose other than the few minutes it takes to clone to a new volume... Then just set it as the startup volume and test...
Last edited:
You got me confused here. Are you saying it is the Security Updates that caused your crackling issue? I thought they were supposed to fix them.
Yup. At least for me that was the case...
https://forums.macrumors.com/thread...akers-crackling.2128234/page-49#post-26923285
Yeah in theory they should... All I know is crackling showed up as soon as I did a back-to-back install of 2018-002 and 2018-003... Since rolling back the issue's gone.
The Logic errors I posted in the thread above started the day after I installed them and sure sound like the crackle is jitter... After reading up about other errors I've seen in Console seems like it might be related to a buffering or core audio driver error.. (All of which the T2 chip manage.)
Anyway... I keep auto-updates turned off in the App Store and run CCC before installing any kind of OS/security update for exactly this reason. Recommend others do too until Apple get their **** together.
Last edited:
I went online to tech support because I had the same crackling issue on my MacBook Pro i9 32GB 1TB 2018. I just wanted to do a chat quickly to at least get another issue in their logs, but they instead wanted to talk to me about the issue, so tech support called me the next day.
This is what happened: I first told them that I understand about when new technology comes out and of course there is sometimes difficulties and therefore was not rude to him nor irritated, but explained I just want this fixed. I stated that I am on High Sierra and want to stay with the OS that came with the system, for I have software that works with High Sierra and does not work with Mojave and I am kind of stuck to not upgrade.
I further explained to him that I did some research before calling and wanted to resolve the issue etc. After showing that I was not going to be a jerk (though I was upset after spending over $4,000, but held it in) and told him that I already knew that he will tell me to upgrade to Mojave as the solution, he tried first to help me, but nothing resolved the issue.
I also asked him does his records show that it is a T2 chip problem and if maybe he could share what his engineering department said is the issue (if he could tell me). I told him I understand that he cannot tell me much...but again since I was cooperative (nice) with him, he said that he would look through what engineering has said and then put me on hold. He came back a few minutes later and said that it is a known issue by apple engineering and that it is a software related issue. By upgrading to Mojave, it should resolve the issue. but if it continues, after upgrading, then you can send it in for repair. I told him that I would rather not send it in (I had issues before when product returning form repair), so we did some other checks, but no resolution.
Unfortunately..The solution: Upgrade to Mojave...that is of course not acceptable (sloppy engineering). Can't do a recall or lawsuits on MacBook pros if there is a software fix. So we are just stuck and have to upgrade. And Apple is covered.
If it is a software issue, then it can be fixed in High Sierra. Apple DOES NOT want to go back and work on the last version to fix it since they have moved on to a new OS. We have no choice if it is not a hardware issue. The tech said to try using bluetooth headphones or external audio options through the headphone jack and that some people have had good experiences with that if I have to stay on High Sierra...but that defeats the purpose of having a laptop...
So...if it is a software issue, that means Apple corrected a few files in Mojave. isn't Mojave REALLY just an upgrade version of High Sierra? The tech kind of hinted that it is an audio issue...so why not copy all of the audio related files, core audio files etc. from Mojave and port them into High Sierra and see if it resolves the issue...? I am willing to try, but do not know which audio related files to port. MAYBE that might fix the issue? I am willing to try.
If someone who knows more about macOS (developer etc.) could tell me what files to grab, I will do it and try. I want to stay on High Sierra and will try anything to avoid upgrading right now.
If it is a software fix, what files were fixed?
Can anyone tell me what files to try? Thanks.
I am going to *cautiously* declare that 10.14.3 beta4 has improved matters considerably for me.
As somebody who has forked out 4k for something to make music on, at 11 days in out of my 14, I was just about ready to return it. Under 10.14.2 I was getting constant clicks and pops.
With the beta I am now largely down to the once a minute smart battery manager click if the first core is heavily loaded. Why can't Apple fix this CPU spike after six months ?
If I really monster the first core with Live, Logic and VCV Rack all running big patches at once then I can get dropouts but running exactly the same on my maxed out 2015 iMac the i9 MBP actually has less dropouts.
I would be interested to hear any other success stories. 3 days to go (and the Vega 20 screen flicker is NOT fixed yet).
As somebody who has forked out 4k for something to make music on, at 11 days in out of my 14, I was just about ready to return it. Under 10.14.2 I was getting constant clicks and pops.
With the beta I am now largely down to the once a minute smart battery manager click if the first core is heavily loaded. Why can't Apple fix this CPU spike after six months ?
If I really monster the first core with Live, Logic and VCV Rack all running big patches at once then I can get dropouts but running exactly the same on my maxed out 2015 iMac the i9 MBP actually has less dropouts.
I would be interested to hear any other success stories. 3 days to go (and the Vega 20 screen flicker is NOT fixed yet).
My matters have progressively gotten worse, I'm considering sending it in for repair just to see what happens (that is if they dont offer me a direct replacement), I have a backup 2016 I can use for a while.
My issues are routed towards bluetooth, i've removed the possibility of USB interference. 10.14.3 should be released very soon, hopefully this week. Given the two betas days between each other. That will be the final straw, thats 6 months, plenty of time to resolve an issue.
I fully understand that by changing some lines of code for audio on the T2 chip can lead to widespread problems with other components within the mac, so its not just as easy as that. But 6 months is surely the deadline.
I wish I had an answer for this... That said, there were a lot of audio extensions and frameworks updated in the Security Updates that caused issues for me. Below are a few screenshots of what was updated with audio related files marked in red.
Also note the modified timestamp, (just so you can confirm these were modified during the updates....)
As far as files that show dates in late November just be aware these are the build dates shown in timestamps... The actual install date for me was Dec 9th, and I've confirmed this by using spotlight to show only modified files from that date...
As you can see System Information makes it seems like less files were modified, but when you actually look in hidden folders you find there are a ton of files updated that either correspond to the extensions and frameworks or don't disply there because they're hidden by default. Many of which are system audio files... (This is also only a tiny portion of files I found modified that date... There are TONS...
You can also see bridgeOS was updated.
And a firmware update was also deployed...
Some of the files that might not seem related at first glance, as far as I've been able to get info about, handle hardware drivers... E.g. IOKit for example deals with drivers for onboard hardware, all of which are handled by the T2/bridgeOS now, including the audio hardware. (The T2's basically taken the place of what used to be SMC, at least as far as I've been able to find out... (Again though, there's very little info about bridgeOS anywhere online, and virtually nothing about it on Apple's site.) There are some articles and video I've found though that explain how it now handles the audio hardware, SSD controllers, camera, microphone, etc... (My understanding of this is crude at best... I do know however that T2/bridgeOS handle the hardware mentioned.)
Also, here's a link answering your question about what was updated in 10.14.2
(Many of which were also updated in the High Sierra Security Update released on the same day.)
http://rixstep.com/1//20181209,01.shtml
AS FAR AS WHAT ELSE YOU CAN DO...
I highly encourage you to call customer relations and file a complaint. Complaints it seem are what this is going to require to get this seen as a 'problem' internally... (I've already filed two complaints. And I'll keep filing them until their sick of hearing my voice...)
And if you have shares in Apple you really need to let that speak for you as well... As I've said in both complaints how is my money safe investing in a company that thinks it's ethical to break the OS my machine shipped with?
OTHER STRATEGIES:
Since I've found that at least on my machine the problem showed up with the security updates, then went away when I clone back from a a backup made before installing them, I'm going to play their game by creating a new partition and install of 10.13 as it came from the factory. (Not a container disk, but an old school partition... This way that version of the OS is 'walled off' from files that might unknowingly getting 'referenced' if in a container disk.)
From there I'm going to stress test and document each incremental update either introducing the issue, or improving it.
1. I'll start with the original OS and stress that for a day, screen capture, and record video.
2. Install the supplemental updates I had installed for the first 3 months that worked for me, screen capture, and record video.
3. Install the first security update, screen capture, and record video.
4. Install the second security update, screen capture, and record video.
Assuming the issue comes back they'll give me the same line about requiring me to update to Mojave.
Then I'll update the new partition to Mojave to stress test if Mojave actually does improve the issue or not... (I won't be kind in my stress tests... I know the behavior so well that if Mojave doesn't fully fix the issue I should be able to reproduce the issue within a day or two..)
If Mojave fails then I'll file another complaint citing that Engineering's requirement didn't address the issue...
If the tone doesn't change after that then It's time to send a fax and write a letter to the CEO's office, then file a complaint with the Federal Trade Commission and BBB then send a follow up letter and fax to the CEO's office. If I'm still back at square one then Apple can kiss my shares goodbye and it's time to embrace the reality that Windows may be the only way forward...
PM me if you want info about filing a complaint or want the fax number and mailing address for Tim Cook's Office...
Last edited:
Not yet, my computer is my main device, I ran into some problems with previous Betas, so I'm off that trail at the moment, hopefully a release is imminent
I wish I had an answer for this... That said, there were a lot of audio extensions and frameworks updated in the Security Updates that caused issues for me. Below are a few screenshots of what was updated with audio related files marked in red.
Also note the modified timestamp, (just so you can confirm these were modified during the updates....)
As far as files that show dates in late November just be aware these are the build dates shown in timestamps... The actual install date for me was Dec 9th, and I've confirmed this by using spotlight to show only modified files from that date...
As you can see System Information makes it seems like less files were modified, but when you actually look in hidden folders you find there are a ton of files updated that either correspond to the extensions and frameworks or don't disply there because they're hidden by default. Many of which are system audio files... (This is also only a tiny portion of files I found modified that date... There are TONS...
You can also see bridgeOS was updated.
And a firmware update was also deployed...
Some of the files that might not seem related at first glance, as far as I've been able to get info about, handle hardware drivers... E.g. IOKit for example deals with drivers for onboard hardware, all of which are handled by the T2/bridgeOS now, including the audio hardware. (The T2's basically taken the place of what used to be SMC, at least as far as I've been able to find out... (Again though, there's very little info about bridgeOS anywhere online, and virtually nothing about it on Apple's site.) There are some articles and video I've found though that explain how it now handles the audio hardware, SSD controllers, camera, microphone, etc... (My understanding of this is crude at best... I do know however that T2/bridgeOS handle the hardware mentioned.)
Also, here's a link answering your question about what was updated in 10.14.2
(Many of which were also updated in the High Sierra Security Update released on the same day.)
http://rixstep.com/1//20181209,01.shtml
AS FAR AS WHAT ELSE YOU CAN DO...
I highly encourage you to call customer relations and file a complaint. Complaints it seem are what this is going to require to get this seen as a 'problem' internally... (I've already filed two complaints. And I'll keep filing them until their sick of hearing my voice...)
And if you have shares in Apple you really need to let that speak for you as well... As I've said in both complaints how is my money safe investing in a company that thinks it's ethical to break the OS my machine shipped with?
OTHER STRATEGIES:
Since I've found that at least on my machine the problem showed up with the security updates, then went away when I clone back from a a backup made before installing them, I'm going to play their game by creating a new partition and install of 10.13 as it came from the factory. (Not a container disk, but an old school partition... This way that version of the OS is 'walled off' from files that might unknowingly getting 'referenced' if in a container disk.)
From there I'm going to stress test and document each incremental update either introducing the issue, or improving it.
1. I'll start with the original OS and stress that for a day, screen capture, and record video.
2. Install the supplemental updates I had installed for the first 3 months that worked for me, screen capture, and record video.
3. Install the first security update, screen capture, and record video.
4. Install the second security update, screen capture, and record video.
Assuming the issue comes back they'll give me the same line about requiring me to update to Mojave.
Then I'll update the new partition to Mojave to stress test if Mojave actually does improve the issue or not... (I won't be kind in my stress tests... I know the behavior so well that if Mojave doesn't fully fix the issue I should be able to reproduce the issue within a day or two..)
If Mojave fails then I'll file another complaint citing that Engineering's requirement didn't address the issue...
If the tone doesn't change after that then It's time to send a fax and write a letter to the CEO's office, then file a complaint with the Federal Trade Commission and BBB then send a follow up letter and fax to the CEO's office. If I'm still back at square one then Apple can kiss my shares goodbye and it's time to embrace the reality that Windows may be the only way forward...
PM me if you want info about filing a complaint or want the fax number and mailing address for Tim Cook's Office...
Wow...thanks for the info. I will try. Thanks for taking the time. I would like to write a compliant to Apple, but what should I say so they don't just ignore it?
You bet!
To file a complaint:
- Call the AppleCare support number.
- When the automated voice asks you why your calling, instead of saying Applecare say "complaint". You should get "Sorry" as a response then the system will transfer you to an advisor.
- You'll most likely be transferred to a Sr. Care advisor instead of Customer Relations.
- Once on the line give them your cased number and ask for Customer Relations. If they try to assist you just continue asking for Customer Relations until they put you through, explaining you've already been through support and you want to file a complaint with Customer Relations.
You might have to go through another round of phone calls from people previously assigned to your case. Grit and bear it, the real end game here is to get enough complaints logged about the issue so Apple realizes it's a liability and/or PR issue, and development needs to address it sooner than later...
They'll probably ask for a summary... Keep it concise and remember this is the relations department. They have their own end game which is for you to walk away feeling like you haven't given up on Apple... You basically need to circumvent all of the corporate tactics they're trained to use... Focus on things like how the issue makes you question the Apple brand, QA at Apple's been declining, Apple prides itself on its support but support failed you, Apple claims it cares about its customers but you don't feel like you've been taken care of etc...Basically keep a cool head and use the force against them
Some examples of things you might mention...
- You paid for support yet support hasn't addressed the issue.
- The issue's been reported since August, how can Apple justify AppleCare if AppleCare won't address the issue?
- Apple hasn't honored the terms and conditions of AppleCare's software support. (Good idea to read them beforehand since they vary from country to country... E.G. "Software support: Not Covered: Apple software other than the Mac OS". iTunes and Quicktime ARE part of macOS and the sound issue affects them so they're covered by US terms...) https://www.apple.com/legal/sales-support/applecare/appgeos.html
- Why would you purchase AppleCare again when it seems like Apple's attitude is that it's ok to leave an issue this disruptive unacknowledged by support?
- The issue appears to be related to the T2 chip or bridgeOS. (Due to the iMac Pro experiencing the same issue).
- Considering the Mini and Air now have T2 chips the issue may eventually show up in all Mac products until it's resolved.
- How can Apple justify its high price tag if all of its flagship devices might potentially develop the same issue?
- Since the issue might be related to bridgeOS the AppleCare term about OS compatibility shouldn't apply since bridgeOS is not part of macOS, it's hardware specific software.
- Apple's Quality Assurance has been getting progressively unreliable.
- iTunes customers and Apple Music users can't listen to music.
- The machine can't be used to run Apple's own software, (Logic and Final Cut)
- The machine can't be used to run popular software like Adobe Premiere, Ableton Live etc.
- Support doesn't have access to information for troubleshooting issues related to T2 machines and bridgeOS.
- Support either doesn't acknowledge the issue, or has very little awareness about it despite it being reported since August.
- If you have shares in Apple you should explain why this concerns you as a shareholder.
- Even if you don't have shares you can mention that you've noticed Apple's stock value is falling, and you ask yourself how recent product failures are related.
- Leaving 10.13 broken damages your perception about Apple's attitude toward its users. (If you're still on 10.13)
[doublepost=1547531711][/doublepost]Also, check this... Looks like the Mac Mini's starting to reveal the same issue.
Do you have any issues with Audio on the Mac Mini?
Pretty solid evidence it's a bridgeOS problem AFAIC...
I am posting this simply as a victim to the audio issues 2018 MacBook Pro models may be facing. Originally in October 2018, I purchased a 2018 MacBook Pro 13" (base model) and eventually decided to load up FL Studio 20, which is new for the Mac since it was only Windows exclusive before. I was working on a music project and had a USB 2.0 audio interface plugged in prior. I was tired and decided to call it a night and I closed up my laptop, also unplugged the audio interface. However I decided that I wanted to watch some YouTube videos in bed and opened the machine back up, only to be greeted with an extremely loud buzzing noise. You guys, it was loud as hell. It almost sounded like an alarm that you would hear during a fire drill. Since I was at the lock screen, I didn't know what the cause of the sound was but I unlocked the computer, and force closed the application. After that, I could only hear treble from the left speaker. If I covered up the left speaker grille, it sounded like a muddy muffled mess. And another funny thing is that I could only turn up the volume halfway, or the left speaker's treble will vanish and both will only produce bass frequencies. I've rebooted the computer, disabled software, but I didn't do an OS reinstall simply because I didn't want to lose all of my documents. I just came to the conclusion that either the speakers, or the audio chip was fried. Fortunately I went back to the Apple Store and exchanged the device for a new one. I was running macOS Mojave 10.14.1 at the time it occurred. Thoughts?
Sorry to hear man, that's rough. Different behavior than I've experienced but seems like the distortion isn't the same for everyone. (Wonder if it varies with different CPUs... No idea, just thinking out loud...)
Have you experienced any sound issues on the new machine?
You could stress test it by to see if the issue shows up. if you do keep the volume really low, (like almost silent.)
One stress test I've done is screen recording with Quicktime using the mic to record audio. I just leave it screen recording until the issue shows up... (Plus it gives you documentation to send to support.)
Have you experienced any sound issues on the new machine?
You could stress test it by to see if the issue shows up. if you do keep the volume really low, (like almost silent.)
One stress test I've done is screen recording with Quicktime using the mic to record audio. I just leave it screen recording until the issue shows up... (Plus it gives you documentation to send to support.)