Apple Intelligence is now available on iPhone, iPad, and Mac!

Yeti Blue Mic Not Recognized on M1 Mac

My Yeti Blue mic only works if I shut down and restart my Mac with the mic plugged in. After a while, the mic disappears as a sound input option in System Settings > Sound > Input. Sometimes the mic works for 2 or three days, but eventually, it stops appearing as an Input option.


The mic is recognized by System Information > USB, but not in System Settings (see attached image):


The problem did not begin until after upgrading to Sonoma and or after installing G-Hub. I have since removed G-Hub.


Here are the troubleshooting steps I've tried:

  1. Create a new user account
  2. Repair disk permissions
  3. Remove G-Hub & Blue Voice


These steps temporarily resolve the problem:


Run these terminal commands:

  • sudo rm ~/Library/Preferences/Audio*
  • sudo kill -9 `ps ax|grep 'coreaudio[a-z]' | awk '{print $1}'`


Remove these files:

MacHD/Library/Audio/Plug-Ins/HAL/LogiGamingAudio.driver

(remove anything related to G-Hub, Sherpa, BlueVoice or Zoom)

MacHD/Library/Preferences/Audio/com.apple.audio.DeviceSettings.plist

MacHD/Library/Preferences/Audio/com.apple.audio.SystemSettings.plist


Then I have to restart and the mic appears for a while, but randomly disappears again and I have to repeat the process.


I am seeing hundreds of posts online about this same problem. I made a video on YouTube called "How to Fix Yeti Blue Not Recognized on Mac in 3 Steps" which goes into greater detail, but just today, after 3 days of successful recording, the mic disappeared again.


ABOUT THIS MAC

MacBook Pro, 16-Inch, 2021

Chip Apple M1 Pro

Memory 16 GB

Startup disk Macintosh HD

macOS Sonoma 14.3.1


OTHER CONSIDERATIONS

Recently using Capcut I could see and use the Yeti mic, but right after that, it disappeared. Happened with Zoom too. Any idea what is causing this or how to fix?


[Edited by Moderator]


MacBook Pro (M1, 2020)

Posted on Mar 11, 2024 10:00 AM

Reply
Question marked as Top-ranking reply

Posted on Mar 20, 2024 4:57 AM

I made a video with a 3-step solution, see if this works for you:


How to Fix Yeti Blue Not Recognized on Mac in 3 Steps

https://youtu.be/jqsCBGoeCG4

35 replies

May 3, 2024 6:22 PM in response to 0X4DBOY

Thanks to all for the info and to the Author for raising this issue. I too will add some data points and keep this thread active.


tl;dr

I haven't read every single post in depth, but I found what appears to be a workaround on the same exact Macbook Pro model.


