![]() After installation a new audio driver is present on your system as playback and recording device. I go to install and.the process repeats itself all over again (unknown error) The drivers simply will NOT install for me. 1- Extract all files in one folder (temporary folder) 2- Run Setup program in administrator mode (right click on exe to see the run as administrator) 3- Follow instruction : REBOOT after installation (mandatory). back to installer, it prompts me to uninstall again? So, I uninstall again, reboot, re-run the installer, and. Open WinX menu by holding Windows and X keys together, and then click Programs and Features. Once I've rebooted, I check the device manager, and now the same device is in error (Yellow Triangle) - So, I re-run the installer, uninstall, reboot. After installing the VB-CABLE driver, a new playback device appears in the audio device list and can be set as default device. Im trying to get VB6 installed on Win10, apparently theres a wizard from Giorgio Brausi, Visual Basic/Studio 6 installer but the web site seems to have gone. So I assume it's a false reading, and reboot. It sits for literally what seems 30 minutes (But it's probably more like 5) and then gives me an "unknown error." BUT In the audio devices in my device manager, I see a brand new Device Driver. ![]() Do you stream and your viewers can hear the mus. Unzipped Cable into folder, on my desktop, ran the 圆4 Installer in Administrator Mode. Have you heard of VB-Cable VB-Cable is a virtual audio device that can split your audio sources to channels. FANTASTICĭownloaded VB-Cable, and the Latest VoiceMeeter I *Have* to be able to mute out Mumble Comms from my stream for Eve Online for OpSec reasons.ĭid some research, found that VoiceMeeter/VB Cable would take care of this nicely for me. Active Directory, WSUS, RRAS, DFS, DNS, DHCP, GPO, WLAN, WAN, Site to Site / SSL VPN, ADFS, Print Servers, Exchange Servers. So, I have a mission critical application for my LIve Streaming. Network Administrator, MS Windows /2016/2012/2008/2003.
0 Comments
Leave a Reply. |