JWalsh - I tried to explain this "USB-MIDI" issue in another post. It's like you have limited number of devices (driverd)  that can be "virtually" binded to one USB port, and to all the ports in general.

If you change USB port where your device is connected, system installs drivers again - to NEW USB PORT, and don't delete old binding. So it's easy to make system "full".
I had some issues with it, my friends too and the best (and only) way was this small utility from KORG. It makes something with registry maybe, I don't really know and I don't care - because it works!

And thanks to this util you can see even "Strange" things like your grapgic card with HDMI output can block some "virtual" USB ports with its audio drivers.
This is another issue and as far as you don't use HDMI audio output it's good to make ANY HDMI audio outs INACTIVE in Windows System Manager.

Another thing - in System Manager too - is going to USB ports and turn off energy saving on all the ports.

In a fact it's basic system optimalisation, but you vcan do it by yourself with no danger of malfunctions.

Anderton


This is reaching waaaaaaay back into the memory banks, but I seem to recall the BCF2000 had an affinity for the USB port in which it was first installed. If I tried to use it with a different port, it wouldn't work. Might have been an XP thing, though...

I didn't read this whole thread - so maybe this was covered -- but I had to make sure "Sysex" was turned on in the options for my BCF to work - and had to load a project.


The sysex was the trick for me basically. I had it turned off previously.

I never heard of it - where you turn on or off? in SONAR?

Cheers Billy, that sounded worth a go, but when I checked Sysex was already enabled in my Sonar Preferences. I assume that's where you meant to turn it on, rather than somewhere on the device itself?

It's always possible you have a defective unit but I don't think it's the case. So far our best assumption were the driver but after all the testing you did I don't think so anymore. I'm now pretty sure that it is just Sonar that is stuck on an invalid state about your BCF2000 driver. I'm not sure how or where but Sonar keeps track of those drivers which allows it to warn you if they disappear or reappear (like shuting down the unit while Sonar is running). So to prove it I messed around with my config and the BCF2000 until I could reproduce your problem. Which I was able to do eventually: have a"Mackie Control" surface defined with a BCF2000 driver as IN and OUT but stuck in "connecting" mode with "ncso" on the display of the BCF2000. I'm not entirely sure how you force Sonar to reset the state but here's something I'd like you to try.
 

1. Create a new project. Delete all control surfaces, save it and exit Sonar.
2. Restart Sonar. Make sure the BCF2000 drivers are active and checked in MIDI devices. Then add a "Mackie Control" (make sure it's not the C4 or XT one) with BCF2000 as IN and OUT. In all likeliness you should get stuck in Connecting mode as usual. Save the project and exit Sonar.
3. Restart Sonar. If it does not connect then make sure the BCF2000 drivers are still active and checked, and make sure the surface still has BCF2000 as IN and OUT. Again save the project and exit Sonar.
4. Restart Sonar and I'm willing to bet that this time it will connect and your BCF2000 will switch to track mode.

Good luck!
 

You're welcome!
 
Well in reality I never turn my BCFs off so it is possible the same situation exists with everybody
 
I noted that when Sonar is running, if you turn the BCF off, it will prompt you to reassign the surface. I always answer NO in order to maintain the existing config valid. I have a feeling if you answer YES that it might be one way of creating your situation. In my case if I turn the BCF on right away, within 20 or 30 sec. Sonar will prompt again and ask if it should add the new found driver. As soon as I answer YES (or OK maybe?) then it connects right away and the BCF goes in track mode.
 
FBB mentioned it at some point, there is definitely a sequence in play here. I know for sure that the BCF has to be ON before you start Sonar and the saved Control Surface config has to be valid because Sonar initialize all Control Surfaces before you even open a project. If Sonar detects anything wrong at that stage it will likely flag the config and maybe even the driver as faulty and I'm not sure there is a way to reset it without a restart. Now I agree that it does not explain why you end up needing that many restart to get a complete reset.
 
Let us know if you find a better way to fix it.

yup - it ahould be there. Install, then go to folder in START menu, choose icon described "uninstall KORG USB-MIDI controller" - or something like this. Launch it, then in program options choose to show all the drivers. Next - check those failed, broken or unneccesarry. And uninstall them............... after rebooting computer you can install your controller drivers once again. BTW - CASE WITH BCF - sometimes after turning it on and launching Sonar - Sonar don't see BCF - it's because SOMETIMES in system - BCF canges it's name (or system changes BCR2000 sescription). Sonar is silly and doens't recognise controller under new or modified name.