Bc2000 (for the BCF2000 & BCR2000)

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
After entering the sysex string using the model definition file, I can edit the sysex string manually at the custom output tab and ad the needed bytes.  But I would like to put together a model file to be able to share and for easily setting up my own BC templates.

I created the alpha juno file that is now included with the BC manager.  I did not run into any troubles there.  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

Thanks for any help.

--- 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.

Exactly what I want.  Thank you for the super fast reply.  I tried putting them in the manufacture ID, but as you said it was not supported.

Been lots of arithmetic fun creating multiple tempo controller items for the def file.  The for the MD you take the tempo multiple by 24, translate to 14 digit binary, then the 1st and last 7 digits into 2 two-digit hex numbers.

I will use the 2.4.0 beta.  I will email you the completed model def file.  Hopefully in time for the official release.  Maybe I'll write in the parameters for the UW model as well even though I only have the non-sampling version.  I'll take a look I think there are only a few line to add.  

Take Care,
Bob

--- In bc2000@yahoogroups.com, "Mark v.d. Berg" <markwinvdb@...> wrote:

>
> --- 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.
>

--- In bc2000@yahoogroups.com, "bobsvitilla" <bobsvitilla@...> wrote:
> I will email you the completed model def file.  Hopefully in time for the official release.

Got it! You're pretty quick as well...!

> Maybe I'll write in the parameters for the UW model as well even though I only have the non-sampling version.  I'll take a look I think there are only a few line to add.

Semi-officially I'm on vacation until August 18, so probably BC Manager 2.4.0 will be released in the week after that.
So you (and everybody else) have at least until then for any other SysEx definition files or feature requests.

Mark.