How schollz/bloom works
Bloom is a norns/SuperCollider generative-music instrument. The main workflow is user input or idle evolution producing patterns, which play scale-based sounds; users can adjust sound and routing parameters. The README documents these capabilities, but the sampled source does not show runtime wiring, so the diagram keeps relationships to those documented there and does not infer calls between library modules.
Main entry points: Engine_Bloom.sc Audio engine · bloom.lua Norns controls · BloomPattern.sc Pattern lanes · data Scale notes
Components 15
Interaction
- Norns controls
bloom.lua - Grid input
bloom.lua - Screen display
bloom.lua
Pattern and scales
- Pattern lanes
lib/BloomPattern.sc - Generate and evolve
bloom.lua - Scale notes
data
Sound and output
- Audio engine
Engine_Bloom.sc - Kalimba samples
samples/kalimba_small - MIDI output
bloom.lua - Crow output
bloom.lua
Runtime components
- Record behavior
lib/BloomRecord.sc - Wild evolution
lib/BloomWildly.sc - Sample support
lib/BloomSample.sc
Other components
- Player
- SuperCollider user
Connections 12
- Player → Norns controls: controls
README.md - Player → Grid input: selects notes
README.md - Norns controls → Generate and evolve: generates patterns
README.md - Grid input → Pattern lanes: creates sequences
README.md - Generate and evolve → Pattern lanes: creates patterns
README.md - Pattern lanes → Audio engine: plays sounds
README.md - Scale notes → Audio engine: provides notes
README.md - Kalimba samples → Audio engine: blends with synthesis
README.md - Norns controls → MIDI output: routes output
README.md - Norns controls → Crow output: routes output
README.md - SuperCollider user → Audio engine: runs instrument
README.md - Audio engine → Screen display: redraws display
README.md