Yeti X unusable on macOS Big Sur on Apple Silicon / M1已回答
When using Voice Memos, it comes out as a chipmunk every few seconds, here is what it sounds like:
When using Logitech G Hub preview, it comes out as a bass humming sound, with repeats, shortening, and skipping of speech in between the humming. ~3 seconds of recording also turns into about ~18 seconds of playback.
Hi there, We will pass this along to our team. We always want to ensure we are providing our customers with the best products and experience. Let us know if there is anything else in the future we can do to assist.评论操作
For extra debugging information, here was my process:
1. Install Logitech G Hub
2. Plug in Blue Yeti X via USB-A into a dock.
3. Logitech G Hub complains that a kernel extension is required to enable the Yeti X.
4. I do the recovery mode, enable the kernel extensions, restart, and the security preference panes about allowing/enabling the kernel extension.
5. I can now open the Yeti X in Logitech G Hub
6. I record a sound bite while I customise the settings. Approximately 4 seconds of recording, turns into a approximately 20 second audio clip of massive distortions, like a broken record.
7. I try the Voice Memos app, and can produce the recording in the OP.
8. I try and cmd+space a few times, and it triggers siri instead of spotlight. I try type in some text areas, and the text input slows to a crawl and skips characters. The computer starts slowing to a crawl. Logitech G Hub needs to be completely closed, and the microphone needs to be unplugged to restore keyboard functionality.
9. I try again with the macos accessibility security preference for g hub enabled and disabled.
10. I try several variations of cables, and usb hubs, all same result.
11. I consider this moot, unplug the microphone, restart into recovery mode, rm -Rf the kernel extension, and continue with other things.
Tomorrow I'll try https://www.bluemic.com/en-us/products/sherpa/ instead of G Hub for the Yeti X, which I didn't know was a thing before just now.
Roasted Toasts says same issue affecting Blue Sherpa:
Franklin Reid has reported that the Yeti X is broken for him too on the M1 Mac Mini, but yet it works for him on the M1 MacBook Pro:
Roasted Toasts has the same issue as Franklin and myself are having on our M1 Mac Mini, on their M1 MacBook Pro:
So the audio issues are affecting:
- 2/2 of the M1 Mac Mini (👎 Franklin Reid, 👎 Benjamin Lupton)
- 1/2 of the M1 MacBook Pro (👍 Franklin Reid, 👎 Roasted Toasts)
For getting it to work, here are temporary impartial workarounds so far.
Roasted Toasts reports that with Blue Sherpa, restarts do work, but you will lose your equalisers and customisations, and if you open the software or replug the microphone, then the audio corruption will occur:
I recently upgraded to a MacBook Pro with the M1 chip. I have a Yeti Nano microphone and am having similar issues to those described above. Sometimes I am able to connect the microphone and use it without issue. More often, the microphone loops 1 second of audio on repeat (e.g., "hello hello hello hello hello hello..."). Also often, the microphone does not pick up any sound despite appearing connected in Mac OS. Having the Yeti Nano plugged in also appears to mess with the MacBook's internal microphone and the microphone on my Logitech 920s such that no microphone picks up sound.
Restarts do seem to work, sometimes. I called Apple support today and they didn't have any good ideas about how to fix this. We tried rebooting in Safe Mode and while that seemed to help a bit, the Yeti Nano still had issues when I booted normally.
Blue and Logitech, please fix this ASAP!
I honestly can't believe Logitech are ignoring this issue.
I am so close to returning my mic under the warranty and getting an Elgato mic. The only reason I picked the yeti X was for blue voice, but as that's useless now, I don't see any point in keeping a broken mic.
Such a disappointment as I've always thought well of Logitech up until now.
> Having the Yeti Nano plugged in also appears to mess with the MacBook's internal microphone and the microphone on my Logitech 920s such that no microphone picks up sound.
Not sure if this is related, but even on my 2017 Macbook Pro, the Blue Yeti X remains silent on certain applications - specifically Discord - despite other microphones working fine.
It just seems the Blue Yeti drivers have taken a nose dive and aren't particularly compatible with the Mac ecosystem anymore, especially the Apple Silicon macs, of which they are completely useless.
I've tried to raise this via Blue instead of Logitech, however their support page is completely broken for me:
I've tried several times via Twitter to Blue and Logitech, as well as via Logitech, and haven't gotten any responses. It is also worth noting that Blue is owned by Logitech.
I've contacted Amazon and have proceeded with Nick's suggestion of a warranty return, I'll post back with how it goes.
I did compare the Yeti X to the Elgato Wave 3 when I got it, and ended up selecting the Yeti X as it filtered out background noise better and gave a more full voice. However, none of that matters if the Yeti X offers better sound but no longer works, which is the current situation.
I found a solution that worked for me. With a bit of effort it will work for anyone suffering the frustration of having bought a now useless microphone that is receiving zero support from Logitech.
1, contact the retailer you bought the yeti x from and explain that due to it being faulty, you would like to return it for a refund. (This step is optional and will depend on when you bought your yeti and the goodwill of the retailer you bought it from, alternatively you could sell it on eBay to someone with an older computer)
2, purchase the Elgato Wave Microphone (either the wave 1 or 3 will work fine, I went for the wave 3 as it was the same price as the useless yeti x I was returning, but you can save some money by going for the wave 1)
3, install the Wave Link app which DOES work on Apple Silicone computers
4, install OBS
5, set up EQ through OBS and route the sound through your system as needed using Wave Link. It’s not as simple as using the Blue Voice app, but has the benefit of not making you sound like a broken robot on LSD. (lots of videos on YouTube showing how to do this)
6, never trust Blue Microphones/Logitech again. (Obviously)
7 (optional) create a new account to post your solution after Logitech block your old account for posting previous negative comments pointing out their failings and how they are letting down their customers (the blocking of my account may have been coincidental or happened by mistake, but it’s very bad timing if that’s the case)
I have suffered the exact same issues everyone is describing here. It has gone on for a month now and I am finally giving up. I am returning mine this weekend and going with a different product that has better support for Apple M1 silicone. It's frustrating because I really like the mic itself.
Oh boy. A few weeks ago, after three decades trapped in the PC world, I switched to Mac via a new M1 MacBook Air so I could use Camtasia and a Blue Yeti to create screen-recording tutorials. After weeks of thinking the problem must be my ignorance about the M1 Air, Camtasia, and the Blue Yeti, at least now I know it's not.
Does this mean that Tim Cook runs an even worse horror show than Bill Gates did?
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 not compatible with the current generation of Macs.
Hi, I'm having the same issues. I have an M1 Mac and a Yeti X; I can't use the G Hub which is the reason why I bought the mic in the first place. I contacted Blue and waiting for a reply. I also went to the apple forums and many users having the same issues. I worry that maybe it could be a hardware issue and cant be resolved via a firmware update. My understanding is that Apple sent out test codes for the M1 almost a year ago and Logitech never implemented them into the latest microphones. I like the mic but considering if I should return it and go with another brand that works well with the M1 chip from Apple. This is also my first Blue mic and it's not a good first impression of this company. I can't find any public response by them about this widespread issue. Please share if you guys hear any news.
Same issue here. Mac Mini M1. The computer won't even pick up my Yeti X as an input source. Restarts don't work, but haven't even tried the software because of the thread here, on Reddit, on Twitter... everywhere. Going to wait it out and continue to troubleshoot for a few more days, but seriously considering returning my Yeti and going with an El Gato.
I was having this problem on my M1 MacBook Air. I followed George Jarrett's recommendation which, as I write this, is four posts above.
After I followed George's instructions, my Yeti X works with Camtasia, Zoom, and GarageBand. I do not have G Hub or Blue Sherpa to control the microphone; but I least I have the microphone working.
Thank you, George Jarrett!
I called Logitech. The woman with whom I spoke said they are working on the problem. She also said that, once G Hub and Blue Sherpa work, I would be better off using G Hub than Blue Sherpa. I did not understand why.
For those of you who, like me, are not as savvy as George, here's what the terminal dialogue that I used to follow his instructions and remove the offending resources looked like (The ls, that is LS, command lists what's in the directory so I could make sure I was in the right place.):
Last login: Mon Mar 29 14:53:09 on ttys000
jerry.redacted@Jerrys-MacBook-Air Resources % ls
blue.icns cryeti_0_20.bin sherpa-remove-all.sh
compatibility qml yetinano_4_5.bin
crsnowball_2_1.bin qt.conf yetix_11_3.bin
jerry.redacted@Jerrys-MacBook-Air Resources % chmod +x sherpa-remove-all.sh
jerry.redacted@Jerrys-MacBook-Air Resources %
[Restored Mar 29, 2021 at 3:07:27 PM]
Last login: Mon Mar 29 15:07:24 on console
Restored session: Mon Mar 29 15:06:34 EDT 2021
jerry.redacted@Jerrys-MacBook-Air Resources %
As I remember, to get the removal to take effect, I may have had to reboot a couple of times.
Same issue for me with Yeti X on MacBook Pro M1, latest software as of post.
Shame that Blue sold, Logitech are notoriously bad and are living up to their reputation.
And it’s unfortunately mindblowingly short sighted. As vast numbers of content creators are going to be updating to the M1 for faster video progressing, and that’s going to be a huge part of their early adopter community who’ll just go elsewhere and find new brands to love, who obviously will influence late adopters.
So well done Logitech, hopefully the future drop in sales will hurt you enough to start caring again.
I can confirm that Blue Voice features do not work for Yeti X Pro microphones, in either the Blue app or Logitech G Hub app on M1 Macs. The microphone also needs to be connected at boot to get basic functionality with the Blue app.
This is very disappointing considering Blue Voice is a key feature/selling point of this microphone.
Please Logitech, can you acknowledge and work on a software update to address this issue, thank you.
Having the same issue as partyondudes it's a shame all of this.
Also experiencing issues. MacMini, M1 chip, MacOS 11.2.3.
Blue Sherpa can detect my YetiX, but only when connected directly to the machine (no hubs).
Sherpa can live monitor the input levels and control mic functions, but when I choose Yeti as the output device for sound, I hear nothing from my headphones connected to the YetiX.
All functions well on Windows 10, even through USB hubs, so I have a good control to judge by. Really need this to work on my MacMini. Strongly emphasizing a need for this fix.
I'm not sure why no one from Blue or Logitech have said this here on this thread, but after making my comment above, I also submitted a support ticket directly. This is their response, which sounds hopeful:
"Thanks for reaching out. We are aware of the compatibility concerns with Sherpa and G HUB for macOS 11 Big Sur. This has been flagged as a priority and we are working on an update."
You, sir, have given me hope.
I've bought my Yeti X today and was wondering why it was not connecting to my
Mac air only to find out it's not compatible with Big Sur yet and was about to return it.
I love how to mic sounds and hopefully they will fix it soon. Or I'll follow the others with returning/reselling.
For the love of god, please fix it. Is it a resource issue or software limitation? Or does someone need to own the roll out of this bug / feature?
I’m happy to own this product. Point me towards your JD, I’ll apply, and land the gig just to get this fixed.
I want my crispy HD voice on my meetings to flex to my other FAANGers.
My problem is that I just updated from Big Sur 11.2.3 to 11.3, and now my Yeti is not working. I've an intel processor. I use the yeti to record online exercise classes, so I'm a bit stuffed now. It worked perfectly on 11.2.3. The workaround above - shutting down my Macbook Air, plugging in the yeti, then restarting the system has worked, but it's not ideal.
Does anyone from Logitech even read these pages? And how will we know when there's a fix?