Bc2000 (for the BCF2000 & BCR2000)

Heh, thanks for the quick replies yes. I fixed it up and it's working fine now. I actually didn't have much hope for this, because of the USB not working, so I gave up quickly.. But these things are built like a tank.

But I was mucking about with BC Manager and tried to come up with a sysex setup that works with my samplers knobs, I had a whole bunch of presets and was getting the hang of how the program worked, so I did a save of the preset I wanted to use and then a 'restart with default setup', so to thoroughly start a new. I probably did a send of the empty setups then?

Anyway all good now :)

Robert


--- In bc2000@yahoogroups.com, "Mark v.d. Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "zeitgeber24" <rbeenen@> wrote:
> > Thanks so much, I forgot about the USB modes U1-4.. I set it back to a MIDI mode and everything is working again. I don't know how I put it in that mode though, maybe BC Manager did that somehow?
> 
> Yes, that's possible:
> 
> In BC Manager, the Operating Mode setting is in the "Global setups" window.
> So if you haven't first loaded your BCF's global setup into BC Manager, BC Manager maintains its default, which is U-3,
> 
> BC Manager sends the Operating Mode to the BCF in 2 cases:
> 
> 1. You run MIDI => Send from the "Global setups" window.
> 
> 2. You run MIDI => "Send all data" from the "B-Controls" window.
> (This sends both the global settings and all 32 presets.)
> 
> I suspect the second scenario has occurred in your case.
> 
> I suppose that most people use the BCF/BCR in a U-mode, in which case this behavior isn't such a problem, but I admit that this behavior almost amounts to a "behind-your-back" operation.
> 
> So maybe I could have BC Manager display a warning whenever the user is about to send the Operating Mode - I'll think about it.
> 
> By the way: the idea is that the user hardly ever uses "Send all data", and instead uses "Send" from the Presets window to upload presets.
> 
> Sorry about the confusion if BC Manager was responsible for your problem. But at least we've managed to avoid real disaster, in the nick of time...
> 
> Mark.
>