The program crashed randomly on me, and after stopping BitBridge and relaunching Sonar X1 Producer, I get a message saying that there are no devices detected for my interface (ASIO) I have checked and the SD-50 was functioning just fine with other programs, but there doesn't seem to be a way to force Sonar X1 to rescan for the SD-50 that is connected to my PC. The only way to regain the use of SD-50 with Sonar X1 producer would be to reboot the PC. This is impractical, and I would like a better solution.

Is X1d applied? What OS are you on?

 
Hi there
 
I've had exactly the same problem with my Line 6 Toneport USB interface, and the only way I can sometimes get SONAR to recognise it again without rebooting my PC is to unplug the USB lead for a few seconds and then plug it back in again.
 
Even this doesn't always work, and I've tried it with SONAR open and closed before now, and a reboot is the only way to get back to work.
 
I've also tried changing from ASIO to WDM drivers to force SONAR to run the Wave Profiler. Again, sometimes this works and I can then switch back to ASIO, and sometimes it doesn't. I don't bother with this anymore as it's generally quicker to reboot my PC anyway.
 
Sorry I can't be of any further help than suggesting you try unplugging the USB lead, and I'll be interested myself to see if anyone comes up with a foolproof way to rectify this.
 
 

The obvious questions first :
 
Are you running it using a mains power supply as against USB power supply (or batteries) ? Mains would be the way to go, using a transformer/wallwart
 
Have you tried plugging it into a different USB port ? This will force a driver re-installation.
 
Have you updated the SD50 drivers, if there are any ? If there are updated drivers, delete the older ones first then install the newer ones BEFORE plugging in the SD50 (or Line 6)
 
I have an SD20 and its a cantackerous bar-steward at the best of times, but the method below worked for me and for the last 12 months or so, no problems.
 
Try deleting the drivers, deleting the USB port (or ports if you're felling brave) in the Device Manager then rebooting and letting Windows re-install a fresh set of drivers (before you re-plug in the SD50 or Line 6). But (yes, there's always a but, you may have to re-install all your USB drivers by this method, but its worth a try and worked for me.
 
Good luck to both of you,
 
Cheers,
Jerry

I occasionally have this issue with my Presonus AudioBox 1818 VSL audio interface, and it sometimes hiccups and loses touch with Windows altogether, even though the interface displays the blue light that tells me everything is OK.
 
I power cycle the interface, and even that sometimes does not work, as the interface comes back to life with screeching white noise.  I found through trial and error that going into the interface UI and changing the settings from one sample rate to another, that it somehow regains its sanity.
 
The point is that sometimes these things happen to different interfaces for different reasons, but that rebooting and/or an interface power cycle usually fixes things, and that since for me this all happens whether or not Sonar is running means that at least for me Sonar itself is not the culprit.
 
Anyways, you could check for driver updates, OR try using one PRIOR version of the drivers, OR try powering the interface down/up as choices.  (since you don't like the reboot option).
 
Bob Bone
 

JoanMichele
The program crashed randomly on me, and after stopping BitBridge and relaunching Sonar X1 Producer, I get a message saying that there are no devices detected for my interface (ASIO) I have checked and the SD-50 was functioning just fine with other programs, but there doesn't seem to be a way to force Sonar X1 to rescan for the SD-50 that is connected to my PC. The only way to regain the use of SD-50 with Sonar X1 producer would be to reboot the PC. This is impractical, and I would like a better solution.

You can try switching ASIO buffer size or sample-rate... but that may not resolve the issue.
In that case, if cycling the power of the SD50 (with audio applications closed) doesn't resolve the issue, the only option you really have is to restart the machine.