Microtiming Sequencer with Max for Live

[@chozilla]

Every time i watch a video I think "This are the last missing puzzle pieces i was looking for!" ... In reality Max is still very complicated coming from normal programming. >_< Thank you so much for teaching! I am learning a little bit every time.

[@domuzo]

killer stuff, thanks so much!

[@magade4206]

Ha! That was me! Super happy to see this video up!

[@illegalgiant_]

"if you dont have that book and you're patching in gen, youre insane" hes so right.... thanks philip. still slowly chugging along through a big patch im making over here. I'll share in your discord when its done. cheers edit: this is great. I much prefer this to printing the midi notes for shifting them, personally.

[@p__meyer]

excited to see what you're working on!

[@just-ask]

this is super insightful, thanks philip

[@vojkofau]

Great tutorial. the quantizer device you mentioned at the end seems even more interesting. I find it strange that plugphasor~ is out of sync, first time i've heard of this. Maybe if you put @sync lock attribute on the rate after it?

[@p__meyer]

thanks vojko! Yes good call. i should probably have spent some more time actually thinking about phase sync in general with the clocks, because it is kind of an important detail!!

[@henksmith8611]

Hey thanks for video. But why do you never do a little sound demo of the patches?

[@p__meyer]

these videos focus on the technique - the rest is up to you all!

[@AaronLevitz]

I’m not clear on how the new timing interacts with your incoming transport clock. It might help to mess with the sliders while hearing the rhythm against a metronome? (Like, I assume the downbeats line up. But as I slow one pulse, do the others retain their length, or is everything scaled proportionally to fit in a bar?)

[@p__meyer]

Hey Aaron! Yeah you hit all the big questions there. So in this case we're just scaling the input slope, which can push things way out of phase with the main sequencer. There's sorta two ways to address this: 1) "Normalize" the offsets so that they add up to 0. This is what I do in rtt.feel~. The result is that the output remains in phase with the clock phasor so that the first event of every bar lines up. 2) Instead of dynamically starting each subsequent subdivision when the last one is finished, initiate each in response to a straight subdivision. So you have like a pulse that is just a straight subdivision of the input clock, and each of those triggers a ramp with a "microtimed" slope. I haven't tried doing this yet but it would perhaps give the most predictable musical results.

[@AaronLevitz]

@@p__meyer I see the appeal of either approach. Perhaps a toggle switch can offer both?

[@StanleyKubick1]

Why is this in slomo?

[@StanleyKubick1]

Btw, you either have a thyroid issue or narcissism

[@jamg6311]

You probably changed the play rate

[@pangea2003]

amazing 🫶