polyrhythm sequencer patch

Here is my polyrhythm sequencer patch. There are three [bang] objects at the top; RESET, OFF & ON. There is a PITCH CONTROL. The horizontal PITCH slider does not adjust the PITCH in real time. After you increase or decrease the pitch you must push the ON [bang] object to initiate your change in PITCH. The basic to running this patch once constructed correctly in pure data; Select these objects in order; RESET, select the MEASURE (1-32), adjust the PITCH & last ON. This should initiate the patch to run correctly no matter what pitch. I have set the min-max values in the properties of the pitch slider: 1-400. As I close in on a performance I often adjust these values with the max set about 20 clicks above the pitch that I feel best suits the pitch with the patch. This creates a finer adjustment on the slider. A pitch of 0 will create anomalies in your performance & can create uncontrollable sounds with your outboard gear. When the patch is performing, pushing the RESET button either, starts the starting pattern from the beginning or creates different patterns without disturbing the pitch. At this moment in my working with pure data this is either an error in my patching or an interesting result of when I pushed RESET [bang] object in the timing of the performance.

Interesting things could happen here; patch a [random] or [moses] object here to alter the pattern during is performance.

This video presents the polyrhythmic sequencer in action. Please note that in the patch the "Rim Shot" is a "crazy train" Shaker (I wish) instrument, not a rim shot. It was a rim shot but the sound overtook the kick drum & I wanted the sounds on each track to be distinguishable for this presentation.

This polyrhythmic patch is built off of the Linear patch presented in my earlier blog post. Polyrhythm is essentially different clocks or in puredata's case [metro objects] beating at different rates, governed by a master clock or the central [PITCH CONTROL] in this patch. This polyrhythmic patch yields three metro objects (different tempo branches) that sequence through 8 send [s ]& 8 receive [r ] objects. The three red bangs ( valued 1 - 3) for each of the groups give the conductor the ability to easily alter multiples or denominators. Multipling or dividing the master pitch. In each of the three groups the pitch can be set to equal the master pitch (value = 1) or a multiple / division of the master pitch at (value = 2) or a triplet at (value = 3). In this patch I have two metro groups that multiply & only one that divides. This can be changed by altering the math objects, [* 2] to [/ 2] for example, in any of the groups. Or an entirely new metro group could be added to the overall patch, so that the patch would have two [* 2] & two [/ 2] metro groups. Any number can be predetermined into the puredata math objects seen in the youtube video patch version or available as a selection into these pd math objects, as displayed in the patch image. Playing around with these multiples or divisions of the central PITCH will produce many different outcomes in tempo for it's specific [metro] object branch. Depending on your midi gear & other hardware you may find excessive values wreck havoc in the production. keeping values strict in the math objects to 1-3 is suggested. With the master pitch slider set from 1-1000 you'll be able to (increase / decrease) various [metros] and cover all the various time signatures out there from quarter, half & triplet. and still find that your midi gear can handle excessive tempos and not run off the rails. I have created both gigantic sounds & sounds that won't stop unless you power down your equipment, because of bad math in the patch, whether your midi panic buttons work or not. These puredata patches as you construct & test them, considering the math employed can & will produce anomaly midi issues, reminiscent of midi flatulence. These audio anomalies can just be devastatingly different depending on the mathematical outcome of your puredata patch. Dividing by 0 or values that create a tempo that is too fast or too slow, can produce undesirable results depending on your application of a [metro] object's tempo into your midi components.

* KicKRaTT; MUSIC, ALGORITHMS, DOCUMENTS, GRAPHICS & LOGOS: ISNI# 0000000514284662 *