|
|
#1 |
|
Human being with feelings Join Date: Aug 2007 Location: Near Cambridge UK and Near Questembert, France Posts: 22,690 |
Been ages since I even tried to use WASAPI on the studio machine — it still works fine on my W10 laptop but in the course of checking something else out today, I discovered I am getting a «WASAPI error — could not find output device format» No real big hurry as I seldom if ever need to use WASAPI on this machine.
__________________ |
|
|
|
|
#2 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,564 |
It’s probably the case that you have an Exclusive Mode for WASAPI selected in Reaper and the access to the audio device is blocked by another process/application (which is currently using the same audio device). In general, you might also check if the Allow applications to take exclusive control of this device option (in the Advanced Properties Tab) is disabled for all Devices in the Windows Sound Settings: https://support.presonus.com/hc/en-u…-audio-device-
Last edited by solger; 11-04-2017 at 12:09 PM.
|
|
|
|
|
|
#3 |
|
Human being with feelings Join Date: Feb 2009 Location: UK Posts: 1,429 |
Just adding to what solger said. |
|
|
|
|
|
#4 |
|
Human being with feelings Join Date: Aug 2007 Location: Near Cambridge UK and Near Questembert, France Posts: 22,690 |
Tried all the different modes available also juggled with 16bit vs 24 bit & no change. Thanks for the suggestions though. P.S. Just checked it on my laptop using shared mode and it works fine, so I will now have to double double check my settings on the studio machine — probably something stupid I missed,as it has always just worked before….
__________________ |
|
|
|
|
|
#5 |
|
Human being with feelings
Join Date: Dec 2012 Posts: 11,847 |
Try «Exclusive(polled)» mode. Restart Reaper after that. Oh, download fresh version and install it as portable. If it will work, there is a problem with your options. |
|
|
|
|
|
#6 |
|
Human being with feelings Join Date: Aug 2007 Location: Near Cambridge UK and Near Questembert, France Posts: 22,690 |
I will give the portable version a try. Silly me — I have advised countles people on here to do exactly that to figure out where a problem lies, too!
__________________ |
|
|
|
|
|
#7 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Did you get this working Ivan? WASAPI driver no longer working for me in Reaper 5.92 and Win10 (all drivers/updates bang up to date). Reaper says: Similarly it doesn’t work in IL standalone software. The NI and Pianoteq work just fine. I haven’t used the WASAPI device in the last few weeks so I don’t know when this issue started. Evidently the hardware works. |
|
|
|
|
|
#8 |
|
Human being with feelings
Join Date: Nov 2011 Posts: 434 |
P.S.A, if anyone wants an excellent non interface ASIO driver that isnt asio4all, go download the Fl studio demo and you’ll automatically get the FL Asio driver. It is rock solid. |
|
|
|
|
|
#9 |
|
Human being with feelings
Join Date: May 2009 Posts: 29,038 |
The second half, possibly all of ^that error is possibly coming from the OS, and it reads as if it is attempting exclusive mode and not getting it because something else may already have it open in some mode.
__________________ |
|
|
|
|
|
#10 |
|
Human being with feelings Join Date: Feb 2008 Posts: 57 |
Hello, Same problem here. Regards, Johan |
|
|
|
|
|
#11 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Quote:
Originally Posted by johan-v Hello, Regards, Johan Hi Johan, Quote:
Originally Posted by thevisi0nary P.S.A, if anyone wants an excellent non interface ASIO driver that isnt asio4all, go download the Fl studio demo and you’ll automatically get the FL Asio driver. It is rock solid. Cheers. I would like to use the driverless WASAPI for this, not add another ASIO into the mix. Quote:
Originally Posted by karbomusic The second half, possibly all of ^that error is possibly coming from the OS, and it reads as if it is attempting exclusive mode and not getting it because something else may already have it open in some mode. Yes, however it won’t work in shared mode either, but I guess it might not work in that mode anyway? |
|
|
|
|
|
#12 |
|
Human being with feelings
Join Date: May 2009 Posts: 29,038 |
Quote:
Originally Posted by Softsynth Yes, however it won’t work in shared mode either, but I guess it might not work in that mode anyway? What peaked my interest more was what else might have it or makes the OS/Reaper thinks it has it. Not that something isn’t broken, just the engineer/geek poking its head up. I can always test when I have time with a test portable install since I use ASIO/RME in my main config/install.
__________________ |
|
|
|
|
|
#13 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Quote:
Originally Posted by karbomusic What peaked my interest more was what else might have it or makes the OS/Reaper thinks it has it. Not that something isn’t broken, just the engineer/geek poking its head up. I can always test when I have time with a test portable install since I use ASIO/RME in my main config/install.
Yes I suspect that is what is going on too. |
|
|
|
|
|
#14 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
My mistake, one mode working. The «shared loopback» (CAUTION) mode works. Non of the other modes will play ball. Never used that mode before. Reaper manual says about this mode: However I was merely using this to enable sound from Software synths, WAV files from inside Reaper without muting output. Following the guide you can indeed record anything such as YT with WASAPI, just as you can with ASIO with the right settings.
Last edited by Softsynth; 07-11-2018 at 12:46 PM.
|
|
|
|
|
|
#15 |
|
Human being with feelings
Join Date: Apr 2011 Location: St George, UT _ USA Posts: 2,855 |
Running now on Win10 Pro desktop PC, Reaper v5.92, Kontakt5.8.1(R43). This has been daily setup for months now BUT recently went back onto Pro Insider Preview _ now Build 17711. Was previously on v1803 and all has worked throughout the change. DAW #2 is still on v1803, but normally runs Focusrite Pro14 & their ASIO driver. |
|
|
|
|
|
#16 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Quote:
Originally Posted by sostenuto ……
Okay cheers.
Last edited by Softsynth; 07-11-2018 at 04:21 PM.
|
|
|
|
|
|
#17 |
|
Human being with feelings
Join Date: Apr 2011 Location: St George, UT _ USA Posts: 2,855 |
Yeah �. very different Reaper uses, and I sold my Grotrian Concert 225 some time ago, so nothing live/direct any more �. Tried singing into mic once, and the scar (from those whose name shall not be mentioned) is still present �… |
|
|
|
|
|
#18 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Quote:
Originally Posted by sostenuto Yeah …. very different Reaper uses I can use the internal card for what loopback modes gives me so still need a solution for external sources which is what the external sound device is for. Quote:
Originally Posted by sostenuto , and I sold my Grotrian Concert 225 some time ago, so nothing live/direct any more …. I don’t think the mono input on my cheapo 24/48 guitar interface was designed to do justice to your magnificent Grotrian! Boasting that she stuck around even after that eh! |
|
|
|
|
|
#19 |
|
Human being with feelings Join Date: Aug 2007 Location: Near Cambridge UK and Near Questembert, France Posts: 22,690 |
Totally forgot about this issue — mine turned out to be a messed up Win10 update which they «fixed» a day or so later & the new update had everything working again with no hitches since. Frustrating as hell when that happens and you waste all that time looking for errors in your interface drivers or Reaper itself…
__________________ |
|
|
|
|
|
#20 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Quote:
Originally Posted by ivansc Totally forgot about this issue — mine turned out to be a messed up Win10 update which they «fixed» a day or so later & the new update had everything working again with no hitches since. Frustrating as hell when that happens and you waste all that time looking for errors in your interface drivers or Reaper itself…
Cheers Ivan, |
|
|
|
|
|
#21 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
The following is a kludge (it used to work fine without this): This articles implies everything would be honky dory if everything was at the same rate. This appears to not be the case as I cannot work either device outside 48khz. My internal soundcard and external WASAPI sound device both work all the time at master sampling rate 48khz. Actually my internal soundcard crashes this Win10 machine if I don’t select 48khz. Has done this for years. It seems to be a quirk of how it works in Windows 10. I don’t mind it is stable with 48khz and works fine. If I disable input channels. I can use WASAPI. This renders WASAPI pointless, since then it just gives me the functions of another internal soundcard. |
|
|
|
|
|
#22 |
|
Human being with feelings Join Date: Aug 2007 Location: Near Cambridge UK and Near Questembert, France Posts: 22,690 |
This is weird. I have had no issues whatsoever with WASAPI since I sorted out that bad W10 update. If you like, I will plod through my basic reaper settings & copy them for you just in case it is something I changed without realising it.
__________________ |
|
|
|
|
|
#23 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Quote:
Originally Posted by ivansc This is weird. I have had no issues whatsoever with WASAPI since I sorted out that bad W10 update. If you like, I will plod through my basic reaper settings & copy them for you just in case it is something I changed without realising it.
Hi Ivan, |
|
|
|
|
|
#24 |
|
Human being with feelings
Join Date: Jul 2008 Location: Putnam County, NY, USA Posts: 3,950 |
Hi- This isn’t exactly the same as the OP’s issue, since I don’t get a WASAPI or any other error, but this is the thread that came up with a search and it’s not all *that* old I used to be able 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 Audio Device Settings is grayed out, so I can’t select a track input. I followed the instructions in the User Guide, and «Allow feedback» is enabled in Project Settings. WASAPI loopback works fine in Audacity with the recording device set to the Main Output of my Komplete Audio 6 Main Output, so it’s not the end of the world, but I’d prefer to use REAPER for this. REAPER v.5.961/x64, Windows 10 x64 Thanks! -Susan |
|
|
|
|
|
#25 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,103 |
Alesis support told me the fall creators update for Win 10 messed up a lot of systems. I confirmed that the issue was with WASAPI not the hardware by getting other (terrible latency) drivers to work with the Core 1. Unusable but technically working, proving it is a software issue. Also I cannot use my WASAPI USB microphone either. Same issue in Reaper and Audacity. |
|
|
|
|
|
#26 |
|
Human being with feelings
Join Date: Jul 2008 Location: Putnam County, NY, USA Posts: 3,950 |
Hi Softsynth- That’s interesting. Since it works fine in Audacity, it’s not a big deal for me, as I said. I don’t want to revert my Windows to an earlier version, so I’ll just leave it alone. At this point, I’m just curious why I can’t choose my KA6 output as an input in REAPER while I can in Audacity. Thanks for the reply! -Susan |
|
|
|
|
|
#27 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,564 |
Quote:
Originally Posted by Susan G That’s interesting. Since it works fine in Audacity, it’s not a big deal for me, as I said. I don’t want to revert my Windows to an earlier version, so I’ll just leave it alone. At this point, I’m just curious why I can’t choose my KA6 output as an input in REAPER while I can in Audacity. Hi Susan, I just tested this here with the KA6: I believe the input device box in Reaper is greyed out by default when using WASAPI Shared loopback. So having the KA6 selected as Output Device should be sufficient. Another thing to check in general might be that the sample rate for the KA6 entries in the Windows Sound Settings (Playback Device > Properties > Advanced) and Reaper are matching. |
|
|
|
|
|
#28 |
|
Human being with feelings
Join Date: Jul 2008 Location: Putnam County, NY, USA Posts: 3,950 |
Quote:
Originally Posted by solger Hi Susan, I just tested this here with the KA6: I believe the input device box in Reaper is greyed out by default when using WASAPI Shared loopback. So having the KA6 selected as Output Device should be sufficient. Hi Solger- Eureka! The Input Channels setting was in fact 2, but I had my Output Channels setting on 0. Changed that to 2 and it’s now working great. Thanks so much! -Susan |
|
|
|
|
|
#29 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,564 |
Quote:
Originally Posted by Susan G Eureka! The Input Channels setting was in fact 2, but I had my Output Channels setting on 0. Changed that to 2 and it’s now working great. Great |
|
|
|
|
|
#30 |
|
Human being with feelings
Join Date: Mar 2014 Location: Louisville, KY, USA Posts: 1,070 |
I thought I’d share. REAPER v5.983 x64 For me the solution was to restart REAPER. When WASAPI wouldn’t engage, ASIO4ALL also would not engage. Both worked perfectly after closing REAPER and starting it back up again. |
|
|
|
|
|
#31 |
|
Human being with feelings Join Date: May 2018 Posts: 16 |
Quote:
Originally Posted by thevisi0nary P.S.A, if anyone wants an excellent non interface ASIO driver that isnt asio4all, go download the Fl studio demo and you’ll automatically get the FL Asio driver. It is rock solid. I agree, this is actually one of the best that I have used! |
|
|
|
|
|
#32 |
|
Human being with feelings Join Date: Oct 2009 Posts: 20 |
Sorry about the necro bump, but this just happened to me after attempting to install the waves suite. The first thing I noticed was the windows default audio device was changed to «Speakers (Waves Soundgrid)» and I changed it back to «Speakers / Headphones» because I couldn’t hear anything. But now when I start Reaper, I get the error about WASAPI, I tried changing it from «shared mode» to «Exclusive mode» but now I get the error: There was an error opening the audio hardware: WASAPI error: could not find input device format I don’t understand why Waves has to be so intrusive and just act like any other normal plugin without taking over the entire audio configuration of your machine and screwing it all up. edit: I went into «open sound settings» (this is win 10 btw) by right clicking the speaker in the notification area and hitting «open sound settings» and there, under «input» I noticed the default input device had also been changed to «Line in / Mic (Waves Soundgrid)» so I changed it back to the normal «Microphone Array (Realtek audio)» and now I can hear audio from reaper again. Ridiculous.
Last edited by danknugz; 01-09-2023 at 09:05 AM.
|
|
|
|
|
Forum Jump |
All times are GMT -7. The time now is 10:30 PM.
Powered by vBulletin® Version 3.8.11
Copyright ©2000 — 2023, vBulletin Solutions Inc.
-
#1
Здравствуйте, и это снова я со своим Realtek, в общем после той фигни с ASIO я забил болт на ASIO и использовал WASAPI в Shared режиме, задержка была довольно низкой и при этом не блокировалось аудио, можно было включить и Exclusive mode чтобы задержка была ещё меньше, но вот мне пришлось переустановить винду и снова столкнулся с проблемой, WASPI не работает вообще, что Shared mode, что Exclusive mode — ошибка та же:
Код:
There was an error opening the audio hardware:
WASAPI error: could not initialize shared input deviceОкей, из ошибки ясно что проблема в Input device, ставим такие вот настройки:
Жмем ОК и офигеваем от задержки в 60 MS!!!! (раньше было максимум 20 ms) Конечно это очень странно, окей — ставим Exclusive mode с такими же настройками — ситуация лучше 7.6 ms (у ASIO4ALL к примеру — минимум 16 ms), в чём может быть проблема?
-
#2
в чём может быть проблема?
Ну собственно, в этом и проблема: если работает в shared mode — то он все равно ждет, пока все приложения свои буфферы отдадут, а там приоритеты не такие, как в рипере.
-
#3
В общем проблема решена, надо было ставить Input device channels не 0, а 1
Forum rules
This forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from «Help menu > About Audacity«.
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
-
Justgoble
- Posts: 5
- Joined: Sun Feb 20, 2022 9:32 pm
- Operating System: Windows 10 / 11
Wasapi not working [SOLVED]
I’ve been using audacity for a long time and have always been able to record from my sound card. after update to 3.0 when I try to use WASAPI I get the message Unable to open sound device.. and these are the details..
{
«timestamp»: 1645395559,
«event_id»: «f326041e3bbc2c4099c9a5592fdd8c9f»,
«platform»: «native»,
«release»: «[email protected]»,
«contexts»: {
«os»: {
«type»: «os»,
«name»: «Windows»,
«version»: «10.0.22000»
}
},
«exception»: {
«values»: [
{
«type»: «Error»,
«value»: «Error opening sound device.nTry changing the audio host, playback device and the project sample rate.»,
«mechanism»: {
«type»: «runtime_error»,
«handled»: false
}
}
]
}
}
I’ve changed every sample rate, and matched them in windows and on audacity multiple times. I’ve unistalled and reinstalled, and rolled back all the drivers. nothing seems to work! Please help!!
-
jademan
- Posts: 3658
- Joined: Fri Jul 17, 2009 10:11 pm
- Operating System: Windows 10 / 11
Re: Wasapi not working
Post
by jademan » Sun Feb 20, 2022 10:30 pm
Justgoble wrote: ↑
Sun Feb 20, 2022 10:21 pm
I’ve changed every sample rate, and matched them in windows and on audacity multiple times. I’ve unistalled and reinstalled, and rolled back all the drivers. nothing seems to work! Please help!!
If this is an external USB sound card, make sure it is turned on and connected before you start Audacity. Otherwise Tranport > Rescan Audio Devices.
Audacity Volunteer
-
Justgoble
- Posts: 5
- Joined: Sun Feb 20, 2022 9:32 pm
- Operating System: Windows 10 / 11
Re: Wasapi not working
Post
by Justgoble » Tue Feb 22, 2022 2:07 pm
It is not, it is the internal soundcard that came in the computer. Which is an HP Omen. I never had this problem until I upgraded to 3.0. One other thing that may have changed, I now have the computer running through a Sony receiver via HDMI. So the sound is output through the HDMI port. I don’t think that should effect anything considering my goal is to record internally anyway!
-
Justgoble
- Posts: 5
- Joined: Sun Feb 20, 2022 9:32 pm
- Operating System: Windows 10 / 11
Re: Wasapi not working
Post
by Justgoble » Tue Feb 22, 2022 2:09 pm
Also I’m using Audacity 3.1.3 and Windows 11
-
jademan
- Posts: 3658
- Joined: Fri Jul 17, 2009 10:11 pm
- Operating System: Windows 10 / 11
Re: Wasapi not working
Post
by jademan » Tue Feb 22, 2022 2:19 pm
Justgoble wrote: ↑
Tue Feb 22, 2022 2:07 pm
I now have the computer running through a Sony receiver via HDMI.
Hmm… Even now, I am trying to visualized this… 
Justgoble wrote: ↑
Tue Feb 22, 2022 2:07 pm
So the sound is output through the HDMI port.
HDMI drivers have caused issues for other Audacity users in the past. In the upper right corner of the Forum, you can search for HDMI.
Perhaps someone else will want to comment.
Audacity Volunteer
-
Justgoble
- Posts: 5
- Joined: Sun Feb 20, 2022 9:32 pm
- Operating System: Windows 10 / 11
Re: Wasapi not working
Post
by Justgoble » Wed Feb 23, 2022 6:38 am
I will see what I can find when I search that! Thank you for your time!
-
Justgoble
- Posts: 5
- Joined: Sun Feb 20, 2022 9:32 pm
- Operating System: Windows 10 / 11
Re: Wasapi not working
Post
by Justgoble » Wed Feb 23, 2022 6:41 pm
I figured it out! If anyone else runs into this issue, in the sound setting on Windows 11 on the playback device menu under advanced options, it was set at 5.1 for my surround sound. I have to change that to Sonic for headphones. Once I do that I can us WASAPI like normal. But I do not have surround sound. So I just have to switch back and forth when recording via loopback, and everything else. Thanks for your time! I hope this helps anyone else that may be running into this issue!
-
jademan
- Posts: 3658
- Joined: Fri Jul 17, 2009 10:11 pm
- Operating System: Windows 10 / 11
Re: Wasapi not working [SOLVED]
Post
by jademan » Wed Feb 23, 2022 10:17 pm
Thanks for posting back with a solution I never would have guessed! I have marked this thread as solved.
Audacity Volunteer
-
steve
- Site Admin
- Posts: 86194
- Joined: Sat Dec 01, 2007 11:43 am
- Operating System: Linux *buntu
Re: Wasapi not working [SOLVED]
Post
by steve » Thu Feb 24, 2022 10:13 am
Justgoble wrote: ↑
Wed Feb 23, 2022 6:41 pm
I figured it out! If anyone else runs into this issue, in the sound setting on Windows 11 on the playback device menu under advanced options, it was set at 5.1 for my surround sound. I have to change that to Sonic for headphones. Once I do that I can us WASAPI like normal.
That’s very useful. I’ll lock this topic so that it doesn’t get buried.
Learn more about Nyquist programming at audionyq.com
Windows 10: WASAPI can’t see audio input of generic USB audio device
Discus and support WASAPI can’t see audio input of generic USB audio device in Windows 10 Drivers and Hardware to solve the problem; I have a very old Roland audio interface (UA1-EX) which I have to use in its generic USB audio mode because it is no longer supported by Roland. I have…
Discussion in ‘Windows 10 Drivers and Hardware’ started by ricecrispies, Dec 22, 2017.
-
WASAPI can’t see audio input of generic USB audio device
I have a very old Roland audio interface (UA1-EX) which I have to use in its generic USB audio mode because it is no longer supported by Roland. I have been able to get it working using ASIO4ALL and record from its audio input, albeit very poorly. So I decided to try using it with WASAPI. However in my DAW’s audio device controls, the mic input of the interface is not listed, even though its ouput is. Why would the input of a generic USB audio device not be available in WASAPI?
-
Windows 10 BSODs
Yes, twice. Both as Headphones (USB Audio Device) and Headset Microphone (USB Audio Device) in Audio Inputs and Outputs which is using the generic Microsoft driver (10/29/2015 and version 10.0.10586.0)
As well as USB Audio Device in Sound, video and game controllers which is using the following drivers:
- dmk.sys
- ksthunk.sys
- portcls.sys
- USBAUDIO.sys
- SysFixUI.dll
- WMALFXGFXDSP.dll
-
Xbox recording has no sound while playedback.
There is something you can try, though it is unnecessarily complicated:
- Use a different screen recorder
- Download Audacity (it’s free). Set the audio provider as Windows WASAPI and the input device as your speakers. Then record, and piece the recording together to match the sound.
WASAPI can’t see audio input of generic USB audio device
-
WASAPI can’t see audio input of generic USB audio device — Similar Threads — WASAPI can’t audio
-
Audio Input Device Not Recognised
in Windows 10 Software and Apps
Audio Input Device Not Recognised: As the title says my recently purchased microphone isn’t showing up as an input device. this is the error code 0x80004003but i have seen the other related posts and for some reason the update that allegedly caused the fault isn’t showing up on my uninstall updates tab even… -
Audio Input Devices Not Showing
in Windows 10 Drivers and Hardware
Audio Input Devices Not Showing: My headset has a built in microphone into it, but when I plug it in the microphone doesn’t work. The audio does, but not the microphone. I have looked on many forums and have tried to fix the problem, but nothing seems to be working. I have never had this problem before, even… -
audio input device
in Windows 10 Drivers and Hardware
audio input device: I just recently keep getting a pop up constantly regarding the conextant audio failed to >>>>. How do I get rid of it?https://answers.microsoft.com/en-us/windows/forum/all/audio-input-device/50ffcf6f-9935-4e5f-8401-8196c6f081b6
-
USB audio input freezes
in Windows 10 Drivers and Hardware
USB audio input freezes: I have a USB turntable that used to work just fine. Now, when try to record or just listen to with the audio device set to 2-channel 16-bit 44.1kHz or higher sampling rate, the audio will freeze after a bit.I’m not using any application software at all. I just open the…
-
Available Audio Input Device
in Windows 10 Drivers and Hardware
Available Audio Input Device: I have a Bluetooth headset which is paired with a PC. However, when in Settings > System > Sound it appears as an available output device but not in the input devices selection box; it is empty. To resolve the problem I have updated the driver / removed the device in Settings… -
USB audio input
in Windows 10 Drivers and Hardware
USB audio input: I can’t get my computer to recognize audio from a mixer through the USB port.https://answers.microsoft.com/en-us/windows/forum/all/usb-audio-input/85208a1b-6d71-4501-83f8-827d76baf1ff
-
Audio Input Device
in Windows 10 Drivers and Hardware
Audio Input Device: Have downloaded the latest microsoft Windows 10 update applied and I lost my Audio. I do not have a microphone or headset. Just want my sound back with my apps.https://answers.microsoft.com/en-us/windows/forum/all/audio-input-device/7765bd26-430f-45a0-a0fa-8b86f8bc8480
-
USB GENERIC AUDIO ERROR
in Windows 10 Installation and Upgrade
USB GENERIC AUDIO ERROR: Hi,i have a problem with my usb headset like for 2 weeks and i cant fix it. I cant stream because the streaming app cant controll my headphone volume. When i lower my volume from pc ( windows ) it doesnt effect the stream app. My viewers are hearing always the same…
-
Code 10 generic usb audio device
in Windows 10 Drivers and Hardware
Code 10 generic usb audio device: So i own a FIIO E10k DAC/AMP the asio drivers that they have make my PC BSOD,this is a well known problem among both asio users and E10K usersThat’s why they recommend using the windows audio drivers that automatically install when you plug it in…
for some reason i can’t…
Users found this page by searching for:
-
WASAPI error: could not find input device
,
-
wasapi input software windows
,
-
cant find wasapi input radio.co
- Remove From My Forums
-
Question
-
I have posted this question on Larry Osterman’s blog:
http://blogs.msdn.com/larryosterman/archive/2009/08/07/a-quick-run-through-the-new-windows-7-multimedia-audio-sdk-samples.aspxI am following a sample, CaptureSharedTimerDriven, under SDK 7.0 on Win 7 RTM release, 64 bit version,
here is what I have changed in the code as Larry has hinted in his blog to make it work in ExclusiveMode
HRESULT hr = _AudioClient->Initialize(AUDCLNT_SHAREMODE_EXCLUSIVE, 0, _EngineLatencyInMS*10000, _EngineLatencyInMS*10000, _MixFormat, NULL);
the above call returns me a very large -ve number (-2004287480, HEX: 0xFFFFFFFF88890008) on Win 7 64 bit version, on 32 bit you can expect the return code to be 0x88890008Previously I was using the sample from SDK 6.1 as
hr = pAudioClient->Initialize(
AUDCLNT_SHAREMODE_EXCLUSIVE,
0,
hnsRequestedDuration,
hnsRequestedDuration,
pwfxInTemp,
NULL);
This code has been working fine on Vista but fails on Win 7, which had made me try the sample from SDK 7.0 but the result is the same,Machine: Dell Gx620
Processor: Intel Pentium D CPU 2.80 GHz
RAM: 1.00 GB
OS Win 7 Ultimate, RTM, 64 bit version
Device: WebCam with a microphone, Logitech Pro 9000
Driver: MS UVC Driver, 6.1.7600.16385On a side note I have also tried with my Logitech Driver, but that doesnt work either
Can somone please help me out here, I would really appreciate it.
Thanks in advance
aliqadri
-
Edited by
Thursday, October 1, 2009 3:30 AM
Update the Hyperlink
-
Edited by
-
tox
- Posts: 10
- Joined: Thu Oct 06, 2016 4:43 pm
Re: Trouble with WDM Realtek digital output
Yes, the problem only appears to affect Dolby Digital Live. On a side note, Dolby DIgital Live and DTS Connect are once again broken in Windows 10 Insider Builds. I’m now running build 14986 and it doesn’t work no matter whether it’s direct from the Realtek driver or via Voicemeeter.
Microsoft really need to get their act together when it comes to multichannel / multi device audio.
-
CaptaPraelium
- Posts: 21
- Joined: Mon Oct 17, 2016 4:31 am
Re: Trouble with WDM Realtek digital output
Post
by CaptaPraelium » Thu Feb 16, 2017 2:52 pm
Vincent Burel wrote:the problem seems to concern only this Realtek Optical output in multichannel mode and WDM interface…
we simply have to reproduce the problem here to correct it…
what is connected to your optical link : an AV-amplifier ?
I agree, it seems specific to multichannel mode (dolby digital specifically) and WDM and realtek cards.
I have a headset base-unit connected to the PC via optical cable. I’ve tried a hifi receiver and had the same behaviour.
I have lots of spare time if you want any testing done consider me available.
-
CaptaPraelium
- Posts: 21
- Joined: Mon Oct 17, 2016 4:31 am
Re: Trouble with WDM Realtek digital output
Post
by CaptaPraelium » Fri Feb 17, 2017 9:12 am
Thank you for helping us!
Good idea. I had not seen this problem anywhere else but after a few minutes trying different configurations of VLC, I was able to get the distortion to occur. It only gives distortion when I select «Windows Multimedia Device output» as the ‘Output module’, and select my realtek optical output as the default in windows. Using this configuration, if I view the module list, I can see ‘generic»wasapi»‘ as a loaded module. Other configurations which do not distort, do not show this module… So I guess I am using wasapi when the distortion occurs, and no distortion when I am not using wasapi.
I hope this helps. Please let me know if there’s anything else I can try for you.
-
CaptaPraelium
- Posts: 21
- Joined: Mon Oct 17, 2016 4:31 am
Re: Trouble with WDM Realtek digital output
Post
by CaptaPraelium » Fri Feb 17, 2017 1:10 pm
This may be interesting: Reaper seems to work with this card and driver in WASAPI mode. Exclusive mode throws an error:
Code: Select all
There was an error opening the audio hardware:
WASAPI error: could not find output device format
But shared mode works fine. No distortion, no long/odd length buffers
HTH!
By the way, I stumbled across ASIO drivers for these cards while testing, if anyone’s interested I could send a link.
-
tox
- Posts: 10
- Joined: Thu Oct 06, 2016 4:43 pm
Re: Trouble with WDM Realtek digital output
Post
by tox » Fri Apr 07, 2017 6:37 pm
Just an FYI, since all Insider builds and the current live build have now syncronised to the Creative Update, DDL and DTS Interactive are now broken on all current builds of Windows 10. We can only hope that Microsoft fix this but they seem to be pushing Dolby Atmos and Windows Sonic Audio as these are now integrated in the sound options.