Hi,
I've installed a US-366 on my 64 bit Windows 7 system. No problems with it once I get it up and running. The problem is that it fails to start up properly when I launch Windows, whether it's from bootup or when I log back in.
The power lights (red 48V, and blue USB) flash on and off continuously and there's a clicking sound in the headphones. I can unplug the USB cable, wait for a few seconds, plug it back in, and it will usually work fine.
I have uninstalled the drivers several times. Have downloaded and installed the latest ones. Have searched the registry and deleted any references to it, before reinstalling. I'm stumped. It's something to do with the way it's trying to launch itself when Windows starts, and I just can't seem to find the source. I've done troubleshooting in Windows Device Manager, checked all the hardware drivers.
FWIW, I'm using Sonar Producer, but it's not the audio software that's causing the problem. Once working, it works with Sonar, Reaper, Windows native audio apps, online audio, etc. It's just the startup that has me baffled. Could it be the 366's control panel software? I've tried every different setting I can think of there, but that makes no difference, either. I'm thinking that maybe it's the 366 Control Panel program that's causing it.
Thoughts? thanks,
--john
I've installed a US-366 on my 64 bit Windows 7 system. No problems with it once I get it up and running. The problem is that it fails to start up properly when I launch Windows, whether it's from bootup or when I log back in.
The power lights (red 48V, and blue USB) flash on and off continuously and there's a clicking sound in the headphones. I can unplug the USB cable, wait for a few seconds, plug it back in, and it will usually work fine.
I have uninstalled the drivers several times. Have downloaded and installed the latest ones. Have searched the registry and deleted any references to it, before reinstalling. I'm stumped. It's something to do with the way it's trying to launch itself when Windows starts, and I just can't seem to find the source. I've done troubleshooting in Windows Device Manager, checked all the hardware drivers.
FWIW, I'm using Sonar Producer, but it's not the audio software that's causing the problem. Once working, it works with Sonar, Reaper, Windows native audio apps, online audio, etc. It's just the startup that has me baffled. Could it be the 366's control panel software? I've tried every different setting I can think of there, but that makes no difference, either. I'm thinking that maybe it's the 366 Control Panel program that's causing it.
Thoughts? thanks,
--john