• SONAR
  • Behringer BCF2000 and Sonar ? (p.3)
2014/04/04 16:44:04
Senn5
Glad to see someone is still using these. I pulled mine out of the closet to use for just some of the basics I know it was capable of. I used it before with sonar and never had any problems but NOT now...:(
 
I have it connected via USB, Sonar Producer x3 finds it and I have installed the usb to midi driver from the Behringer site.
I have booted the BCF in Sonar mode and set everything in sonar from directions. My problem is this:
Moving the faders and pan on screen moves the motorized faders and pans properly, BUT when I move the faders on the BCF its NOT controlling the faders or pan inside Sonar. When I touch any of the actual faders on BCF I can see the track hi-light in Sonar and the transport buttons on the BCF fully play and stop the daw properly.
Am I missing some additional settings in Sonar?  I connected it this way before with no problems talking back and forth, but I have tried everything and can't get the Faders or Pans on the actuall BCF to control the daw???
 
Any help would be much appreciated, and thanks in advance.
2014/04/04 17:19:13
daloopstar
See below. I jut got this response this morning the Behringer. 
 
Did you manage to set the BCF to the correct mode? Hold 4th button (not encoder) along from top left whilst powering up. MCso should now appear in the display. Select Mackie Control from the MIDI controller list in Sonar and you should be good to go. 
 
I am adding to make sure you pick the Mackie 1 controller. I picked the Mackie 4c by accident. Once I realized what i did and made the switch it all came together. The the faders in sonar x3 and the BCF 2000 were in sync. Let me know if this helps E.C.
2014/04/04 17:40:36
Senn5
Thanks for the heads-up daloopstar. I'll have to give that a try. I'm not at studio right now so will try tonight. When you say "Mackie 1" controller........ if memory serves me right, in the drop down menu it showed Mackie AND a Mackie 1. Do you happen to know what the difference is in these. I don't ever recall seeing a Mackie 4c in mine.
 
2014/04/04 17:48:12
daloopstar
You got me. i'm also not at the studios now. Pick one and see what happens. Good luck. E.C.
2014/04/06 20:06:09
Senn5
Finally solved!!!!!
I went into playback and recording preferences and turned on everything..... lol
Everything back to working as it should. Thanks for your input daloopstar.
 
2014/04/07 10:37:55
daloopstar
Great. Good luck and have fun. 
2014/04/09 20:10:55
stxx
MAJOR SHORTCOMING!!!  Faders are not touch sensitive so you cannot overwrite automation lanes already there!  When a fader is not moving, the data goes back to the original lane.  If you move a fader up to a new level and hold it, the hold is not registered.   If you google this, you will find it to be true.  I have one and that is a major bug for me so I am selling it
2014/04/09 23:31:40
Senn5
Not sure if this will help you, but faders "are" touch sensitive. From track view click on utilities and scroll to Mackie control -1.  On right hand side check off options:
1. Solo selects channel
2. Fader touch selects channel
3. Select highlights track
Click on layout...... configure twice and done.
Took me weeks to find out how to activate the touch sensitive, but all is working once I did this.
Hope this helps you out a bit.
 
2014/04/10 16:30:37
stxx
Sorry but that does not solve the issue.    Documentation all around the net as well as Behringer says these are not "touch sensitve"  which is different from having motorized faders.  The Behringer does not send midi information by just touching the fader.    Again. if you have a volume envelope already written in the track and you wish to ride the fader differently and overwrite it,  even with those settings checked, Sonar does not pick up where the fader is when it is stationary (with the track playing.  So if I raise the fader to a new level and hold it there, the held value does not record and the envelope drops back down to the previous value at the start.
2014/04/10 16:58:07
Noel Borthwick [Cakewalk]
stxx
MAJOR SHORTCOMING!!!  Faders are not touch sensitive so you cannot overwrite automation lanes already there!  When a fader is not moving, the data goes back to the original lane.  If you move a fader up to a new level and hold it, the hold is not registered.   If you google this, you will find it to be true.  I have one and that is a major bug for me so I am selling it



Have you tried using automation write mode Overwrite or latch in SONAR? Both these will write automation from the last touched fader position and not jump to the prior envelope when you release the fader.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account