• ### Quantising in real time for step sequencer

Hi posted in here about this, but then deleted my post thinking ive found a solution. Now I've run into some problems with that. Basically i want to be able to play in and quantise notes to 16 step sequencer in real time. I thought if I used 1/32 clock running 0.5 ahead of the 1/16 clock this would do the trick. The only thing is that the way my patch works is that I sent the current step recording to a tabwrite object, as the index to write the note that is coming from notein to an array. The problem is if it is going from 1 to 32 then it is too many numbers for my array and if i half it then [i] to make integer it just runs at same time as the 1/16 clock. What am i missing here? Sorry i am a pd beginner. Thanks

• Posts 7 | Views 4404
• quant_step_seq_forum_2.pd

voilà 4 vanilla

(edit: increasing the resolution 2 times instead of 10 might be more efficient)

• @djpersonalspace and I messed with the BPM

• Awesome thanks, works great. I do not understand your patch at all though so i I have some studying to do haha

• @djpersonalspace
It's commented on almost every step.
Some arrays are just for visualisation.
The [% 10] and [mod 10] are there just for understanding the [expr] better.

Read the patch from the top left to the lower right.

I guess it is not efficient at all, could be made easier, - these are just my thoughts sketched.

The main idea is: increase the resolution by 10 and round up if the remainer of /10 is >=5, else round down.
A complicated way to round 3.7 up and 6.2 down!

Increasing the resolution by 2 and distinguishing between even and odd numbers might be more efficient and would make the decision symmetric
(even vs. uneven / set current step or one step later) ... ( now it is 1234 vs 56789, these are 4 cases vs. 5 and this is not a symmetrical decision in the center of the two beats)

Your BPM conversion might be more true.