Tips for using clocks limited to 300 BPM when need faster rate?

Plugins & Modules
21

a while ago I did this for the VCP-26:

title: “How slow can 60000bpm be”

1 Like
22

So I thought, what to do with a fast clock?

fastclock.vcv (10.9 KB)

Just a little experiment

23

I don’t know if it’s in your skill set, but looking thought the source of Impromptu’s Clock it’s defined simply:

#include "ImpromptuModular.hpp"


static const float ratioValues[34] = {1, 1.5, 2, 2.5, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 19, 23, 24, 29, 31, 32, 37, 41, 43, 47, 48, 53, 59, 61, 64};

static const int bpmMax = 600;
static const int bpmMin = 30;

Redefining bmpMax sems to work.

600
600773×667 142 KB

You’d probably be limited to 999 BMP owing to the display.

1 Like
24

I originally limited the master BPM to 300 since it has to support a x64 clock ratio (which gives 19200 BPM), all the while supporting SWING and PW modulations given that the minimum a pulse width can be is 1ms. But it can definitely be hacked to circumvent those limits… kind of like overclocking a CPU, haha :slight_smile:

And just like in those cases, overclocking CLOCKED may lead to undefined behavior and might void your warranty! :stuck_out_tongue:

5 Likes
25

I’ll make you a deal. Gimme 900 and reduce the multiplier to 21.3…wait that won’t work. How 'bout gimme 600 and reduce multiplier to 32? Totally kidding :yum: I appreciate your explanation :grinning:

Edit - …and I appreciate all that you do for the community whether I use your modules or not :grinning:

2 Likes
26

Thanks for the kind words, very much appreciated! :slight_smile:

1 Like