Is WASAPI not working properly on Win10 now? [Datei] (2023)

ivansc

04-11-2017, 11h07

It's been years since I tried to use WASAPI on the Studio machine; It still works fine on my W10 laptop, but when I checked something else today, I found that I got a "WASAPI Error: Could not find output device format".
Has anyone shed some light?

I'm in no rush as I rarely need to use WASAPI on this machine.

Solger

11/04/2017, 11:55

It is likely that you have selected an exclusive WASAPI mode in Reaper and another process/application (currently using the same audio device) is blocking access to the audio device.
If you haven't already, try setting WASAPI mode to [Shared Mode] in Reaper.

In general, you can also make sure that apps take exclusive control of this device. The option (in the Advanced Properties tab) in Windows sound settings is disabled for all devices: https://support.presonus.com/hc/de-br /articles/210046283-How-do-I-disable-the- exclusive-mode-for-a-windows-audioger-

dorado

04.11.2017, 14:00

ivansc

04-11-2017, 14h07

I have also tried all available modes with 16 bit vs 24 bit and no change.
To clarify, it's WASAPI in Reaper that's giving me the "Can't find any output" message, and that's with absolutely nothing besides my antivirus running and nothing else I might want to access the audio stream.

But thanks for the suggestions.

PS I just checked my laptop in shared mode and it works fine, so now I need to double check my settings on the studio computer, probably something stupid that I overlooked since it always worked before...

Vitalker

04.11.2017, 14h34

ivansc

05.11.2017, 01h45

soft synth

07.11.2018, 08:20

Did you get this job Ivan?

The WASAPI driver no longer works for me on Reaper 5.92 and Win10 (all drivers/updates are current). 🇧🇷
I used to plug in the WASAPI USB stick and immediately toggle it on in Reaper Preferences > Settings. Now neither mode works, it is neither exclusive nor shared.
However, the device works on standalone products like Pianoteq and FM8 with the correct settings, but not on Reaper.

cutter says:
"An error occurred while opening the audio hardware:
WASAPI-Fehler: Unable to initialize single input device"

It also does not work in the standalone IL software. NI and Pianoteq work very well.

I haven't used the WASAPI device in the last few weeks, so I don't know when this problem started. Obviously the hardware works.
I think you could try the portable version. Look what's going on there.

elvis0nario

07.11.2018, 08:23

carbon music

07.11.2018, 08:24

johan-v

07.11.2018, 09:14

Hola,

The same problem here.
WASAPI has stopped working.

Compliment,

Juan

soft synth

07.11.2018, 09:48

Hola,
The same problem here.
WASAPI has stopped working.

Compliment,

Juan
Hi John,
I suspect it is due to Windows Updates. It's funny how WASAPI modes work well for standalone software.

P.S.A. if anyone wants to have a great ASIO driver without any interface other than asio4all, please download the Fl Studio demo and you will get the FL Asio driver automatically. It's hard as a rock.

Health. I want to use driverless WASAPI for this and not add another ASIO to the mix.

In the second half maybe all ^this error maybe it's coming from the OS and it looks like it's trying exclusive mode and not getting it because something else might already have it open in a certain mode.

Yes, but it doesn't work in shared mode either, but I guess it doesn't work in that mode either.

carbon music

11-07-2018, 10h03

Yes, but it doesn't work in shared mode either, but I guess it doesn't work in that mode either.

What piqued my interest the most was what else it could have or make OS/Reaper think it had. Not that something isn't broken, just the engineer/geek looking up. I can always test with a portable test install when I have time since I use ASIO/RME in my main setup/install.

soft synth

07.11.2018, 10h17

What piqued my interest the most was what else it could have or make OS/Reaper think it had. Not that something isn't broken, just the engineer/geek looking up. I can always test with a portable test install when I have time since I use ASIO/RME in my main setup/install.

Yes, I also suspect that is why.
I don't expect anyone to try anything unless this issue might affect them, but thanks for the offer. 🇧🇷

soft synth

11.07.2018, 10h43

My mistake, a way of working.

The "Shared Loopback" mode (CAUTION) works. None of the other modes play ball.

I have never used this mode.

