phiol

sharing-is-fun-matrixctrl-sequencer-sig-tightness-2

If you want real signal tightness you have to stay entirely in MSP. Triggering your samples with bangs will introduce a jitter. One way to accomplished this is to store your sequence in buffers using peek~ and recall them with index~.

yes, I did. You are using edge to convert your audio impulse to a bang. That means that you are leaving the msp world, what makes all your effort useless.

Something like this should do the trick:


but I was sharing for people to use with Midi based triggers and UI stuff.

I like your little twist in the 2nd patch very useful.

Testing things around this morning I found how different Max6's Audio Status

behaves very differently to Max 5's. I.e. Audio interrupt really does interrupt the signal.

And the signal I/O vector really do affect the behavior in comparison to Max 5.

tried both in max 32bit and 64 bit. Then when put into a bpatcher there was even a different behaviour there :-| !

cool :-)!
but I was sharing for people to use with Midi based triggers and UI stuff.
I like your little twist in the 2nd patch very useful. 

on a side note
Testing things around this morning I found how different Max6's Audio Status
behaves very differently to Max 5's. I.e. Audio interrupt really does interrupt the signal.
And the signal I/O vector really do affect the behavior in comparison to Max 5. 

sharing is fun! (matrixctrl sequencer sig~ tightness!)