Blue Yeti X Mic & Big Sur / M1 Macbooks - Error trying to synchronize Audio and MIDI

I am having the same issue. To get the mic to work without software, restart your M1 with the mic plugged in and don’t open the software. The mic will work but I purchased this for the software enhancements so this is a show stopper for me.

I bet this is Silicon problem. I have 2015 MBair and 2020 M1 MBP. After I've updated my two MB to Big sur, MBA 2015 has no issue with Yeti X and Blue Sherpa app, but my M1 MBP has problems with Yeti X and Blue Sherpa app. It has echoing in its sound. (If I record 5 secs to test, it turns out to 20 secs of recording of echoing..)

It’s definitely Logitech software incompatible with M1 processor. I booted without their software and like others, my Yeti X works as a basic microphone. The only problem is if you plug headphones into the mike to monitor sound you can’t control the volume.

I am also having this problem. The only way that I can get the micrphone ITSELF to work, is by restarting with the microphone plugged in. However, it seems there is absolutely no way to get the Logitech "G Hub" or Blue Sherpa software to work (which is literally why I bought the Yeti X to use the different settings). This issue is incredibly frustrating.

Yes, there are no reported issues with the intel macs, just M1. I made this video to talk people through a temp fix that enables you to use the Yeti X without the Blue Voice software, as well as a live demo of Krisp, a third party software that does work for the M1 Mac that allows you to eliminate background noise live while on a zoom call, streaming, etc. https://youtu.be/MrDJI1zEXnA

I am having a problem I believe is very similar to this discussion; however, I am on a mid 2020 Intel MacBook Pro with Big Sur. Yesterday I tried to use my Blue Yeti with Zoom and was unable to hear the other person I was connecting with, and unable to take the system off mute. I could go into the volume and move the bar to increase volume (and hear it increasing), only to see it immediately go back to mute. Unable to force a change, I restarted with the Yeti plugged in. I was then able to control the volume.

I have been using Yeti with Zoom since late December on this computer, with no problems. The latest Big Sur update to 11.2 was on 2/3, and this was my first Zoom since that update. I am assuming it has something to do with the update.

I will report this separately as an Intel Mac problem, to see if anyone else is having this issue on an Intel machine.

The reply I got from Blue (Logitech) support was similar. They asked me to do some tests and send them a recording, which I did. They are blaming Apple when it was actually their fault for not testing their software when Apple offered test M1 Macs almost a year before they were released. Blue (Logitech) did not do their job. Thats like saying it's Ford's fault when a part you make doesn't fit their new model year car. I guess Apple is supposed to make sure the Blue microphones and their software work with the new processor. Even if Apple has to fix something, it is impossible for Apple to test every USB device and all software. If Blue had discovered this problem 9 or 10 months ago they could have worked with Apple to fix it.

I don't have a Blue microphone or a M1 device, but I do have a very similar problem. I had been using a Soundcraft NotePad-5 with Garageband for months to record an audio track. I use a 2020 MacBook Air with an Intel processor. Right after upgrading to Big Sur (and updating Garageband itself to the latest version) I started getting this same error message. Part of the recording is simply missing, while the rest of it is sped up/distorted.

I thought I'd post about it, since at least in my case this seems to have more to do with Big Sur/Garageband than Apple Silicon. Hope that might help others. I haven't tested the solution about plugging the NotePad in before starting up/restarting, but I will be giving it a try tomorrow.

This happens with Logic pro software as well. Can't switch to Google Chrome while using Logic Pro. Apple just needs to accept that they are selling crap for big $$$. Just plain frustrated with how Apple not fixing this coomon issue for so long.

I am frustrated too, but you shouldn't blame Apple. Third party developers had a year to test their hardware and software on the M1 processor. It's the developers who dropped the ball. Even if it is an Apple issue, the developers should have been working with Apple to get it fixed. Logitech tried to say they didn't even know there was a problem. If they didn't know about it, it was because they didn't even test their software and hardware. I put all the blame on Logitech.

BTW, I do know that Logic Pro X is apple software, so if there is a problem there, there is no one else to blame. You mentioned Chrome and that is another problem. The security team at the Fortune 500 company I work with has asked us all to remove Chrome from our systems. There are so many security issues with it and Google tracks everything, we are not allowed to login to the corporate system using Chrome.

Here is the bug report on the Logitech/Blue forums. Please post there so it gets their attention.

https://support.logi.com/hc/en-001/community/posts/1500000075682-Yeti-X-unusable-on-macOS-Big-Sur-on-Apple-Silicon-M1

I had this problem, too. Macbook Pro M1, Big Sur 11.2.3, brand-new Yeti Nano.

What worked was to remove all of the Blue software and reboot. I believe the problem is the Extension installed in the /Library/Extensions/ folder.

If you go to the Applications folder, right-click on the Blue application, and choose "Show Package Contents," you should see a folder labeled "Contents." In that folder is another folder, "Resources."

In the Resources folder is a shell script to uninstall the software. I went to the Terminal and ran that shell script with sudo.

Now the mic works for basic sound input. Still sounds better than the built-in one in my laptop. But I want that Blue software to work too...

Clearly Blue/Logitech needs to update their driver to be M1-compatible. Blue's fault, not Apple's, for not informing customers that their product is incompatible with the current generation of Macs.

For those who are blaming the M1, I must disagree. This is a Big Sur problem. I have a mid-2020 MacBook Pro that is Intel based. It is acting exactly the same from problem to solution. This problem is not M1 - it is software.

Model Name: MacBook Pro

  Model Identifier: MacBookPro16,2

  Processor Name: Quad-Core Intel Core i5

I'm not sure what release I was on when I switched to my new M1 Mac mini. I have 11.2.3 installed on my MacBook Pro now, but I haven't tested the Yeti X on it for a while. The Yeti works as a better than average microphone on the M1 without the software enhancements.