home/ atoms/ nodeproxy-modular-patching

Each NodeProxy can act as a module patched into others at audio (.ar) or control (.kr) rate

In ProxySpace each NodeProxy can be seen as an individual module, and each module can be plugged into others to create a complex network of interconnected musical and control elements. This is achieved by setting up audio (.ar) and control (.kr) proxies: audio-rate proxies carry signal, control-rate proxies carry modulation, and one proxy is embedded as an argument inside another. Because any proxy can be rewritten with a crossfade, the whole patch — oscillator into filter into effect — stays live-editable, unlike a fixed SynthDef chain. When proxies feed back into each other, DC bias can accumulate, so wrap the offending stage in LeakDC and fade modules gradually to keep the patch stable.

Examples

~lfo = { SinOsc.kr(0.5) }; ~filt = { LPF.ar(~src.ar, ~lfo.kr.linexp(-1,1,100,8000)) }; — a control-rate proxy modulates a filter cutoff.

Assessment

Build a three-module ProxySpace patch (oscillator, filter, delay) where the LFO rate can change without stopping audio, and explain what LeakDC does and when a feedback patch needs it.

“Each NodeProxy can be seen as an individual module, and each module can be plugged into others”