Bc2000 (for the BCF2000 & BCR2000)

Just for information, if anyone is interested, I failed to program BCR to control OASYS PCI with sysex.
I used MIDIOX to observe what messages OASYS is sending out (tried several parameters in various OASYS synths) and it seemed like each controller/parameter did use all 4 bytes for representing its value.
Completely out of luck, what a pity!


Anyway, thanks to Royce for the try and the advice.

Kind regards

malichos.



--- In bc2000@yahoogroups.com, "Royce" <rpcfender@...> wrote:
>
> Hi
> the max BC controllers will output are 14bit data numbers.
> So if the OASYS uses 4 bytes (4 x 7 bit = 28bits) then you could be out of luck.
> 
> I suspect that not all off the parameters need 28bits so you could use 0's in the first numbers.
> 
> $F0 .. OASYS header ... parameter address ... 00 00 val7.13 val0.6 checksum? $F7
> 
> You can put the val terms where ever you want
> 
> $F0 .. OASYS header ... parameter address ... val0.6 val7.13  00 00 checksum? $F7
> 
> is OK.
> 
> Perhaps you could give a detailed example?
> 
> Best of luck
> 
> Royce
> 
> --- In bc2000@yahoogroups.com, "Dariusz" <dmaliszewski@> wrote:
> >
> > Hello everyone,
> > I am new here and looking for help in controlling KORG OASYS PCI dsp with BCR2000. I have been trying to use BC Manager as well as BCReditor to program encoders to control parameter values of any synth in my OASYS PCI, but no luck so far. The problem probabely lies in the sysex format OASYS PCI supports - each sysex message has 14 bytes and four of them stores parameter value. In BCmanager or BCReditor one can assign just 2-byte value for a parameter, or am I missing something?
> > Would anyone on the forum help me, maybe what I am trying to do is not possible to achieve?
> > I will appreciate any hint.
> > Thanks in advance.
> >
>