The Reaper manual says about this mode:
3.43
Record live Windows output
Windows users (Vista/7/8/10) can use
home driver
to record the live output of Windows (eg.
copyright restrictions, a YouTube video). This requires the use of a feedback loop, so you need to continue
Beyond this point, be careful. This is not recommended for beginners.
First create a new project file. Show project settings (
everyone sign up
) and enable it on the Advanced page
Allow comment routing
.
then show yours
Settings, Audio, Device
window and select
AT HOME
like your audio
System. to choose
shared loopback
way (cf.
On the right). requires block size and sample rate
match those of your sound device, as defined in
Panel de control de Windows.
Finally, just add a new track and arm it.
Recording. You probably want to set the input to
Stereo.
Mute the REAPER's audio output and press
R-Force
to record what you are playing
Windows. For example, it could be a YouTube video that you are listening to through your speakers.

However, I've only used it to mute soft synths and WAV files in Reaper without muting the output. If you follow the guide, you can record anything like YT with WASAPI and ASIO with the correct settings.
However, I would like the normal modes to work.

supports

07.11.2018, 12:58

Now it runs on desktop PC Win10 Pro, Reaper v5.92, Kontakt5.8.1 (R43).
START (Windows 7/8/10/Vista)
shared mode; Input: Default; Output: Speaker (Realtek High Definition Audio)
(4) input, (4) output, 512 block size, 24 bits, 48000 Hz.

This has been set daily for months, but has recently been moved back to Pro Insider Preview _ now build 17711. I was previously on v1803 and everything worked fine during the move.

DAW #2 is still at v1803 but normally works with Focusrite Pro14 and its ASIO driver.
I will test WASAPI on this system later today.

soft synth

07.11.2018, 14:59

......
.....
I will test WASAPI on this system later today.

Good, Prost. 🇧🇷
In loopback mode I can't record any input, just sounds from Windows or DAW VST, not the guitar.

supports

07.11.2018, 17:05

Yes actually . very different uses of Reaper, and I sold my Grotrian Concert 225 a while back, so nothing live anymore. 🇧🇷

I tried to sing into the microphone once and the scar (of those whose names should not be mentioned) is still there...

soft synth

07.12.2018, 12h57

Yes …. Very different uses of Reaper

I can use the internal card for what the loopback modes give me, so I still need a solution for external sources, which is the external sound device.

, and I sold my Grotrian Concert 225 some time ago, so I no longer live/live…. 🇧🇷
I tried to sing into the microphone once and the scar (of those whose names should not be mentioned) is still there...

I don't think the mono input on my cheap 24/48 guitar interface is designed to do Grotrian justice!

Brag about staying here after that, huh! 🇧🇷

ivansc

07.12.2018, 02:20

I completely forgot about this problem - mine turned out to be a broken Win10 update that they "fixed" a day later and with the new update everything has been working smoothly ever since.

It's very frustrating when that happens and you spend all that time troubleshooting the interface drivers or Reaper itself...

soft synth

07.12.2018, 02:36

I completely forgot about this problem - mine turned out to be a broken Win10 update that they "fixed" a day later and with the new update everything has been working smoothly ever since.

It's very frustrating when that happens and you spend all that time troubleshooting the interface drivers or Reaper itself...

Hug Ivan
That's how it is. Maybe a future Windows update will fix this?

soft synth

08.07.2018, 04:55

The following is a botch (used to work fine without):
https://blog.mouten.info/reaper-tips-how-to-fix-wasapi-shared-mode-device-error-input-device-samplerate-does-not-match-13d930dda5e1

This article implies that everything would be great if everything was at the same pace. This doesn't seem to be the case as I can't get either device to work outside of 48kHz.

My internal sound card and external WASAPI sound device run at a main sample rate of 48 kHz all the time. In fact, my internal sound card hangs on this Win10 machine if I don't select 48kHz. He's been doing this for years. There seems to be a quirk to how it works on Windows 10. I don't care that it's 48kHz stable and works fine.

When I turn off the input channels. I can use WASAPI. This renders WASAPI useless as it only gives me the capabilities of another internal sound card.
So if anyone has alternative ideas?

ivansc

08.08.2018, 02:01

That's weird. I haven't had any issues with WASAPI since I fixed the bad W10 update.
I just double checked and everything is fine on my laptop AND my main studio desk!

