Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Message

Re: Can the BCR2000 ouput sysex program change messages?

2007-05-30 by rpcfender


> Does this apply to the BCF as well?
I've not used a BCF, but from what I have read the only difference is the lower 24 encoders on the BCR are replaced by the 8 motorised faders.
The script uses the command $fader and then uses most of the same encoder functions plus some special ones.
The first line of the script in the BCF is different. It should be $rev F1 where the BCR is $rev R1
>
> If so, what is the best current editor for the BCF?

Mine of course :-)
If you want to do simple things the Birdie editor is better to edit a patch, but there is not library function like the java one has.
Mine is, perhaps a bit more complex, in as much as you don't point-and-select but have to write the script.
But you can cut/copy and paste.
You can load a sysex file and the program reduces it to just the script so you can load one in and modify it. It will also show how the script works.
After its loaded you edit it like any other text file.

I didn't put in a way to get the sysex from the BCR as there is a bug in the BCR firmware. The BCR reads the checksum command correctly but when it sends back it fails to put it in.

You will need to use MidiOx or a sequencer to get the Sysex dump from your unit if you want a starting point (or Behringer has a large collection of them on the BCR/BCF download web page). I might include away to download a sysex dump from the BCR in a later version if anyone is interested, but at the moment I don't need it.

As far as I am aware, the only sysex messages that the BCF/BCR use are request Software ID and request patch names (gives the names of the 32 internal patches) and of course the script line.
The script editor (also has both the software id and patch list request in it) simply takes lines from a text file and wraps each line in the sysex header and footer that the BCF or BCR needs.
So you can write anything. If there are errors the BCR just ignores it and flashes Err on the display

Version 1.1 of the BCR/BCF firmware added the increment argument in the easypar command. I don't think either the java or the Birdie editor has included this.
As a working musician I wanted to be able to take advantage of this and other firmware changes that may occur without me having to change a line of code. I'm basically lazy.

So for the BCF I should think that this would work

$rev F1
$fader 2
; .minmax 0 127
.default 1
.tx $F0 $41 $10 $00 $6B $12 $10 $00 $27 $07 val cks-1 $06 $F7
.showvalue on
$end

This is a sysex command for the Fantom X.
cks-1 is the checksum that works for Roland (that the BCR would not have put out if it sent the sysex dump back).

Hope this helps

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.