Open Nibato opened 10 years ago
/cc @mirhl @kissaki @aforanonymous
Why do you guys want to use ASIO for output as opposed to WASAPI?
The plan for Mumble 1.4.0 is to drop ASIO completely, because we believe WASAPI should be sufficient.
We'd like to be proven wrong. Thanks!
Milestoning for 1.3.0; we want to solve the discussion during 1.3.0.
Yes, I read #1604. Though I could never even use ASIO due to this very problem with my xonar..
So I always used WASAPI tbh, and I don't think it has any actually important downside.
If any, I believe it would just be a pity for this program to lose support for the still[??] least latency prone API out there. I mean, just think how those "faster than through air" arguments would dampen their appeal.
Removing the 1.3.0 milestone, adding 1.4.0 instead.
I don't know where I should post this, but I just now figured out ASIO (no ASIO4all, I'm saying the real one) is working natively in Realtek dsp. You just need to install the relative driver.
ftp://spcust:hwwk758z@ftp3.realtek.com.tw/Realtek/ASIO_v2.2.zip
(stupid github seems not to support ftp protocol)
I feel like this changes everything, considering this now becomes something available to 99% of people, rather than 1%.
I have an audio device that has a ton of outputs, but most of them can only be used with the ASIO interface. I noticed mumble seems to support using ASIO as an input device, but not for the output device.