The Logitech Blue Yeti Nano USB microphone gets a bit of a bad rap on the ole' "Interwebs", with comments like "...just not worth the cost.", and "It was terrible for my use case..." just in the first few posts of one Reddit thread -- and it didn't get much better after that.
Also, Logitech's "Blue VO!CE" software isn't provided for Linux. As we will see, this isn't an issue either, as the same Reddit thread calls Blue VO!CE "...crappy bloated Logitech software."
It turns out that the Blue Yeti Nano USB microphone and other USB microphones -- even ones that are not top of the line -- can be used for recording or streaming on Linux, and with a little skill, produce very professional sounding results.
This is intended as a Quick Start Guide to Upping your Game of Recording or Streaming from Linux.
Hardware:
-- I purchased a Blue Yeti Nano at an Estate Sale for a very reasonable price (which in itself mitigates some of the complaints), but most of what is in this guide pertains to any pro or semi-pro microphone. It assumes an input other than a simple mic connected to the PC's 3.5mm mic input, although even if that's your setup, this guide will help.
-- Mounting the mic is important. Sitting it on the same desk with a PC full of fans is far from professional. The stand included with the Blue Yeti Nano is wholly inadequate for providing any significant noise/vibration reduction. A professional boom and vibration isolator will obviously help, but even placing the basic stand on a second mouse pad or similar soft pad is a step in the right direction.
-- Set the microphone to Cardioid mode. The Blue Yeti Nano is not going to perform adequately (no single mic really is) to pick up a room full of voices. If you are hosting a symposium, get a mixer such as the Mackie DLZ creator described here, and mic each person. Don't forget that unlike a basic Cardioid Dynamic Mic, the Cardioid shape is to the side of the Blue Yeti Nano with the Mute/Volume control, not the top or back. IMHO, Omni mode for this microphone is generally unusable.
-- Lastly, buy a $100M recording studio -- Just kidding -- Room sound/sound absorption material is another important aspect of good quality sound, but is considered to be beyond the scope of this article.
Software:
For any sound processing on Linux, a few basic apps are needed. (Note: This article is based on Pulse Audio -- Linux Distributions not based on Pulse Audio, or that do not have the Pulse Audio extensions available, are not covered.)
-- Pulse Audio Volume Control (pavucontrol) gives us far more control than the desktop's basic volume slider.
When connected, the Blue Yeti Nano USB Microphone pops up in the Configuration Tab without adding "drivers", etc. Select Digital Stereo (IEC958) Input. Note that a professional setup will probably not use the Blue Yeti's headphone jack, so we select it as an input device only.
Install Pulse Audio Volume Control from your distribution with:
Code: Select all
sudo apt install pavucontrolCode: Select all
sudo apt install pulseeffects1. Audio Feedback can occur, causing a loud squeal or echo. This could potentially damage both ears and equipment.
2. Having a feedback path during a live broadcast or while recording is unprofessional. This is why the studio and sound processing equipment is generally separated into 2 sound proof rooms. (Did you buy that $100M studio?)
3. It is nearly impossible to equalize your own voice, as we will be hearing ourselves normally, and via the equipment albeit with a short delay. Your voice will not sound like it does to others. Especially if you do not have a sound engineer helper, it is best to leave loopback off, and do trial-and-error recordings.
4. If you do choose live monitoring, it should only be done with headphones, and mute all sound before removing the headphones, as they can squeal as you remove them.
5. The above considerations are why live monitor (loopback) is not included as a GUI option in either Pulse Audio Volume Control or Pulse Effects.
Given the above, if you still must use live monitoring, set your Output Device volumes down, and issue the following command from a Terminal:
Code: Select all
pactl load-module module-loopbackNote that Pulse Effects creates new virtual sound devices to implement the desired sound processing. Each of these Virtual Devices live in the proper location between our Recording or Streaming apps and the Sound Hardware to implement sound processing. These virtual audio devices will persist after Pulse Effects is terminated. To return Pulse Audio to a normal state after we are done using Pulse Effects, we need to execute the following from the command line:
If you used live loopback, stop it with:
Code: Select all
pactl unload-module module-loopbackCode: Select all
killall pulseeffectsExecute:
Code: Select all
pactl list modulesPulseEffects_apps
- and -
PulseEffects_mic
Note the Associate Module Numbers -- e.g. Module #26 and Module #27
Remove the 2 modules with commands such as:
Code: Select all
pactl unload-module 26
pactl unload-module 27Next: Using Pulse Effects to improve the Sound Quality of the Blue Yeti Nano USB Microphone