TL; DR: basically, if I want to use this audio interface as an external sound card -- an upgrade over the builtin -- I'm screwed?
First off, the software bundle installs a mixer, which helps itself as the default device on each boot. I don't like it at all, since the sound quality is horrible -- maybe because the mixer works strictly in 16/44.1. Definitely not an upgrade over HD Audio. I uninstall it. The sound of the "US 2x2" device itself is great, no problems with output.
The input is what drives me up a wall. When I boot the system -- windows device reports normal input. Once I join one of my voice chat apps -- the sound is gone. (Signal LED on the device keeps working fine though). Once I leave the voice app -- the sound is back. I have to plug it off and on again for it to keep working. Should I god forbid try to output something using exclusive mode -- I'm back at sq. 1, having to replug, even if I close the offending app and restart the services, etc, etc.
Recently I have learned that in the year of our Lord 2018 Microsoft has finally released an audiodriver for USB Class 2.0 audio devices. I decided to switch from Windows 8.1 to Windows 10 to give it a spin (and possibly ditch the TASCAM drivers altogether). As if. The driver doesn't even get up, bringing up outlandish claims like "This device cannot start. (Code 10) An invalid parameter was passed to a service or function. A feedback endpoint implemented by device <> is unusable because its bInterval value is not supported. Audio glitches might occur." Seems like "USB Class 2.0 - compliant" part in the advertising pamphlet isn't quite true eh?
I have contacted the support with my woes, and unsurprisingly, was not contacted back. Not much info on the internet either. Was I the only one who bought it with a broader purpose in mind? All in all, I'm pretty angry about this situation. I'm way past every return at this point, and all I want is not a glorified $150 paperweight.
First off, the software bundle installs a mixer, which helps itself as the default device on each boot. I don't like it at all, since the sound quality is horrible -- maybe because the mixer works strictly in 16/44.1. Definitely not an upgrade over HD Audio. I uninstall it. The sound of the "US 2x2" device itself is great, no problems with output.
The input is what drives me up a wall. When I boot the system -- windows device reports normal input. Once I join one of my voice chat apps -- the sound is gone. (Signal LED on the device keeps working fine though). Once I leave the voice app -- the sound is back. I have to plug it off and on again for it to keep working. Should I god forbid try to output something using exclusive mode -- I'm back at sq. 1, having to replug, even if I close the offending app and restart the services, etc, etc.
Recently I have learned that in the year of our Lord 2018 Microsoft has finally released an audiodriver for USB Class 2.0 audio devices. I decided to switch from Windows 8.1 to Windows 10 to give it a spin (and possibly ditch the TASCAM drivers altogether). As if. The driver doesn't even get up, bringing up outlandish claims like "This device cannot start. (Code 10) An invalid parameter was passed to a service or function. A feedback endpoint implemented by device <> is unusable because its bInterval value is not supported. Audio glitches might occur." Seems like "USB Class 2.0 - compliant" part in the advertising pamphlet isn't quite true eh?
I have contacted the support with my woes, and unsurprisingly, was not contacted back. Not much info on the internet either. Was I the only one who bought it with a broader purpose in mind? All in all, I'm pretty angry about this situation. I'm way past every return at this point, and all I want is not a glorified $150 paperweight.
