Hi!
 
I'm being an idiot here and can't figure out what I'm doing wrong ... maybe one of you can help me real quick.
 
I dug out an old BCF2000 that I used years ago (properly stored away so I doubt it's broken), just wanted to check on something quickly using the Mackie control surface option. I downloaded and installed the latest BCF2000 driver for win7, but no matter how I select the ports, the unit remains unresponsive (i.e. there is a blinking LED showing constant MIDI traffic on either MIDI port A or B, but whenever I move faders, they snap back to zero) and Sonar does not receive any MIDI signal that would move faders ... BCF is in "MCSo" mode (as I used to have when it was working years ago), firmware is 1.10
 
EDIT:  I belive this is a connection issue i.e. when Sonar starts it says "Connecting ..." in the ACT toolbar module. I can intercept/record the MIDI messages that go out - it some sysex string "$F0 $00 $00 $66 $14 $1B $54 $5A $42 $47 $2D $41 $2D $F7" which repeats about 10 times per second ... but never gets across this conneciton issue

still not working ...
 
some more info:

• BCF2000 is in U3 mode (as it always was)
• BCF2000 is also in "MCSo" emulation mode (as it always was)
• I can use the BC Manager software and it picks up the device, showing it connected to "BCF2000 port1"
• BC Manager input meters pick up fader movement on the BCF2000, but it does not arrive in Sonar
• with Sonar and BCF2000 configured as "Mackie Control" on "BCF2000 port1" I can see constant "traffic" on the SysEx channel of the BC Manager input meter

weird ...
 
Sonar keeps sending "F0 00 00 66 14 1B 54 5A 42 47 2D 41 2D F7" which is probably some sort of connection message as in the ACT controller module it keeps showing "connecting..."

I used a BCF2000 for a long time (recently replaced it with a new X-Touch).  I don't recall installing any drivers for Win 7 (or now Win 10) as it was "plug and play" if I remember correctly in Win 7. 
 
Sounds like its not in Mackie mode.  I forget, but I think you have to hold button 4 down while powering on to get it in Mackie mode.  Mine was set initially when I got it and I never had to set it again.  (Azlow will know).   I didn't use ACT either, I used Mackie in the Sonar setup.

how are you connecting the surface to sonar ?
through usb or midi cable ?
sorry not to familiar with the BCF2000
but I do run Mackie control myself.

RehabRob
weird ...
 
Sonar keeps sending "F0 00 00 66 14 1B 54 5A 42 47 2D 41 2D F7" which is probably some sort of connection message as in the ACT controller module it keeps showing "connecting..."

Till BCF respond properly on that message, nothing will work correctly. But you mention that BCF does not send anything at all. So check that (after MackieController plug-in removed) that you can record MIDI from BCF. That will be good start, which avoid other potentially problematic points.

Thanks, guys.
 

chuckebaby
how are you connecting the surface to sonar ?
through usb or midi cable ?

I do connect via USB.
 
Strange things continue happening. Just hooked it up to the DAW PC that I had it connected back in the days and it worked like charm (so it's not the BCF); however, that new DAW PC (same OS, same Sonar version, same win 7 updates, ...) does not like it ...
 
So it is possibly a driver or USB port issue ... I will try again tomorrow or later in the week and let you know

Removed

I need to revive & bump this thread as this problem still exists ...

• Meanwhile migrated to win10, same issue persists
• BCF is picked up OK by BC manager software, which shows (like the the BCF display) that it's in MCSo mode
• When trying to use it in Sonar it does not get passed the "Connecting..." message (see above)
• It's not a faulty unit as it works fine with the other DAW
• It's not a driver issue either as it has identical problems when connected via MIDI instead of USB
• MackieControll.dll is the same as on the other DAW where it works

What else could I check / try???

well, after testing the BCF unit on a 3rd PC (where it worked right away) I went back to the troublemaker PC (where it did not work, of course) ... so I messed with "Playback and Recording" settings for SysEx and now it does work (however, I now can use any settings for SysEx and not deliberately break it) ...
 
Really weird, like some setting was stuck and had to be overwritten by whatever I did ... hmmm ...