Bc2000 (for the BCF2000 & BCR2000)

> Okay, I did some homework and this appears to be control resolution issue (i.e., different controls have different operating resolutions).  The Fine Tune control is a 5-bit control and a switch is a 1-bit control, etc.
> 
> I had hoped that if I switched over to sending sysex messages instead of cc messages, I could set the number of bits in the control and thus bring the BCR and the Six-Trak into the same numeric realm.  But that doesn't seem to be working.
> 
> For one thing, I'm not clear on what "Value" setting in BC Manage correlates to what bit resolution.  The value settings are listed as 
> Value, Value: bits 0-6, Value: bit 0, etc.  I tried them all and none allowed me to synchronize the numbers.
> 

It is best to think that internally the BCR uses 16 bit but only goes up to the max for 14 bit Midi numbers. That is 2 bytes but only 7 bits long (bits 7 - 13 and bits 0 - 6 ).
14bit $0000 to $7F7F
16bit $0000 to $3FFF
That is in 14 bit midi numbers
$007E
$007F
$0100
$0102
$0103

The value is generated then the bit wise filters are applied.

the numbers in the val statement are for a 16 bit number
val = val0.6 = bits 0-6
val0 = bit 0 (val AND $0001)
val1.7 = bit7 and bits 1-6 (val AND $00FE) rolled right once into bits 0-6
val7.13 = bits 7-13 (val AND $7F00) rolled to bits 0-6
val0.3 = bit 0 - 3 (val AND $000F)
val4.7 = bit 0 - 3 (val AND $00F0) rolled to 0-6
val8.11 = bit 8 - 11 (val AND $0F00) rolled to 0-6
val12.13 = bit 12 - 13 (val AND $3000) rolled to 0-6

Because the BCR uses 16 bit internally we can exploit this to generate -ve number ranges 

eg -7 to 7
min = $80 - 7 max $80 + 7
min = 121 max = 135
default = 128  (this becomes 0 with val because the binary of 128 is 1000 0000 - bits 0 to 6 are all 0)


Royce