Hello everyone,
I’m reaching out to the community to discuss some challenges I’ve been facing with WASAPI on Windows 11, particularly when trying to achieve a full digital capture of all system audio, much like how it worked seamlessly on Windows 10.
On my previous setup with Windows 10, WASAPI allowed me to digitally capture every sound I heard - system audio, application sounds, and screen readers like JAWS - in a direct digital fashion. Whenever I adjusted playback volume, recording volume wouldn’t change at all. This made it ideal for recording without any external noise interference or latency. However, since upgrading to Windows 11 and using a laptop with Cirrus Logic High Definition Audio drivers, the functionality of WASAPI appears to have changed significantly.
The Issues:
Limited Functionality:
While WASAPI still appears as an option in Audacity, it doesn’t behave as it did in Windows 10. Instead of capturing all system sounds with the Headphones / loopback device, it seems less reliable and incomplete in its output. Volume changes are now affected in the recording (awful), static is introduced (defeatesthe purpose!) and the audio just sounds a lot worse on this driver.
Latency:
When attempting to route JAWS (a screen reader) through any virtual audio device to capture it with WASAPI, I experience significant latency, which renders the setup almost unusable. This latency was nonexistent on Windows 10.
Incompatibility with Cirrus Logic Drivers:
My laptop uses Cirrus Logic High Definition Audio drivers. Despite multiple attempts to configure and test, the drivers don’t seem to allow WASAPI to capture all audio correctly. Additionally, replacing the Cirrus Logic drivers with the native Microsoft High Definition Audio driver isn’t an option, as the Microsoft driver is not listed in my system’s “Let me pick from a list” driver selection.
Virtual Audio Solutions Are Inaccessible:
I’ve experimented with solutions like VB-Cable and Voicemeeter Banana to create a digital loopback, but these tools are largely inaccessible for blind users. This makes them impossible to configure and manage effectively.
My Goal:
I’m trying to replicate the behavior of Windows 10 WASAPI as closely as possible on Windows 11. Specifically, I want to capture every sound I hear in a direct digital format, without latency or quality loss, and without introducing inaccessible third-party software into the mix.
Has anyone else experienced similar issues with WASAPI on Windows 11? Even when you sllect the main headphones device, its “Loopback” device, it still messes things up for me!
Are there specific configurations or tweaks I might have missed to make WASAPI work as it did on Windows 10?
Can Audacity developers shed light on whether changes in WASAPI functionality are due to differences between Windows 10 and 11, or something specific to my drivers?
Are there alternative tools or methods that are fully accessible and could achieve what I’m trying to do?
I appreciate any insights or advice you might have. Thank you in advance for your help!
Best regards,
Michael
DOES ANYBODY HAVE A FRICKIN’ SOLUTION FOR THIS??? I CAN’T GET ANYTHING TO WORK LIKE THE OLD WINDOWS 10 WASAPI LOOPBACK, AND I JUST HATE THIS WINDOWS 11 CRAP!!! I just wish we didn’t have to force to move on to Windows 11 because at least on my own laptop, I cannot record using Wasapi / Loopback like I used to, and THIS IS VERY VERY IMPORTANT!!! WHY HAS WINDOWS 11 TURNED INTO A TOTAL PIECE OF TRASH!!!
Michael, we all know how frustrating running a Windows PC can be sometimes, as the former Dell Chief Software architect, I know more than most. However, for the most part, people responding are just volunteers and typing in ALL CAPS isn’t really that readable. You also don’t say which Windows 11 you have home/pro ?
As is the case often with complex hardware interactions, your problems in this case, are more than likely just that, your problems. The unique set of drivers, processor, etc. has somehow changed how Audacity can capture sound.
My experience with Windows 11 hasn’t changed from Windows 10. Note that I have not progressed beyond Audacity 3.2.2 as my use is fairly simple, recording from a USB controller to a Music Hall A2D which is connected to a turntable, 8-track, cassette and reel to reel tape deck. There have been too many UI changes for my use case and for now I’m happy to stick with backlevel audacity while it works.
I do from time to time use the loopback drivers for my hardware to record. Choosing the right driver, the right driver rate (Hz) is critical in this environment as you are asking Windows to basically pipe a reasonable amount of data back to itself and then have audacity capture. Having 2400Hz in one place, 9600 in another and 4800Hz for an adacity project is a roadmap for failure.
I’d start by checking all the devices are a compatible Hz and related settings. Microsoft have been making a lot of changes in the UI but many of the underlying services have not changed excep how you access them. Type Sound settings into the start bar, chose sound and then select “More sound settings” from the Advanced area. This should bring up the old sound device properties for playback/recording/communication etc.
I honestly don’t know which version of Windows 11 I’m using, I’ll need to ask my dad about that.
Unfortunately, when I go into Sound Settings and the Advanced tab of both the Speakers and the Headphones devices, the default format option isn’t there. The very first thing that appears is a Test button only. From what I gathered from other people who have that problem, the default can’t change from 16 bits / 48000 Hz, and this is why Wasapi Loopback can’t record in a similar way to how it used to with Windows 10 which supported 24 bit. I wish there was a way to change this setting again!
From what it sounds like, it sounds like you have an external audio interface. I’m just using the onboard sound card because I’m mostly budgeted, but if an external audio interface is required to record via Wasapi Loopback in 24 bit, I’ll let my dad know. He was the one who bought these new laptops for Christmas for me and my sister, since Windows 10 won’t be supported by the end of this year which I think is quite sad. I’ve also read other people’s online opinions, and while there are various ‘yes-screams’ and ‘no-screams’, there are mostly ‘no-screams’ for Windows 11.
The other problem is that VB Cable which seems to be the only other real solution for now, is totally unaccessible to blind people who use screen readers. I Emailed Vincent B. about this, and he says he has no plans to make the software accessible, which is technically illegal in the USA because all software must be accessible for people with disabilities, by law. But the laws might be different in France where he’s from.
Because it has to evolve or would die anyway. Corporate customers have been screaming at Microsoft for years to solve the virus and related security on Windows, Windows 11 is at last a first step on this path with Secure Boot and TPM.
Windows also needs to keep up with user needs. There have been a lot of changes in the way sound and video have been handled precisely because people want to project to other devices. At least on my Windows 11 system in my home office, I can stream the sound to play on a Denon amplifier and home wide speaker system in the living room. They’ve also made changes for VR headsets etc.
I’m not an apologist for Microsoft, but the fastest way to irrelevance is not to keep up with consumer trends.
I have a personal copy of Office 2016 which used to run on my old Windows laptop, until the laptop died. I removed the SSD, put it in a Dell Windows 11 Pro desktop and it runs great in a Hyper-V virtual machine. The logon, all the apps, everything work as it did on my old Windows 10 laptop. Not reinstallation.
Also Windows 10 systems are available for next to nothing. I wrote this back in 2021, it still applies and you only have to spend around $80 now to get a pretty decent i7 system that cannot be updated to Windows 11. If nothing else works, maybe try one of these ideas.
Well, the only reason for dad giving us Windows 11 laptops is literally due to the support. Since he told me that Windows 10 won’t be supported after October this year, I’m just taking his advice since he’s been in computers longer than I’ve been alive. If I had a choice, I’d definitely just keep my Windows 10 laptop for recording purposes and whatnot. But some reason I feel forced to give it up and use Windows 11.
I still have a Windows 7 computer! There are some applications that it won’t run but I use it as an “office machine” and the older apps run fine. I don’t need “support”. (I don’t use it on the Internet.)
My “audio video” computer is Windows 10. I originally set-up a separate A/V computer because I was experimenting with a lot of unknown audio/video applications (including lots of free utilities) and I didn’t want to take the chance of messing-up my main computer. The hardware won’t run Windows 11.
I also have a couple of Windows 11 laptops… I’m not completely out-of-date.
Now here’s the thing. The primary reason why I’m a Windows user is because one of the best companion audio editors specifically designed for the blind, “Studio Recorder” made by the American Printing House for the Blind in Kentucky, only runs on Windows. I don’t know how many times I’ve tried them to convince them to make a Mac version and they still refused, but if they made a Mac version I’d switch to Mac immediately. Even if it involves learning the Mac Audacity. But just because Studio Recorder is a forever Windows thing.
[quote=“Michael_Kazmierski, post:4, topic:127578, full:true”]
I honestly don’t know which version of Windows 11 I’m using[/quote]
In the start bar, type about system - there are also a number of differences between the updates.
Windows 11 Home 23H2 is most up to date and what you probably should have.
This will depend on your laptop/hardware. My external speakers on my monitor are supported in 16-bit or 24-bit, they also support 32kHz, 44.1 kHz and 4800 khz. Provided you match the speakers/loopback and project level in Audacity, you should be able to record everything at 16-bits / 4800 khz which is basic DVD level.
Yes, I have a Dell 34-inch 4k monitor with a built in soundbar. However, that said I am able to record using 16-bit 4800kHz using the built-in hardware on a Dell Inspiron 5410 2-in-1. It turns out I can even record via loopback on the default internal speakers at 24-bit / 9600kHz.
Do I take it from your post that you are visual impaired, that will make difficult for me to provide useful screen shots, especially as my last one didn’t upload correctly and I’m not sure why. I have put these screen shots on my website. Perhaps they will help.
Hopefully these will help you in the right direction. Also, try to find out the model and specifications of your new laptop. The manufacturer website should also dell you the capabilities of the sound chip/processor and that way you know what to expect.
Maybe this info will help.
OS Name Microsoft Windows 11 HomeComponents Version 10.0.22631 Build 22631Software Environment Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name MICHAEL
System Manufacturer Dell Inc.
System Model Inspiron 15 3520
System Type x64-based PC
System SKU 0B92
Processor 12th Gen Intel(R) Core™ i7-1255U, 1700 Mhz, 10 Core(s), 12 Logical Proc…
BIOS Version/Date Dell Inc. 1.29.0, 11/11/2024
SMBIOS Version 3.4
Embedded Controller Version 1.07
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 0YNT2Y
BaseBoard Version A00
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Bound
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = “10.0.22621.2506”
But yes, there’s clearly no way to change to 24 bit, and I swear by 24 bit especially for recording with Loopback. When I record using 16 bits there’s this constant static I can’t stand, and literally I tried this on my Windows 10: I did an experiment on my old laptop which uses that good RealTech driver just to compare. The volume is still not linked to the playback volume, but I actually recorded with Audacity using the Wasapi setting at 16 bits instead of 24 bits, and I heard the exact same kind of static I would hear if I would’ve been recording with the Cirrus driver because the Cirrus driver only supports 16 bits. I’m sure that problem would go straight away if it could support 24 bit, but also the other remaining problem would be for me is that the volume would still not be fixed. I wonder if there’s a way to keep the recording volume fixed on the new laptop. And my dad doesn’t mind looking into a better sound card for this new laptop because he knows how important sound quality is to me. If there’s no way to keep the recording volume fixed using the Cirrus driver, then do you think dad would be able to help me basically mirror my headphones to Cable Output using the VB Cable control panel? Or do you need VoiceMeter to do that? All I want is for all headphone sounds to be mirrored to Cable Output while still being able to rely on listening to them normally so I can hear Jaws, my screen reader.
If you haven’t noticed already, this one is a Cirrus Logic High Definition Audio driver. But the other problem is, my sister’s laptop has a RealTech driver on it, but yet it only supports 16 bit / 48000 Hz. To me, 16 bits is not enough dynamic range.
I really can’t help you beyond what I’ve already recommended.
The best way to ensure you have the right, up to date drivers on your Dell Inspiron 15 is to run Dell support assist. If it is not installed, you can get it from here Support | Dell US
