Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Thread

BCR2000 to use with KORG OASYS PCI

BCR2000 to use with KORG OASYS PCI

2010-02-25 by Dariusz

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.

Re: BCR2000 to use with KORG OASYS PCI

2010-02-25 by Royce

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:
Show quoted textHide quoted text
>
> 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.
>

Re: BCR2000 to use with KORG OASYS PCI

2010-02-25 by Dariusz

Hi rpcfender,
many thanks for such quick response. I think you may be right - indeed, there is a big chance that OASYS does use 2 bytes out of 4 for the parameter value, so addressing just 2 bytes could be the clue. I did not think of it such way and it's so simple!
I will give it a try this night and return with results.

Thanks again and

God Bless You

Darek




--- In bc2000@yahoogroups.com, "Royce" <rpcfender@...> wrote:
Show quoted textHide quoted text
>
> 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
>

Re: BCR2000 to use with KORG OASYS PCI

2010-03-02 by Dariusz

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:
Show quoted textHide quoted text
>
> 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.
> >
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.