You can do this by using the appropriate installer for the device. If the device is not yet connected, install the device-specific driver first. The problem may not occur if the device is connected to a different USB port. Method 2Ĭonnect the device to a different USB port. In step 2, don't select the Delete the driver software for this device check box. Select and hold (or double-click) the name of the device, and then select Uninstall.To fix this problem, use one of the following methods. Because the new driver does not support the WaveRT port, the system cannot access the driver. Therefore, the operating system assumes that the new driver also supports the WaveRT port. When the device-specific driver replaces the default driver, the device interface that is created by usbaudio2.sys is still used because the reference strings overlap. However, both drivers use the "wave" reference string when the device interface is registered. This "audio not playing" problem occurs because the default USB audio 2.0 driver (usbaudio2.sys) uses the WaveRT port for operation but the device-specific driver does not. Both the Windows Audio and the Windows Audio End Point Builder services must be running for audio to work correctly. When you select the icon, you receive the following message:Īudio services not responding. The speaker icon on the task bar is marked with an X mark. In this scenario, the device cannot be used, and the computer does not have sound. The downloaded device driver replaces the usbaudio2.sys driver.
Windows then downloads the device-specific driver from Windows Update.The operating system detects the device and loads the standard USB audio 2.0 driver (usbaudio2.sys).You connect a Universal Serial Bus (USB) audio device, such as an audio adapter or USB digital-to-analog converter (DAC), to a Windows 10 Version 1703-based computer for the first time.Now it shows 4 channels: PCM, PCM Capture Source(No volume slider, toggles from Mic to Line), Line, and Mic Capture. USB PnP Sound Device at usb-0000:07:00.0-1.4.1, full sĪnother anomaly is alsamixer used to show Capture & Playback channels(It has a 1/8" headphone jack integrated) cat /proc/asound/cardsĤ : USB-Audio - USB PnP Sound DeviceĬ-Media Electronics Inc. The microphone still works, but it's upsetting to not know why this has happened. Usually a simple reboot would make all well, but this time upon reboot the microphone showed up as USB PnP Sound Device instead of it's proper name. On certain occasions with JACK becoming unresponsive the microphone would be unable to start with JACK, but would disappear from PAVUcontrol's configuration tab. I produce content for Youtube with OBS and use JACK with the microphone but keep Pulseaudio running for everything else. I've been using this device for over a year, it's a Audio Technica AT2020-USB+ and until recently has always displayed as such.
0 kommentar(er)
