Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

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

Message

[bc2000] Slim Phatty Arpeggiator Clock Rate

2011-02-23 by Alex

Hi all,

I would like to configure the Slim Phatty Arpeggiator Clock Rate to one of my BCR2000 encoders but I get a strange behavior and I need your help again. Thanks in advance.

First of all this is what manual says:

"The Arpeggiator Clock Rate is set by two MIDI CC messages that correspond to coarse and fine clock rates. The coarse rate is set by CC#04 in increments of 3 BPM over a range of 21-320 BPM, and the fine rate is set by CC#36 in increments of 0.1 BPM. To set the clock rate, first set the coarse rate by dividing the target BPM by three; the integer result (the whole number) will be the CC#04 value. Then set the fine clock rate by subtracting the coarse BPM value from the target value and multiplying the result by 10. This will be the CC#36 value.

For example, to set the Arpeggiator Clock Rate to 121.7 BPM:

Determine the MIDI CC coarse value by dividing the target BPM by 3:

121.7/3 = 40.566

The CC#04 value is ‘40’ (=120 BPM)

Determine the MIDI CC fine value by subtracting the coarse BPM value from the target value:

121.7 - 120 = 1.7

Then multiply the result by 10:

1.7 * 10 = 17

The CC#36 value is ‘17’

For CC#04 = 40 and CC#36 = 17, the Slim Phatty’s display will show ‘121.7 BPM’."

After assigning the CC#04 in absolute (14-bits) mode and with a resolution of 96 for testing every value, this is what I get: (I only tested the first 640 values)

Values BPM

0-494 ---> 20.0
495 ---> 20.1
.
.
511 ---> 21.7
512-592 ---> 20.0
593 ---> 20.1
.
.
639 ---> 24.7
640 ---> 20.0

Could somebody tell me how should I set this encoder in BC Manager to get the full range, from 20.0 to 320.0 BPM, without these jumps and gaps?

Thank you so much in advance.

Alex



Attachments

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.