Ventrilo Tech Support

Ventrilo Tech Support (http://forum.ventrilo.com/index.php)
-   Windows Client (http://forum.ventrilo.com/forumdisplay.php?f=4)
-   -   Failed to open sound input device. (http://forum.ventrilo.com/showthread.php?t=4142309)

LeeroyBro 05-28-2018 07:00 PM

Failed to open sound input device.
 
I was using Ventrilo 3.0.8 client without problems. When launching the client, I received the popup notification that there is a new version (4.0.1) available, so I downloaded it. After having some issues with the install (had to run as administrator), I successfully got 4.0.1 running. Unfortunately the server I was connecting to has not yet upgraded, so I went back to the 3.0.8 client that is still on my computer. Now I receive the following error:

Failed to open sound input device. rc=-10, CreateCaptureBuffer failed. HR=E_FAIL. An undetermined error occurred

Whenever I use the PTT key, the following error occurs:
Can not transmit because the program has not successfully opened a sound input device such as a desktop or headset based microphone. Please check your hardware configuration and any reported errors during connection.

I have checked that the headset works by plugging it into another computer. The headset is USB, so I also tried various ports on the computer. I have also verified that it is the default recording device for the computer. When I select "Listen to this device" under the "Listen" tab of the device properties, I can hear my voice through the speakers. I have also checked everything I could find online about the system registry. I'm not sure what to look for, so I didn't change anything. With all that said, the next post will include DXDIAG info. I appreciate any suggestions that you can offer.

Thanks

Prog-Rocker 05-29-2018 08:12 AM

first, goto vent setup voice-binds-speech tabs and set the output/input devices to the actual name of the headset you're using.

set the hardware-mixer to 'none' and test. then try setting it to the same name as the input device.

clik the 'recording' button and disable all of the unused devices. rt-clik on a device and first enable both 'show' options. then select the unused devices and clik disconnect

--------------

also, can you elaborate further on what type of error you were getting when trying to install version 4 using a non-admin acct.

greenstone 05-29-2018 09:25 PM

Found Fix
 
"Failed to open sound input device. rc=-10, CreateCaptureBuffer failed. HR=E_FAIL. An undetermined error occurred"

I just received this error on my vent after I was checking services in Windows 10.

Service that caused the error:
Capability Access Manager
Service Provides facilities for managing UWP apps access to app capabilities as well as checking an app's access to specific app capabilities.
(Make sure the above service is automatic if you have it.)

Found out that by switching it off it turns off the "privacy settings" for the microphone and various other items in the newest Windows 10 patch.

Look under "setting">"privacy">"microphone", make sure "Allow apps to access your microphone" is turned on to fix most microphone issues with the newest windows 10 patch.

LeeroyBro 05-31-2018 08:18 AM

Quote:

Originally Posted by greenstone (Post 4643925)
"Failed to open sound input device. rc=-10, CreateCaptureBuffer failed. HR=E_FAIL. An undetermined error occurred"

I just received this error on my vent after I was checking services in Windows 10.

Service that caused the error:
Capability Access Manager
Service Provides facilities for managing UWP apps access to app capabilities as well as checking an app's access to specific app capabilities.
(Make sure the above service is automatic if you have it.)

Found out that by switching it off it turns off the "privacy settings" for the microphone and various other items in the newest Windows 10 patch.

Look under "setting">"privacy">"microphone", make sure "Allow apps to access your microphone" is turned on to fix most microphone issues with the newest windows 10 patch.

That fixed it. Thank you!


All times are GMT -5. The time now is 02:57 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.