--- In bc2000@yahoogroups.com, "omnipotent_apparatus" <vladi.dj@...> wrote:
> Today dusted it off plugged in and was unpleasantly surprised with
> inability of bc control to transfer data back to the unit. After a
> brief search on the www i found this group and Bc Manager. Fantastic
> so far. Changed one of the presets and sent it back to the unit via
> midi send - worked as a charm. Back to Ableton. In need for some more
> adjustments i quit Ableton started Bc Manager and accidently clicked
> in Bc Manager something that i don't even remember, at the same
> moment all the LEDs on the unit went off.
It might be that you selected/sent an empty preset, which might then cause the lights on the BCR to go off.
In such a situation, one way to check whether the CONNECTIONS to and from the BCR are still functional is to execute "Refresh connection status" from BC Manager.
> I thought it might be a
> good idea to restart the Bc Manager and the unit. After doing so the
> unit stoped transmitting any MIDI data(panic didn't help), all the
> presets were gone and when i start the Bc Manager i get following
> notification: "Error:Cannot start MIDI input device BCR2000[01].
> Handle being used simultaneously on another thread(eg callback]".
This seems to indicate that there was another program (or instance of BC Manager) that was indeed blocking the BCR's USB-based MIDI devices.
> What did i do wrong so that i can prevent future
> accidents of similar nature?
> How do i recover from this small disaster?
It's hard for me to say what exactly caused the problem.
You may have used the wrong order of switching the BCR and BC Manager off/on. The order should always be:
1. Switch on the BCR (and wait for the USB driver to be installed/started up by Windows).
2. Start BC Manager.
3. Exit BC Manager.
4. Switch off the BCR.
Performing (3) and (4) above in the wrong order may lead to all kinds of trouble concerning suspended USB-based MIDI devices (basically this is Windows' fault).
In general, you should never switch the BCR OFF, then ON again while ANY computer program is linked to the BCR's USB-based MIDI I/O devices: the "old" devices become invalid when you switch the BCR off, then when you switch it on again, Windows "creates" NEW devices, unrelated to the old ones, and the programs that were using the old ones are then left with these "ghost" devices that are completely dysfunctional.
By the way: you should use the latest version of BC Manager, i.e. 2.0.0, since it's by far the most robust as to these connection problems.
If the same problem occurs again, you may try to restart Windows itself: that will clear up any "hung" drivers/devices.
It MIGHT be due to a bug in BC Manager - so let me know if you find that a specific action consistently causes this problem.
Mark.
