Generative Polyrhythms - Max/MSP Tutorial

[@machinate]

this is lovely! I would encourage viewers to dive into [what~] - yes in its default setting it detects the zero-crossing, but it can actually convert a phasor into an entire rhythm set, and in conjunction with subdiv~ you can really get deep into rhythm-land.

[@crash936]

Plz do a tutorial

[@banalytic]

thank you so much for this video. the new objects open up great new possibilities. Based on your patch, I made a sixfold sample player with different subdivisions and probalities that change continuously. loading own field recordings at low bpm numbers and the sun rises :))

[@psydyl]

really nice stuff, the 8.3 update was a little daunting since I never really delved into the phasor controlled stuff, this definitely makes it less so! lovely sounds :D

[@harry2993]

Outstanding execution! I’ve been wondering how to do this for a while, and you’ve answered my thoughts perfectly

[@davidcooper8241]

this sounds fantastic

[@AndrewGordonBellPerc]

Just tried messing around with something similar thanks to this video, you can get really cool off kilter effects by adding a kink between the phasor and individual subdivs

[@machinate]

I love that kink~ is a distortion, if applied to audio, and a weird type of "swing" if applied to rhythm. See also Malcolm Braff and his weirdo work with rhythm in this way. :)

[@NedRush]

Great stuff 👍🏻

[@WARDISWARD]

what's the difference between the what ~ and the delta~ object ? Delta ~already did that

[@HearingGlass]

There is a small difference between the two: delta~ gives you the differences between each sample, while what~ gives you an impulse when the signal crosses a threshold.

[@PaulWegmann]

Hi! What advantages you see in what and subdiv over rate~ and onset detection based in delta~ and edge? Thank you!

[@HearingGlass]

subdiv~ is more versatile than rate~: You can set a sequence of subdivisions, and add probabilities for those subdivisions triggering.

[@yoursaxel]

Nice! n00b question: Since this patch contains live.* elements, I figure its not a standalone Max but running on top of Ableton?

[@HearingGlass]

This is the regular, standalone Max. The live.* family of objects were introduced to synergise with M4L devices, but they work in regular Max just as well. (Except the ones that specifically interact with the M4L environment, i.e plugin~)