NODESTROM SPRINTS
Different MIDI input devices connected to NODESTROM
During the development of NODESTROM, a node-based interface tool I am building for audiovisual live performances, I created several practical application examples called „sprints“. Each sprint is a sketch built within a single day, designed to leave the engine room, gain hands-on experience with the software, and feed insights back into the iterative development process. They demonstrate different use cases and signal routings.
The following examples are the results of this sprint-based process and show the range of possible applications for NODESTROM.
All sketches are available as Git repositories with full project files on my Codeberg at https://codeberg.org/klaasklee/.
Horse Mosaik (audiovisual)
Use Case
Bridge:
Single Output
↓
Single Output
Signal Chain
Strudel (sequencer with internal sound system)
↓
NODESTROM
↓
Processing (visualizer)
Description:
An audioreactive visual system where NODESTROM handles the interpretation logic of MIDI signals for the visualizer.
Strudel (a live-coding environment) generates both audio and MIDI triggers, which are processed by NODESTROM and translated into visual parameters for Processing. The visuals react to the musical events in real time.
Visuals, Strudel, and NODESTROM patch of the Horse sprint
3D Scene
Use Case:
Bridge
Single Output
↓
Single Output
Signal Chain:
MIDI Controller (custom-built slider box)
↓
NODESTROM
↓
Processing (visualizer)
Description:
A 3D scene controlled by an external MIDI controller.
NODESTROM handles the translation, mapping the controller’s MIDI signals to position parameters for the camera and objects in the 3D scene.
Visuals of the 3D Scene sprint
NODESTROM as Sequencer
Use Case:
Generator
No Input
↓
Multiple Outputs
Signal Chain:
NODESTROM
↓ ↓
↓ └──→ Reaper (Audio/DAW)
↓
└──→ Processing (visualizer)
Description:
Here, NODESTROM acts as a standalone sequencer without any external inputs.
The system consists of three components:
1. Generation of time-based patterns within NODESTROM
2. Translation into note signals for the digital audio workstation (DAW) Reaper
3. Translation into control signals for Processing
The visuals consist of a video sequence played back audioreactively, enhanced by additional parameters like scaling and image effects.
Visuals and NODESTROM patch of the Sequencer sprint
Visuals Trigger Sounds
Use Case:
Feedback Loop
Multi-Stage Processing
Signal Chain:
MIDI Controller (keyboard)
↓
NODESTROM ←────────────────┐
↓ ↓ │
↓ └──→ Reaper │
↓ (Audio) │
↓ │
└──→ Processing ───────────┘
(particle system)
Description:
A complex feedback system where visual events generate audio signals.
A MIDI keyboard triggers a particle system in Processing via NODESTROM. Collision events from the particles are sent back as feedback to the same NODESTROM instance, where they are translated into MIDI notes for Reaper. The visual layer actively participates in the musical process.
Visuals of the Visuals Trigger Sounds sprint
Multiple Instruments, One Controller
Use Case:
Splitter
Single Input
↓
Multiple Outputs
Signal Chain:
MIDI Controller (keyboard)
↓
NODESTROM
↓ ↓ ↓
↓ ↓ └──→ MIDI Instrument 3
↓ └──────→ MIDI Instrument 2
└──────────→ MIDI Instrument 1
Description:
Several sketches sharing the same basic structure: NODESTROM receives signals from a controller (keyboard) and drives multiple synthesizers simultaneously. As a solo performer, you can create more complex, layered sounds by using the logic defined in NODESTROM to transform incoming signals and distribute them across different instruments.
Sprint session with various input devices and instruments
The following five variations explore different approaches to signal splitting and transformation:
Sketch 1: Hand-Drawn Arpeggiator with Drone Split
A single keystroke is received from the MIDI controller and distributed across multiple instruments via NODESTROM. This simultaneously produces arpeggiated patterns and drone sounds. The arpeggiator pattern can be drawn by hand in the Graph Draw node. The system outputs only whole tones (no semitones).
Sketch 2: Pattern Arpeggiator
An evolution of the concept using a predefined pattern instead of a hand-drawn one. The clock speed of the arpeggiator can be controlled in real time via an external slider. One instrument serves as a continuous drone layer, while the others play arpeggiated patterns.
Sketch 3: Velocity-Enhanced Pattern Arpeggiator
Builds on the concept from Sketch 2 and adds velocity control. The key pressure is now also processed through NODESTROM and mapped to the different instruments.
Sketch 4: Alternative Pattern Approach
An alternative technical implementation of the Pattern Arpeggiator concept from Sketch 2. This variation explores a different approach within NODESTROM to achieve the same musical goal.
NODESTROM patch of Sketch 4
Sketch 5: „Fur Elise“ Auto-Player
Based on a single starting note played on the MIDI controller, the system plays back the melody of Beethoven’s „Fur Elise.“