this post was submitted on 12 Sep 2023
150 points (100.0% liked)
Gaming
30525 readers
108 users here now
From video gaming to card games and stuff in between, if it's gaming you can probably discuss it here!
Please Note: Gaming memes are permitted to be posted on Meme Mondays, but will otherwise be removed in an effort to allow other discussions to take place.
See also Gaming's sister community Tabletop Gaming.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My snowball would like a word. If you could hear it. Over it picking up everything else in the room.
If I had a dollar for every time people recommended Blue mics while any dynamic mic would've been a better option, I'd be a rich man.
The problem with blue products, isn't the quality but rather it's the price, you can get so much more for the same amount of money as a snowball or yeti.
As for it being too sensitive, try turning it down andoving closer to it, or just using a noise gate, or even noise reduction (like rnnoise based or RTX voice). There are plenty of options for tuning a microphone for better quality. And you don't have to go for the manufacturers software.
Personally I have a Audio interface with an XLR AT2020, and my noise gate and compressor plugin chain running on Carla works fine for what I have on my Linux setup, but you don't even have to go that far. All you need is something like voicemod, voicemeeter, EasyEffects or noisetorch or other standalone setups.
I'm just using pulse effects for gates and compressors.
I was more talking about it's not a directional mic and sound from behind it is no different to the mic as sound in front of it really. So it just picks everything up.
Ahh, a noise reduction setup like rnnoise (noisetorch) might actually help you with that - you can use it to replace the noisegate, as it has voice activation detection which works like a noisegate
It's not a big deal really. I do like the mic because I paid next to nothing for it. (Yay, cheap marketplace shit.) Besides, I rarely use it.
That and I've had to switch over to flatpak pulse effects which refuses to see the mic and allow me to add effects. (The flatpak version of pulse effects didn't even fix the problem I had anyways.)
If you are willing to switch to Pipewire, try EasyEffects, it might work better as it's based off of pulse effects, but for Pipewire, it's actually developed by the original Devs of pulse effects - in fact the original pulse effects repo is now the easy effects repo, the old pulse effects hasn't actually been updated for an entire year now, so you might notice it working less and less well.
To me, Pipewire is the best option for audio on Linux at the moment, it combines the power and low latency of JACK with the ease of use, and multiple device capability of PulseAudio, it really is a great project and is pretty much rock solid at this point in time. It might also fix your issues with pulseeffects/EasyEffects not recognising your microphone.
Honestly, I still don't use flatpaks for specific things - namely OBS, as I have a Blackmagic capture card, and the flatpak version of OBS won't support it due to how the BMD driver is required to be installed. Sure it's good for a lot of things, but sometimes the other options are better for your purposes. I still use the AUR Tytan652 version.