How to control CC's (and delete these controls) in Cubase

2 posts / 0 new
Last post
ZeroZero
ZeroZero's picture
How to control CC's (and delete these controls) in Cubase

Hi Newbie here,

Bit of a tech phobe too. :(

I just purchased a BCF 2000 with the hope of riding faders controlling CC's such as CC1 CC11 etc in Cubase. I want to be able to write into a track by moving the mechanical faders, and then read out the positions of these faders back into the BCF. I want it so that if I swap to another track in Cubase, I can still control the same parameters. This way I set up the BCF to commonly used CCs.

Read the manual, but it was not really directed at doing this.

I have set up my BCF in Cubase, and it is reading both ways I think. There is some residual programming from a previous owner that is working. I tried to get the BCF to work and got it to record a lane of volume into Cubase, but it also recordinged about eight lanes of garbage that I did not want, into other controller lanes. I dont really know why. I currently also have two faders (3 & 4) responding to volume.

 

If someone can please walk me through the process, for say CC11 I can probably work it out from there.

thank you.

 

Z

Mark van den Berg
Mark van den Berg's picture

Since I don't have Cubase, I can't help you with the Cubase side of your setup, so all I can do is give you some tips about the BCF:

Obviously there are always two sides to any type of communication between two devices, in this case your BCF and Cubase.
To analyze and fix your problems, you should look at both sides: first make sure that the sender (primarily your BCF) sends exactly what it should, then make sure that the receiver (primarily Cubase) responds the way you want it to respond.

There is some residual programming from a previous owner that is working. I tried to get the BCF to work and got it to record a lane of volume into Cubase, but it also recordinged about eight lanes of garbage that I did not want, into other controller lanes. I dont really know why. I currently also have two faders (3 & 4) responding to volume.

Assuming that you are using the BCF in standard B-Control mode (i.e. not in some Mackie emulation mode), the BCF's 32 programmable presets come into play.
What you're reporting here suggests that you're using one of these presets (the BCF display should specify this number: "P-nn"), and that this "residual" preset has been set up in a way that doesn't quite do what you want. (Alternatively there could be a hardware problem in the BCF, but let's not immediately think the worst.)
One way to get to grips with things is this:

  1. Download Factory_Presets_BCF.zip from the "Factory presets" folder in the B-Control user files section of this website.
  2. Extract the file bcf_FACTORY_PRESETS.syx from Factory_Presets_BCF.zip.
  3. Start BC Manager.
  4. In the B-Controls window, open bcf_FACTORY_PRESETS.syx via File -> Open.
  5. Send the preset(s) of your choice to your BCF. At the very least you should send preset 1 ("all controls"), which consists of only CC definitions, because that's the one you can use to test things (as described below). But in fact it may be an idea to send all 8 Behringer presets, or even all 32, to ensure presets 9-32 are cleared.
  6. Any problem with multiple BCF elements being connected to the same CC should now have been fixed. So now you can test whether there's still some problem with Cubase: on the BCF, select preset 1, and start pressing buttons, turning encoders and pushing faders, and see how Cubase reacts. (Tip: BC Manager's layout window will show you exactly which CC is under which button/encoder/fader.) If you still get these garbage lanes, it's probably a Cubase problem.
  7. In Behringer's preset 1, the faders use CC 81-88, which is not what you want, but BC Manager allows you to assign CC's to any element easily. It's probably best to leave Behringer's preset 1 alone so you can always return to it for testing purposes, but it should be easy to create your own preset with CC's from scratch.

Hope this helps,
   Mark.