Controlled feedback

Cycles in a graph would normally run forever. The 16-repeat feedback budget turns them into a creative tool: feedback loops produce evolving material until they fade out, while one-way phrases can keep moving through the graph.

Connect a node back to one of its upstream neighbors and you have a cycle. A signal arriving at the loop entry will travel around the loop again, again, again. Without a stop condition, this would run indefinitely. The platform gives repeated feedback routes a 16-hop budget.

Feedback is useful because every signal tracks repeated route hops and stops at the feedback budget.
Study this evolving cycle: listen to the loop decay through the graph, inspect the return wire, then remix the cycle length before it spends the feedback budget.
Study this composition

The move

  1. Place a Source and a Vibe Node. Connect them.
  2. Place a harmony modifier (octaveDown) and a second vibe node downstream.
  3. Connect the second vibe node back to the harmony modifier with a long wire (8+ cells).
  4. You now have a cycle: Source → Vibe → Harmony → Vibe → Harmony → Vibe → … dropping an octave on each pass.
  5. Listen. Each loop drops an octave. After ~3-4 repeated hops the signal is in the bass; after ~8 repeated hops it bottoms out in the lowest octave (clamped). The loop stops when the feedback budget is spent.

What the budget gives you

Sixteen repeated feedback hops is enough for arpeggiated cycles, descending or ascending stacks, recursive call-and-response, and decay-style ornaments. It is too few for runaway. Designers can compose with the limit: the way it forces eventual termination is part of the aesthetic. A cycle that fades feels intentional; an infinite cycle would feel broken.