If I connect my AirPods, the system automatically changes the input/mic to the AirPods, and if I go into system settings and dedicate the Yeti for input, the OS (or AirPods?) switches it back to the AirPods and then the mic disappears from the list of inputs, which seems to only be fixed with a fresh reboot, as disconnecting and reconnecting to the USB to a powered hub or a dedicated connection does not resolve the issue. If I use the Yeti on its own after booting up, it appears to work fine. After getting the mic driver/extension allowed with the system, it seems I can’t split the audio duties between the AirPods and the Yeti. On my older Intel-based Mac running Catalina, I was able to use my AirPods Pro for audio output and my Blue Yeti for input without an issue. Getting it recognized required altering some security settings. Running into this issue in Monterey on a new M1 Mac Mini, regrettably, and there appear to be some lingering issues beyond simply getting the mic recognized. READ NEXT: Logitech MX Keys Mini for Mac review: better than Apple’s Magic Keyboard? However, this only appears to work if you’re not using the Logitech software. Other users have found alternative solutions, including making sure the microphone is plugged in and powered on before rebooting your Mac – when it comes back on, the microphone should be working. I’ve not had a chance to try this but it appears this is the solution for now – using Logitech’s own software and drivers, rather than relying on the default Apple versions. The latency/delay you were experiencing should be fixed with this update. Please update G HUB with the release from yesterday (20). Is there a solution?Ī few weeks later I received this update from Blue… Zoom was particularly bad with a second of lag between video and audio. However, I found a terrible delay introduced into the microphone. This appears to use its own driver, which has worked successfully for some users. Some other users suggested using Logitech’s G HUB application, which works with various Logitech hardware, including Blue microphones. Unfortunately we do not have an ETA at this time.īearing in mind how long the M1 processor has been available, it doesn’t seem great that there’s still no ETA on this, especially as Logitech have been aware of this problem for at least 10 months. Please note that we are currently working on a fix for issues with the Apple Silicon M1 processor. When I raised a support ticket, they quickly admitted there was an issue with M1 Macs. Why doesn’t the Blue Yeti Microphone work on M1 Macs?īlue was bought by Logitech last year, so support is via them and, well, they remained pretty quiet on the subject – in the forums anyway. But, whether distorted or just not there, something was amiss – especially as other microphones appear to work just fine. My particular experience seemed pretty unusual, though, as most people were finding that the sound was simply garbled. A quick Google search and it turned out I wasn’t the only person having an issue, and it seemed to be down to that new M1 chip. Trying it on a Windows desktop, all worked normally. I tried everything, including a replacement cable, but it remained the same. I had my M1 MacBook Pro a few weeks before I noticed an issue – the microphone was shown as plugged in and selected as the input device but no sounds was being shown as being received. But all may not be the same if you’re trying to use it on a M1 powered Mac. On a Mac it works without any drivers – just plug it in. It would be nice if Logitech did, and cleared away all the miasma surrounding the various Windows settings, both modern and legacy versions.I’ve had a Blue Yeti microphone for about 7 years and it’s a brilliant piece of equipment. Enabling advanced functionality under System, Sound did not restore GHub connectivity, but your Sound applet suggestion did! I'm not sure Logitech officially supports the Blue Yeti X under Windows 11. The Win11 text says advanced functionality must be enabled in Windows 11 to let the Yeti driver access advanced software settings. I saw in Windows 11 in the modern Settings under System, then Sound, that there is an ADVANCED setting. Strangely enough, just as you suggested, enabling PLAYBACK fixed connectivity in GHub. In the Sound applet, the Yeti was enabled for RECORDING but not for PLAYBACK (which I never do through any Yeti functionality there). I noticed that the Blue Yeti was disabled in GHub after getting the 7/27/22 GHub update and a Windows 11 Cumulative Update on the same day, then launching the new version of GHub. It fixed my Blue Yeti X connectivity problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |