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

DSI mopho cutoff 164 not 127 and BCR2000

DSI mopho cutoff 164 not 127 and BCR2000

2009-02-28 by organ.symphony

I've seen bits of information about this now and then but nothing
definitive and nothing that makes me say "I know the answer now".
Basically on the Dave Smith Instruments Mopho the cutoff parameter
goes from 0-164 (all the other parameters are the standard 0-127) and
i am wondering if it is possible to set one of the knobs on a BCR2000
to transmit a CC with a resolution between 0 and 164. Ive read a
little bit about upper and lower LSBs/MSBs... but i still don't really
understand them. I'm going to do some more research into that myself
but anyone willing to enlighten me in a response to this is welcome.

Other information you might be interested in to aid your answer: I'm
on a mac, running OS 10.5.6. (I have access to a windows computer if
its completely necessary). I'd like to be connecting the BCR to my
macbook via usb, and the midi in/out to the Mopho.

So, before i drop the money for a BCR2000, can it be done? can i have
one knob with a resolution of 0-164, and how would i go about it?

Thanks

Re: DSI mopho cutoff 164 not 127 and BCR2000

2009-02-28 by rpcfender

Hi 

> I've seen bits of information about this now and then but nothing
> definitive and nothing that makes me say "I know the answer now".
> Basically on the Dave Smith Instruments Mopho the cutoff parameter
> goes from 0-164 (all the other parameters are the standard 0-127) and

Parameters can go from anything to anything, BUT Midi data can only go
from 0 to 127 (00 to 7F)

> i am wondering if it is possible to set one of the knobs on a BCR2000
> to transmit a CC with a resolution between 0 and 164. Ive read a

The BCR uses 14bit numbers internally 0 to 16383 ($0000 $3FFF) but the
Midi CC message has the Status byte B0 to BF then 2 data bytes.
Controller number 0 to 128
Controller value 0 to 128
So nothing can transmit CC value of 164, including Dave Smith

He would have to split the value into at least 2 data bytes.
He could do this with 2 controllers (Like the way a preset bank is
selected with CC0 and CC32)
He could do this with sysex, which is the way most folk do it.

Pitchbend has 2 data bytes so he, in theory, could do this but unlikely.

It is likely that you can map a incoming CC to the filter and although
you wouldn't get the fine resolution you would get the range.

> little bit about upper and lower LSBs/MSBs... but i still don't really
> understand them. I'm going to do some more research into that myself
> but anyone willing to enlighten me in a response to this is welcome.

See the document Secrets.pdf in the files section I think I went
though multiple data bytes in that.

> So, before i drop the money for a BCR2000, can it be done? can i have
> one knob with a resolution of 0-164, and how would i go about it?


The BCF/BCR can do any of these messages (including multiple message
on the one control.) 
The only cases where it gets stuck is when the data is packed (the Osc
octave and the Osc wave type are in the one byte as in the DW6000)
This was used when memory was expensive, so in your case I'm sure it's
not an issue.
Negative numbers where 2 bytes are used for the data as in the EMU
Morpheus/Proteus etc  -7 to 7 but I need $7F $79 to $00 $07
You will need to check the Midi spec to see if this is a problem

The BC can happily do -7 to 7  with a single byte of data $79 to $07
It can do most things as far as controlling a hardware synth.


How would you go about it? There is heaps of messages from other
people that have written presets for hardware synths. Check them out. 

Grab Mark's brilliant editor and BCL (Behringer Control Language)
document on his website.

Give it a shot and then ask folk here for some help if you need it.

I hope this helps

Royce

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.