Bc2000 (for the BCF2000 & BCR2000)

Hello

It works !!

Thank you very much 

Greets

Moroe

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "moroeat" <moroe@> wrote:
> > The gate time can be adjusted from 1 to 1600
> > 
> > I have monitored the output of the dx200 editor with midiox and
> > noticed that the dx200 editor sends 2 sysex strings per value (for the
> > gate time):
> > 
> > F0 43 10 62 10 40 26 val F7    9bytes        
> > counts from 00 to 7F and restarts then with 00.
> > 
> > F0 43 10 62 10 40 46 val F7    9bytes       
> > At start the value stands on 00 and counts one value up (up to 07)
> > every time after the first sysex string restarts at 00.
> > 
> > Is it possible to realise this with one knob of the bcr2000 ?
> > If yes, how can i do this ?
> > 
> > Please forgive my bad english
> > Answers in german would be preferred - but also in english :-)
> 
> Mein Deutsch ist nicht mehr was es einst gewesen ist, en
> waarschijnlijk heb je wat moeite met mijn Nederlands, so I'll stick to
> English, also for the benefit of other people in the group...
> 
> First of all I must say that I don't fully understand the protocol
> used by the DX200:
> 
> From your description of the DX200's output, I would think that the 
> DX200's first message sends the "low" byte (LSB) (from 0 to 127) and
> the second message the "high" byte (MSB) (from 0 to 7). The total gate
> time should then be calculated as LSB + 128*MSB. However, that doesn't
> quite seem to fit the fact that the second value is maximally 7,
> because 7*128 is only 896, so I can't immediately see how that would
> map to 1600.
> 
> However, if we assume that the encoding DOES work as LSB + MSB, you
> can assign the two messages to a single encoder via two ".tx" messages 
> ("custom output lines" in BC Manager's terminology):
> 
> .tx $F0 $43 $10 $62 $10 $40 $26 val0.6 $F7
> .tx $F0 $43 $10 $62 $10 $40 $46 val7.13 $F7
> 
> (You COULD put both MIDI messages in ONE ".tx" line, but then the BCR 
> would output additional, nonsensical MIDI data, so you'd better avoid
> that.)
> 
> See "BC MIDI Implementation.pdf" for further details. (In particular, 
> see the "Data Specifier" section.)
> 
> Mark.
>