Try some combination of the following 👏💻

  • Try to plug the mic into a different USB-C port on the laptop (the left side ports work for me, but the right one did not)
  • If on a laptop, plug it into a power source. Ensure that the battery level is above like 50% (arbitrary % value, just make sure it's at least above critical battery levels).
  • If you're using a USB-C hub converter (i.e. multiple USB-A ports, ethernet, etc), try with a USB-C converter that only takes a single connection.
  • Try to plug the mic into the USB-C adapter using a different USB cable


Disclaimer 🙈

I'm not sure if what I've observed is fully consistent with the Author's observations. The fact that they observe the same behavior in response to the presence of a file does seem like a software problem. So there ultimately could be multiple issues at play. My workaround is also not what I'd call "exhaustively tested", tho I'm fairly confident in the rationale, and it works even after a reboot. I go into detail down below for those that are curious.


My observations 💻 👀

I also see Yeti Blue Mic weirdness on my M1 Macbook Pro on Sonoma--an outdated version though: 14.2.1.

My Macbook Pro is running on battery.

I'm using an IXCC USB-C adapter. I trust it because I've used it with this laptop for other high-powered devices.


At first, the Mic showed up in Mac's Sound Input and even recorded in Audacity, but it kept disconnecting/reconnecting when I would move the Mic USB wire around.

Then the Mic started to show up in Sonoma's Audio Input Device list and detect audio, but it wasn't visible in Audacity.


At another point in time with a different USB cable, Sonoma straight up crashed. This happened with the cable in the right side USB-C port, which is next to the HDMI port on this Macbook Pro.


I tried on my Windows 10 desktop, and I discovered that the Yeti mic's USB cable was faulty.

With yet another USB cable, the mic works perfectly fine on Windows (direct USB connection, no USB-C adapter).

Using this same cable on Mac, it showed up in the Audio Input Device list once again, but not in Audacity.


I then switched the USB-C adapter to a different USB port on the Macbook. THIS WORKED. As in, I could record in Audacity and hear the recording in glorious clarity. I don't know if it will last, but it works for now. Nothing changed except that I switched from the right side USB-C adapter to the left side USB-C adapter closest to me.


My guess as to why this works?

USB-C port power delivery. This is simply an intuitive guess based on my experience in local multiplayer video game development* and DJ mixing with multiple USB MIDI controllers connected to this same laptop.


The Yeti Blue Mic I have is quite hefty, has lots of lights, so it would seem to need a good amount of power.


Anyway, after it started working, it hit me. I noticed that the M1 Macbook pro USB-C ports on the left side are right next to the charging port. Without looking at the Macbook's schematics, I'd guess that the battery has got to be close to the charging port, right? Given this, I'd say that the USB-C ports on the left (charging) side get more power than the one on the right.


I think the brief connection I saw was when the right side USB-C port was delivering enough power to function. The disconnection would happen when the USB-C power delivery fell below a functional connection threshold for the Mic.


--

*In that setup, we had up to 4 XBox 360 gamepads connected to a single USB hub. We would run the game on a laptop. After a while (maybe around an hour), the controllers started to disconnect. The gamepad power lights turned off. At the time, I was kind of freaking out and didn't know what was wrong.

After some more experience, I feel like it was something to do with power. That experience was something like: I didn't notice the issue after I plugged the laptop into a power source.

Apr 14, 2024 11:34 AM in response to 0X4DBOY

Around the same time all of these Yeti disconnect issues arose, I started to receive random 2-Factor Authentication (2FA) notifications from a random number.


This week, I noticed that an orange mic icon appears in my Finder admin bar when I get the 2FA message. I think the 2FA verification link is coming from Stripe, but the fact that the mic icon appears at the same time leads me to believe it could have something to do with a subscription for CapCut or Screenflow.


I am going to test if these messages are arriving when the mic cuts out, but wonder if anyone else has noticed this on your side?

Mar 17, 2024 1:50 PM in response to 0X4DBOY

Logitech is the vendor of record for Yeti products and either they can help you or cannot. Unless some magician contributor who owns a current Blue Yeti in this community has a permanent fix — your topic will remain unsolved — unless you replace that Yeti with another microphone product that has actual vendor support on Sonoma or later.


Randomly removing Apple files has not shown to be the answer either, and Apple has no responsibility for Logitech products.

May 20, 2024 5:17 AM in response to 0X4DBOY

A commentator below the YouTube video title "How to Fix Yeti Blue Not Recognized on Mac in 3 Steps" provided some insight to a potential solution:


I was able to get it to work on my M3 Macbook Pro (2023) model today after following all the directions ...except after reinstalling GHub it still didn't work.

I noticed in the macOS privacy settings that GHub was also requesting access to kernel extensions. After rebooting and holding down the power button, went into Recovery Mode, Utilities in the menu bar, Security settings, then enable kernel extensions for identified applications, rebooted, and then my Yeti X appeared both in GHub and macOS sound settings.


There is something happening at kernel level with security settings. Anyone know how to get Console > Log to track this or see what is happening?

Jul 3, 2024 11:54 AM in response to 0X4DBOY

I was having exactly this problem with my approx 10 year old Blue Yeti. MacBook Pro 14" 2021, Apple M1 Pro, macOS Sonoma 14.5. I followed the instructions in and they worked.


However - Zoom seems to keep recreating /Library/Audio/Plug-Ins/HAL/ZoomAudioDevice.driver, so I have to keep deleting it and restarting to get my microphone back.


Some posts have suggested that the problem might be that older Blue Yetis are somehow incompatible, so I treated myself to a new Blue Yeti X. Today, I plugged it in, and it showed up as a USB device in System Report, but not in Sound settings. I went through the instructions again, restarted, and my Blue Yeti X showed up.


So - brand new mic, new cable, and I'm still having this issue. Everything worked fine until a couple of months ago, so it seems to be something in macOS that's changed.


[Edited by Moderator]

Sep 30, 2024 1:30 PM in response to 0X4DBOY

I am having the same issue with my Yeti Nano! I have deleted blue voice and all related software but the issue remains. I have a MacBook Pro 14in, M3 Pro. Only thing that works for me is deleting `/Library/Preferences/Audio/com.apple.audio.SystemSettings.plist` and `/Library/Preferences/Audio/com.apple.audio.DeviceSettings.plist`. Trying to get a support ticket with Logitech as well.

Oct 6, 2024 4:48 AM in response to 0X4DBOY

Update October 05, 2024

Nearly 7 months since I tried my Yeti, and plugged it in today to my M1 MacBook Pro and it works as expected. I have a Yeti and Fefine plugged in at same time. The Yeti and Fefine appear in System Settings > Sound > Input.


Back in March, it was working just like this, and then I did some recording with CapCut, and mid-way through recording, the Yeti disappeared. That did not happen today.


I also let my Mac go to sleep and wake, which previously disconnected the mic and today it continued to work.


I do see the Mic Mode icon lit up as orange in my Mac app bar (top of the screen), meaning the mic is set to Standard Mode.

Oct 8, 2024 1:11 PM in response to SageFedora

I will try this. My Yeti has been working fine for 3 days in a row, even after unplugging and replugging, sleep restarts, etc. I have been running the Console app waiting for it to drop, but luckily it is working fine.


I am still running macOS 14.3.1 on my M1 MacBook Pro.


I will try the Terminal command as soon as I see the Yeti disappear. Thank you for sharing!

Yeti Blue Mic Not Recognized on M1 Mac

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.