- #Blue yeti logitech g hub mac os
- #Blue yeti logitech g hub drivers
- #Blue yeti logitech g hub update
- #Blue yeti logitech g hub driver
- #Blue yeti logitech g hub pro
After switching back and forth a couple of times, the Yeti disappears from the available input sources. In my case the bug is easy to reproduce by simply switching input sources in MacOS sound preferences. Obviously the new mic suffers from the same issue. That it could be anything different than a faulty mic never came up in the very long thread I had with them. The people at Blue sent me a new microphone (old one still under warranty). It was a BIG mistake to purchase this mic for MacOS! Although even with the previous MacOS, the Yeti was a bit more prone to disconnecting itself than other mics in my experience. Something about Monterey simply destroyed the Yeti X on the Mac. I am not sure if that was helpful, but Zoom is my main web meeting program and figured maybe they could help somehow.
#Blue yeti logitech g hub drivers
Now, this does not resolve the issue with the Yeti X but only saves me from restarting my whole computer when the audio drivers crash.
#Blue yeti logitech g hub mac os
In the Mac OS terminal, and it will reset your audio drivers and re-enable any of the dropped devices.
#Blue yeti logitech g hub pro
It also causes my Logitech G Pro Wireless headset to disappear from the system input/output lists, which makes sense as the same core drivers control both.įor people that encounter this glitch and don't wish to restart their computer, you can try using the command I noticed that when this glitch happens, the core audio drivers that govern the Yeti X (LogiGamingAudio.driver) crash and disappear from my activities monitor. However, I can easily replicate the issue in the Mac OS System settings or G Hub by quickly changing audio inputs between another audio device and the Yeti X. Sometimes, it will work fine for a little bit, then stop working or not be working at all. The issue described here occurs not just with Zoom but with all meeting programs that try to use the Yeti X. After almost two weeks of back-and-forth emails, the problem is still happening. Unfortunately, Blue stopped responding to my support ticket, and I am still going through the process with Logitech. I have reached out to Blue and Logitech about this exact issue.
#Blue yeti logitech g hub update
I will maintain Logitech G-Hub installed hoping that sooner or later they will release an update that corrects the problem and be able to use its advanced equalization and profile functions again.
#Blue yeti logitech g hub driver
I also used this command in Terminal to remove all the drivers I deleted and I will no longer use (if I'm not wrong, I think this removes a folder that works as cache of drivers):Īfter reboot the system, the microphone should now use the built-in macOS driver with no problem.įor now, my Blue Yeti X microphone seems to work without problems with macOS Monterey 12.2.1. To remove the Logitech G-Hub driver you just need to remove the file "logi_audio_override.kext" from the folder library/extensions of your system hard drive (I just moved it to a folder in my Desktop to keep a backup of the file). Of course, doing these, all the "Blue Voice" effects and other settings that Logitech's G-Hub app allowed will no longer work, but the microphone should still be usable in its basic functions including volume control or mode change with its physical buttons. I removed that driver and now my Blue Yeti X microphone is using the integrated driver of macOS and it seems to work without issues. It seems related to the Logitech G-Hub driver for Blue Yeti microphones. I will maintain Logitech G-Hub installed hoping that sooner or later they will release an update that corrects the problem and be able to use its advanced equalization and profile functions again.I experienced the same problem.
0 kommentar(er)
