Message
Re: BCF2000 feedback paramaters / communications / USB
2011-08-20 by Royce
> I have just started using the BCF2000 - very new to it - to control a custom video and audio mixer I have developed in Delphi.
>
> I have the BCF2000 in USB1 mode, and am receiving and parsing fader and button movements/toggles - all good so far - faders in the BCF controlling on-screen faders and buttons in the application.
>
> I would like the BCF to be able to reflect changes in settings of the controls in the software - so if I move a fader on-screen I would like to have the fader on the BCF move to reflect the new value.
>
> From reading the documentation I believe I need to use feedback parameters, however I am having difficulty really understanding what I need to send back to the BCF.
>
> For example if I want to set fader 1 to a value of e.g. 50 what format command do I send to the device? Where could I go to get examples of how to set fader, button, rotary control settings. I want to start simple and then move onto working with presets etc if possible.
Get Mark's editor and his great Behringer Control Language ( BCL) spec from his website or, as a programmer, you prefer to write the BCL out you can use my editor in the files section.
There is an overview of what the BC can do in the SecretBC.pdf in the "Document" file section
You can use an emmulation mode and use those particular midi messages. The info of how the various mixers work is available on the web.
If you want to program the BCF you can use simple Midi messages.
To have controls bi-directional you obviously need to have your software recognize and send Midi messages.
For the BC to recognise data and reset it values, the types of Midi messages are limited, but that shouldn't affect what you need.
To start you off just use Midi Continuous Controller (CC) messages.
For Midi info
http://www.somascape.org/midi/tech/spec.html
As a programmer I assume you know Hex and in the BCL a hex number is shown with '$'
$B0 100 val
CC 100 on channel 1 - the val is a number between 0 and 127 and so your software fader using this has a resolution of 127
You can improve on this 7bit to 14bit, but we'll start simply.
The BCL must use an .easypar statement. ie simple BC programming, not Mark's 'Learn' in his editor which uses .tx statements
BCL example to set your Faders to CC100 to CC107
$rev F1
$preset ; Preset data
.name 'CCs on Chan 1'
.snapshot off
.request off
.egroups 4
.fkeys on
.lock off
.init
$fader 1 ; Fader 1
.easypar CC 01 100 0 127 absolute
.showvalue on
.motor on
.override move
$fader 2 ; Fader 2
.easypar CC 01 101 0 127 absolute
.showvalue on
.motor on
.override move
$fader 3 ; Fader 3
.easypar CC 01 102 0 127 absolute
; .showvalue on
.motor on
.override move
$fader 4 ; Fader 4
.easypar CC 01 103 0 127 absolute
.showvalue on
.motor on
.override move
$fader 5 ; Fader 5
.easypar CC 01 104 0 127 absolute
.showvalue on
.motor on
.override move
$fader 6 ; Fader 6
.easypar CC 01 105 0 127 absolute
.showvalue on
.motor on
.override move
$fader 7 ; Fader 7
.easypar CC 01 106 0 127 absolute
.showvalue on
.motor on
.override move
$fader 8 ; Fader 8
.easypar CC 01 107 0 127 absolute
.showvalue on
.motor on
.override move
$end
All the best
Royce