Bc2000 (for the BCF2000 & BCR2000)

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
>