Bc2000 (for the BCF2000 & BCR2000)

Hi,

its me again.

I have managed to convert text to sysex and now I am able to create a nice, really nice controller for Oberheim Matrix 1000.
Shall post it in the files as soon as I have it finished.
I just have to think of where to put what button .. i have a lot of coffee so it shall be ok.

My next plan was to make a controller for my Crumar Bit01 

http://www.vintagesynth.com/misc/bit01.php synth.

I got it basically for free (20 eur they did not know in the shop what it is) and it has very limited routing but it is an beautiful sounding instrument .

I would love to be able to use BCR 2000 to control it .

The oberheim was easy to figure out as i just spied on the soft editors midi out and that is how I found the sysex.

The Crumar does not have midi out ..and the only editor ( midi quest) sends this as sysex for cutoff to midi monitor:

F0 25 10 07 4A 00 00 00  00 00 00 00 00 00 00 00
08 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 F7

it looks big....I don't know much about sysex but this is big.

How do I put this in this form :

.tx  $F0 $25 $20 $10 $28 val $F7 (this is from the matrix 1000)

There is a manual as well with the sysex implementation (from page 30) which I do not understand.

http://www.pierregander.com/bit/bit99_manual/index.html

http://www.pierregander.com/bit/bit99_manual/CrumarBit99Manual.pdf

The bit99 and bit01 are same.

My question .... can somebody help me by just looking at the manual and maybe send me the code for cutoff as I think I can figure the rest.

I know it is to much to ask ... but I give coffee in Geneva..good coffee.


yours rastko

On 28 Apr 2009, at 09:55, lazichi wrote:

> I got it basically for free (20 eur they did not know in the shop  
> what it is)

wow... congratulations!

 From the manual it looks like your message is a 'single program dump'  
which has 74 bytes of data. Was the cutoff set to 0 when the message  
was sent?

It seems that the way to send parameters to the synth is through a  
full program dump, which would kinda suck if you're hoping to control  
it real time with the BCR.

If I understand it correctly, each parameter has a position in the  
program data and takes up two bytes. How the two-byte value is  
constructed is detailed on page 32: least significant 4 bits in the  
lower part of the first byte, and most significant 4 bits in the lower  
part of the second byte. That's one binary representation I've never  
seen before.
Given a valid value 0 <= x <= 256, the first byte is x & 0x0f and the  
second byte is( x >> 4) & 0x0f
If this seems too complicated try changing just the second (most  
significant) byte with values between 0 and 0x0f (decimal 15) for  
coarse grained control.

So to change e.g. the cutoff frequency you need to find the right byte  
pair in the sysex...
It says byte 28, which I take to be the two bytes marked LL and MM  
below, counting from the first byte after '4a':

F0 25 10 07 4A 00 00 00  00 00 00 00 00 00 00 00
08 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 LL MM 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 F7

The table on p.32 also has a 'parameter' column - I don't understand  
what that means. If you're really lucky it is perhaps the CC number of  
that parameter. Try it!

In any case, good luck and happy experimenting,

/m

Thank you for your answer,

I did not have much time to try it but I think that the bit 1 has some kind of buffer so real time control via sysex is actually imposible.

They manage to go over the buffer thing with the complete program dump .

This is what I think and I know very little.

Still I shall use your info to at least try to make the non real time editor....

> The table on p.32 also has a 'parameter' column - I don't understand 

the parameter control is the internal thing.
you dial in the number and then with plus or minus you can change the parameters of the synth.

that works real time of course.

only if they have at lest made a knob...

but anyways the editing in this way is not so complicated .....I think still it is definitely forth the money and much more.

As for the matrix 1000 I shall start a new topic.
Had played a lot with it yesterday and it is WOW but I get this panic attacks from the matrix , they can be solved with a sysex string but the string is to long for the BCR ... anyways more about that soon.

have a nice day 

r

--- In bc2000@yahoogroups.com, Martin Klang <mars@...> wrote:

>
> 
> On 28 Apr 2009, at 09:55, lazichi wrote:
> 
> > I got it basically for free (20 eur they did not know in the shop  
> > what it is)
> 
> wow... congratulations!
> 
>  From the manual it looks like your message is a 'single program dump'  
> which has 74 bytes of data. Was the cutoff set to 0 when the message  
> was sent?
> 
> It seems that the way to send parameters to the synth is through a  
> full program dump, which would kinda suck if you're hoping to control  
> it real time with the BCR.
> 
> If I understand it correctly, each parameter has a position in the  
> program data and takes up two bytes. How the two-byte value is  
> constructed is detailed on page 32: least significant 4 bits in the  
> lower part of the first byte, and most significant 4 bits in the lower  
> part of the second byte. That's one binary representation I've never  
> seen before.
> Given a valid value 0 <= x <= 256, the first byte is x & 0x0f and the  
> second byte is( x >> 4) & 0x0f
> If this seems too complicated try changing just the second (most  
> significant) byte with values between 0 and 0x0f (decimal 15) for  
> coarse grained control.
> 
> So to change e.g. the cutoff frequency you need to find the right byte  
> pair in the sysex...
> It says byte 28, which I take to be the two bytes marked LL and MM  
> below, counting from the first byte after '4a':
> 
> F0 25 10 07 4A 00 00 00  00 00 00 00 00 00 00 00
> 08 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> 00 LL MM 00 00 00 00 00  00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 F7
> 
> The table on p.32 also has a 'parameter' column - I don't understand  
> what that means. If you're really lucky it is perhaps the CC number of  
> that parameter. Try it!
> 
> In any case, good luck and happy experimenting,
> 
> /m
>