If you want, I'll go through my basic Reaper settings and copy them over for you in case I inadvertently changed something.

soft synth

08.08.2018, 02h29

That's weird. I haven't had any issues with WASAPI since I fixed the bad W10 update.
I just double checked and everything is fine on my laptop AND my main studio desk!

If you want, I'll go through my basic Reaper settings and copy them over for you in case I inadvertently changed something.

Hello Ivan,
Thanks for the offer, I don't want to get anyone in trouble like that.
I don't think it's the Reaper himself anyway. Most likely it has something to do with Windows updates and sound card drivers. The silence on the forum tells its own story, if it was a Reaper issue I would expect a few others to say the same.
I was hoping someone would come forward and say they solved the same problem. Maybe it's just a quirk of this system since no one else replies to say they have the same problem?

Susana G.

09.11.2018, 20:17

Oye-

This isn't exactly the same as the OP's problem, as I don't get a WASAPI or other error, but this is the thread that came up in a search and it's not all *so* old ;).

I used to record audio from my PC (YouTube etc) using WASAPI in "Shared Loopback" mode, but now I can't get it to work. The input device in the audio device settings is grayed out so I can't select a track input. I followed the instructions in the user guide and the "Allow comments" option is enabled in the project settings.

WASAPI loopback works fine in Audacity when the recording device is set to the main output of my Komplete Audio 6 main output, so it's not the end of the world, but I prefer to use REAPER for that.

SEGADOR v.5.961/x64, Windows 10 x64

Thank you very much!

-Suzanne

soft synth

11.10.2018, 02:57

Alesis support informed me that Fall Creators Update for Win 10 broke many systems.
They received many support requests with WASAPI devices, so they suggested going back to a previous version of Windows.

I confirmed that the issue was with WASAPI and not the hardware causing other drivers (horrible latency) to work with Core 1. Unusable but technically working which shows it's a software issue.

I also can't use my USB WASAPI microphone. Same problem in Reaper and Audacity.

Susana G.

11.11.2018, 13:38

Hallo Softsynth-

That's interesting. Since it works fine in Audacity, as I said, it's not a big deal for me. I don't want to revert my Windows to a previous version, so I'll leave it alone. At this point I'm just curious why I can't select my KA6 output as input in REAPER while I can in Audacity.

Thanks for the reply!

-Suzanne

Solger

11.11.2018, 13:54

That's interesting. Since it works fine in Audacity, as I said, it's not a big deal for me. I don't want to revert my Windows to a previous version, so I'll leave it alone. At this point I'm just curious why I can't select my KA6 output as input in REAPER while I can in Audacity.
Hi Susan,

I just tried this with KA6:

I believe the input device field in Reaper is grayed out by default when using the WASAPI shared loopback. So it should be enough to have selected the KA6 as the output device.
But here it seems important to reduce the number of input channels (eg 2) to have them available as track inputs.

Another general thing to check might be that the sample rate for the KA6 inputs in Windows Sound Settings (Playback Device > Properties > Advanced) and Reaper match.

Susana G.

11.11.2018, 15:08

Hi Susan,

I just tried this with KA6:

I believe the input device field in Reaper is grayed out by default when using the WASAPI shared loopback. So it should be enough to have selected the KA6 as the output device.
But here it seems important to reduce the number of input channels (eg 2) to have them available as track inputs.
Oi Solger-

Eureka! The input channel setting was actually 2, but I had my output channel setting at 0. I changed it to 2 and now it works great.

Thank you very much!

-Suzanne

Solger

11.12.2018, 10h31

insub

28.09.2019, 11h01

Thought I'd share.
I had trouble enabling the WASAPI driver, although it worked fine on all Native Instruments standalone versions.

SEGADOR v5.983 x64
windows 10 v1903

For me the solution was to restart REAPER.

If WASAPI didn't fire, ASIO4ALL didn't fire either. Both worked fine after closing and restarting REAPER.

Bill_Texas

28.09.2019, 11:52

P.S.A. if anyone wants to have a great ASIO driver without any interface other than asio4all, please download the Fl Studio demo and you will get the FL Asio driver automatically. It's hard as a rock.

Agreed, this really is one of the best I've ever used!