saaaameee, i have a HyperX solocast you?

try going to your sound settings (windows wise) and manually set your main mic there

same issue here

That's why there's a mic test demo 🤦

Some pull requests on the Godot Github propose that the issue is audio setups with multiple channels, ie surround sounds ones such as 5.1 or 7.1. In your instructions, you also mention changing the format to 1 or 2 channels as well as changing to 44100 Hz. Would you be able to confirm whether your mic works when using 44100 Hz but more than 2 channels? (assuming that's something your settings allow)

same issue. Using a shure microhpone connected to a studio 1810c audiobox, and then my headset is a HyperX cloud 2. Game picks up my mic, but doesnt play any of the audio back to me. 

im using the exact same setup and im also experiencing latency. its bad enough where it becomes difficult to play.
and like you said sample rate and buffer size have no effect on latency.  
if you were able to find a workaround or solution, i'd love to know :))

So I did some reading and ran some diagnostics. What it comes down to is the Focusrite driver.

The problem is specifically with non-ASIO applications. Like most games, Discord, etc.
The Focusrite ASIO driver is great and has great latency. Focusrite's WDM driver however... is trash. 
I've measured the latency in a bunch of different applications and the latency can be as bad as 400+ ms. 

Now I'm not sure if this also affects older Gens but it is absolutely a problem on the 4th Gen Scarlett. 
Specifically combined with Windows 11 it seems.

I've tried a lot of things, including looking at LatencyMon, changing things in MS Interrupt Affinity Tool, messing with sample rate, buffer size and the list goes on.

The only solution I have found thus far is completely removing all Focusrite drivers, I also removed whatever left-over folders and "invisible" devices I could find in my sound settings. Also make sure to double check your Device Manager.
Once you've done that, restart your PC and plug your Scarlett back in. 

Using Window's native drivers for the interface, you'll have next to no latency. It is miles better than the Focusrite driver.
I was immediately able to play games I wasn't able to play before due to massive latency improvements and also noticed a huge improvement on Discord.

You'll miss out on Focusrite Control 2 but in turn you'll have no latency, besides most of the functions are buttons on the interface itself. You're not missing out on a whole lot, except for the loopback function and Focusrite USB ASIO (if you were using that in a DAW for example).

The next paragraph only applies to 2i2 and above due to the amount of channels, this is not an issue with the solo if you change it to 44100 kHz like another user mentioned. (Can't test this as I'm using a 2i2 with 4 channels).

Now doing this you will run into the issue a lot of other people are having trying to play The Choicer Voicer. 
Which is the game won't recognize your microphone signal at all. (Not to worry it does work in every other application I tested, seems to be isolated to the Godot engine).
There is a relatively easy workaround, though. I just route my microphone through Voicemeeter and select the Voicemeeter output in The Choicer Voicer. Sure this will add the tiniest bit of latency again but compared to what it was using the Focusrite driver, it's negligible. Took a while but I can finally play the game, and a lot of other games I wasn't able to play before.

I do hope Focusrite fixes this issue at some point, it's a seriously bad oversight. 

Quick edit: Once you're using the Windows drivers make sure to go into your sound settings and turn off any audio enhancements. Windows likes turning those on for some reason. 

same thing happened to me it looks like it records and captures my voice but when it goes to play it back nothing happens

Yeah, I ran into the exact same problem. If anyone is wondering why this happens, it's a bug in the game engine itself, which struggles with audio capture when wireless devices are involved. The game picks up your voice signal, but the engine freezes up and fails to save or output the recorded audio file if Bluetooth headphones are set as the default device.

To fix it, you can set your standard motherboard audio and your microphone as the default devices in Windows, and then plug in regular 3.5mm wired headphones directly into the back of your PC. If you really want to use wireless headphones, you'll need to install a virtual audio cable program to bridge the audio stream so the game thinks it's working with a standard wired connection, and then everything will record and playback properly.