rs_asio VS winget-cli

Not natively, but you can mod the game to enable ASIO support.

Try changing the input channel, in fact if you check the premade config files in the github page, for the focusrite solo gen 3 (may also work on other Solo generations.) https://github.com/mdias/rs_asio/blob/master/docs/focusrite_solo/README.md you will se both inputs use channel 1

There is also a mod for the game that allows to use an existing audio interface for lower latency: https://github.com/mdias/rs_asio

Or try this: https://github.com/mdias/rs_asio

Why random googling and not looking for information at the source, i.e. the rs_asio github? It has sample configs for many interfaces https://github.com/mdias/rs_asio

Used the latest release from - https://github.com/mdias/rs_asio/releases+

Alternatively, you can use various interfaces with RS2014 via RS_Asio. So you can have direct monitoring for headphones or active speakers there. I mean, I think my Focusrite Scarlett Solo sounds noticably better than the RTC, but RTC is the simplest way to do it.

https://github.com/mdias/rs_asio/issues/140 for example - a user writes the 96 works just fine in 48kHz mode with a buffer size of 64.

GitHub

Source: https://github.com/microsoft/winget-cli/issues/3832

You're correct here, and that's exactly the reason Winget is a package manager, as dependency management is part of teh stable release since version 1.6.3133:

Currently, I'm troubleshooting an annoying issue on my shared devices that it's a hell to delete. See this ticket: https://github.com/microsoft/winget-cli/issues/3365

It's also on the official microsoft package manager (winget).

https://github.com/microsoft/winget-cli

Winget install