- 2007/09/08 features:
- 4 drum slots with 3 engines each
- 16 steps
- 4 step envelopes to trigger FXs
- 4 envelope patterns assignable to FXs send by drag and drop
dll:
MokaColladrum.rar
SE source file :
http://mokafix.chez-alice.fr/vst/SE_modules/seq5.rar
I made this drum sequencer:

full size
http://mokafix.chez-alice.fr/vst/SE_modules/seq5.rar
It works pretty well, I think, and it could be fun to make a nice drum machine with it.
I think collaboring on synths can be difficult, but drum is different, as several people can submit different small engines, and they can all be put together in the end, with a similar GUI, as there is room in a drum synth for different engines, different synthesis, sampling, or wathever you want.
This sequencer let you add all the classic features, and more. The patches use characters instead of didigts. I used DH Bitmap charcter driver module because it can be fed by a continuous text without comas, separate the values one by one, and translate them into numbers
And as it is case sensitive, it let you store up to... I don't know exactly, but 26x2+ all other kind of characters, + numbers, so at least 70 differents values in one character space, which is nice for storage in DH patch mem array. That way, if you limit the number of velocity levels, you can have different kind of effects (like in tatapoum) storable in that very small space.
In this example, it has 9 velocity levels, + 0, and one effect (flam). so it uses 19 kind of characters, which let room for at least 6 or 7 other pad triggered effects.
And of course, the pads don't need to be limited to 1 character. With 2 characters per pad, I let you imagine all the possibilities... (70 velocity levels x 70 effects
The sequencer sends gate and velocity, but if Fxs are added, it's easy to add other messages, as Voltages or midiCCs.
I have no much time myself to spend on this, and have no particular ideas, but as I did that sequencer and know some people might be interested in using it, I thought why not make a gorgeous KVR drum synth, with loads of features inside?
Of course, the less cpu hugry are the engines, the more engines can be put in it.
Collaborators would submit engines, or pad triggered FXs, and others would vote in the end to see what is kept.
It could end up with a great drum vsti.
Just an idea...
