RotSprk-ProximityCore-v2.amxd<\/code>) that handles the spatial logic. Newer versions are being developed to support multiple instances by using automatically generated instance numbers.<\/p>\n<\/details>\n\n\n\nNotes here are intended to provide necessary details to extend work to date for orchestration of Rotating Speakers to better support devices such as the triple rotators supporting horizontal position or rotation rate and 3 independent vertical speakers. <\/p>\n\n\n\n
As part of the Rotating Loudspeaker project orchestration layer, I developed an M4L Device that supports basic rotation controls that can be mapped to Ableton variables and the “Proximity Engine” node.<\/p>\n\n\n\n
Node: to date, the RotSprk-ProximityCore-v2.amxd works as a single instance in an Ableton set due to hardcoded Max send and receive objects. A new version of this and the underlying subpatches in progress that uses automatically generated instance numbers to allow multiple instances.<\/p>\n\n\n\n![\"\"](\"https:\/\/composers-inside-electronics.net\/cie-wp20\/wp-content\/uploads\/2026\/04\/image-37.png\")
<\/figure>\n\n\n\n<\/span>node_single_rotatorV1.maxpat<\/span><\/h2>\n\n\n\nThis is a work in progress for use in Ableton and Max Patches for controlling sound and kinetic objects such as rotating loudspeakers and associated audio contexts.<\/p>\n\n\n\n
Google Gemini is used to describe the function of the patch.<\/p>\n\n\n\n
<\/span>Presentation View node_single_rotatorV1.maxpat<\/span><\/h3>\n\n\n\n![\"\"](\"https:\/\/composers-inside-electronics.net\/cie-wp20\/wp-content\/uploads\/2026\/04\/image-29-1024x979.png\")
<\/figure>\n\n\n\n<\/span>Record \/ Play Control embeded in node_single_rotatorV1.maxpat<\/span><\/h4>\n\n\n\nA mechanism is provided to record and playback motion.<\/p>\n\n\n\n
A pulldown menu provides selection of:<\/p>\n\n\n\n![\"\"](\"https:\/\/composers-inside-electronics.net\/cie-wp20\/wp-content\/uploads\/2026\/04\/image-32.png\")
<\/figure>\n\n\n\n\n- Stop<\/li>\n\n\n\n
- Play<\/li>\n\n\n\n
- Loop 0 disables the play loop<\/li>\n\n\n\n
- Loop 1 enables the play loop<\/li>\n\n\n\n
- Record starts recording the movement<\/li>\n\n\n\n
- Read reads a file of the movement<\/li>\n\n\n\n
- Write writes a file of the recorded movement<\/li>\n<\/ul>\n\n\n\n
<\/span>Patching View node_single_rotatorV1.maxpat<\/span><\/h2>\n\n\n\n![\"\"](\"https:\/\/composers-inside-electronics.net\/cie-wp20\/wp-content\/uploads\/2026\/04\/image-28-1024x741.png\")
<\/figure>\n\n\n\n<\/span>Gemini AI explanation of the max patch<\/span><\/h2>\n\n\n\nPrompt: explain this max patch (text of patch loaded into the browser)<\/p>\n\n\n\n
—————– Gemini Response –<\/p>\n\n\n\n
This patch, titled node_single_rotatorV1.maxpat<\/code><\/strong>, is a sophisticated spatial or parameter controller designed to move a “node” (a data point) in a circular or complex geometric pattern. Based on the file path and objects, it\u2019s part of a “Pepscillator” project, likely used for controlling a Rotary Speaker<\/strong> simulation or a panning effect.<\/p>\n\n\n\nHere is the breakdown of how it works:<\/p>\n\n\n\n
<\/span>1. The Core Engine: Movement<\/span><\/h3>\n\n\n\nThe patch features two distinct modes of movement, controlled by the obj-32<\/code> toggle (labeled “Clifford” in the presentation):<\/p>\n\n\n\n\n- Standard Rotation (The “Simple” Mode):<\/strong> It uses a
phasor~<\/code> (an audio-rate ramp) converted to control data via snapshot~<\/code>. This drives a cos<\/code> and sin<\/code> relationship to create perfect circular movement for a node.<\/li>\n\n\n\n- Clifford Attractor Mode:<\/strong> When toggled, the data flow shifts to a
bpatcher<\/code> called clifford-worker<\/code>. This uses a mathematical Clifford Attractor<\/strong> (a type of chaotic fractal) to generate more organic, non-repeating, and complex movement patterns rather than simple circles.<\/li>\n<\/ul>\n\n\n\n<\/span>2. The “Nodes” System<\/span><\/h3>\n\n\n\nThe patch uses two nodes<\/code> objects (obj-48<\/code> and obj-1<\/code>). In Max, nodes<\/code> is a UI object used to map 2D space.<\/p>\n\n\n\n\n- It appears the patch takes the mathematical output (the circle or the attractor) and uses it to “drive” the position of Node 1<\/strong>.<\/li>\n\n\n\n
- This position is then sent out via
send nodectl<\/code>, likely to an external audio processing patch that handles the actual panning or filtering of the audio.<\/li>\n<\/ul>\n\n\n\n<\/span>3. Key Controls (The UI)<\/span><\/h3>\n\n\n\nYou have several parameters that shape the movement:<\/p>\n\n\n\n
\n- Rate (
obj-38<\/code>):<\/strong> Controls how fast the rotation or the attractor updates. It scales between 0.002 and 0.5.<\/li>\n\n\n\n- Scale (
obj-42<\/code>):<\/strong> Controls the “width” or “depth” of the movement\u2014essentially how large the circle or pattern is.<\/li>\n\n\n\n- Phase (
obj-16<\/code>):<\/strong> Offsets the starting point of the rotation.<\/li>\n\n\n\n- Node Number (
obj-70<\/code>):<\/strong> Allows you to specify which node (if there were multiple) is being commanded.<\/li>\n<\/ul>\n\n\n\n<\/span>4. Data Recording & Playback<\/span><\/h3>\n\n\n\nThe bottom-right section (objects like mtr 10<\/code>, umenu<\/code>, and obj-75<\/code>) is a multi-track recorder<\/strong>.<\/p>\n\n\n\n\n- The
mtr<\/code> object allows you to record<\/strong> the movement of the nodes and play it back<\/strong>.<\/li>\n\n\n\n- The menu contains standard transport commands:
play<\/code>, stop<\/code>, record<\/code>, loop<\/code>, and write<\/code> (to save the movement data to a file).<\/li>\n<\/ul>\n\n\n\n<\/span>5. Automation & Presets<\/span><\/h3>\n\n\n\n\nthispatcher<\/code> & zoom_ctl<\/code>:<\/strong> These are utility objects used to manage the window size and UI scaling, making it act more like a professional plugin interface.<\/li>\n\n\n\n- Message Boxes (
obj-6<\/code> and obj-40<\/code>):<\/strong> These contain “presets” for the Clifford Attractor, instantly setting the $a, b, c, d$ variables to specific values to generate different chaotic shapes.<\/li>\n<\/ul>\n\n\n\n<\/span>Summary of Logic Flow:<\/span><\/h3>\n\n\n\n\n- Clock:<\/strong> A
metro<\/code> or phasor~<\/code> provides the timing.<\/li>\n\n\n\n- Generator:<\/strong> Either a Sine\/Cosine pair or a Javascript\/Clifford math script generates X\/Y coordinates.<\/li>\n\n\n\n
- Mapping:<\/strong> Those coordinates are scaled and sent to the
nodes<\/code> object.<\/li>\n\n\n\n- Output:<\/strong> The final X\/Y position is broadcast via
s nodectl<\/code> to affect your sound.<\/li>\n\n\n\n- Storage:<\/strong> The
mtr<\/code> captures these movements if you want to repeat a specific performance.<\/li>\n<\/ol>\n\n\n\nIs there a specific part of the math (like the expr<\/code> objects) or the recording logic you’d like me to dive deeper into?<\/strong><\/p>\n\n\n\n<\/span>node_rotator_manyV1.maxpat<\/span><\/h2>\n\n\n\nThis is a bundle of 4 node_rotator_singleV1.maxpat with the addition of a Mira iPad interface. The “Rotator Many” panel surfaces as a tab in Mira on an iPad and integrates into Ableton via NodeRotMap8.maxpat<\/strong> as adapted from M4LRotSkpkrMap8.amxd<\/strong>.<\/p>\n\n\n\n![\"\"](\"https:\/\/composers-inside-electronics.net\/cie-wp20\/wp-content\/uploads\/2026\/04\/image-30-698x1024.png\")
<\/figure>\n\n\n\n<\/span>iPad Mira<\/span><\/h4>\n\n\n\nhere is a screen snapshot of the the Rotator Many tab from an iPad. (needs further explanation)<\/p>\n\n\n\n![\"\"](\"https:\/\/composers-inside-electronics.net\/cie-wp20\/wp-content\/uploads\/2026\/04\/Image-1024x768.jpg\")
<\/figure>\n\n\n\n<\/span>M4LRotSkpkrMap8.amxd Base