Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "bobsvitilla" <bobsvitilla@...> wrote:
> I am trying to create a SysEx model definition file for the MachineDrum.  
> I need 2 bytes between the start sysex command and the manufacture ID.  00 20

Aren't these 2 bytes PART of the manufacturer ID, formally speaking?
Behringer, for instance, has 00 20 32.

> The machine drum wants its sysex like the following:
> $f0 | SYSEX Start 
> $00 | Europe/USA ID 
> $20 | Europe ID 
> $3c | Elektron ESI ID 
> $02 | Machinedrum ID 
> $00 | Base channel (Padding)
> A complete SYSEX message looks like this: $f0,$00,$20,$3c,$02,$00,command,...,$f7

BC Manager's current preprocessor format doesn't support Manufacturer IDs consisting of multiple bytes.
You could cheat your way out of this as follows:

ManufacturerID=00
ModelName=...
ModelID=20 3C 02
DevicePosition=AfterModel

... but of course that would be a bit dirty.

Therefore I've now implemented multiple-byte Manufacturer IDs in the upcoming BC Manager 2.4.0.
The release version is scheduled for next month, but you can already download the beta 1 from my website:
http://home.kpn.nl/f2hmjvandenberg281/download/BC/BCMan240b1.zip
This is just the exe; basically you can put it in any folder you like, but perhaps your existing BC Manager program file is the easiest - the beta has a different filename, so shouldn't hamper your existing version.

In the SysEx definition file you should change the ProgramVersion field from "2.3.0" to "2.4.0" (at least in any definition file with a multiple-byte Manufacturer ID).
So you get something like:

ProgramVersion=2.4.0
ManufacturerName=...
ManufacturerID=00 20 3C
ModelName=...
ModelID=02
DevicePosition=AfterModel

Does this do what you want?

Mark.