benniy

i'm tinkering with the idea to build a new sequencer (i love them so much!! (:). obviously, clocking is always the big topic here! ... up till now, all sequencer's i've written (such as 

) were non-audio-driven / clocked. knowing barely anything about the DSP domain of max, this was partially a pragmatical approach :) so:

any advantages or disadvantages to go for a sample-rate based sequencer-clock? any starting point and experience as for such a clocking system? or is this an overall stupid idea?

i'd be gracious for any input, links, and thoughts.

i'm tinkering with the idea to build a new sequencer (i love them so much!! (:). obviously, clocking is always the big topic here! ... up till now, all sequencer's i've written (such as polyrhythmus) were non-audio-driven / clocked. knowing barely anything about the DSP domain of max, this was partially a pragmatical approach :) so:

any advantages or disadvantages to go for a sample-rate based sequencer-clock? any starting point and experience as for such a clocking system? or is this an overall stupid idea? 

i'd be gracious for any input, links, and thoughts.


sequencer-clocking-the-options

beside the question of advantages there is the question of necessity.

a signal driven clock is only required when you are controlling nothing else but signals with it. but in this case, of course, it is superior to messages.

also, in opposite to metro, a signal driven clock remains tight when you use bigger I/O vector sizes.

Here is a good start, especially the patch that goes with this tutorial:

https://cycling74.com/wiki/index.php?title=MSP_Sequencing_Tutorial_1:_Audio-Rate_Sequencing

Here is a good start, especially the patch that goes with this tutorial:
https://cycling74.com/wiki/index.php?title=MSP_Sequencing_Tutorial_1:_Audio-Rate_Sequencing


depends on what the sequencer is doing. :)

http://www.izhikevich.org/publications/pllnn.pdf

(sequencer) clocking. the options?