Skip to content
blzr docs

What is a module?

A module is a closed subgraph with its own inputs, outputs, and exposed parameters.

Inside the module, you can build with primitives.

Outside the module, you only see the interface you chose to expose.

Group and ungroup

Section titled “Group and ungroup”
  • Select nodes and press g to group them into one module.
  • Select a module and press u to ungroup it.
  • Pressing g twice on the same selected module does not wrap it again.

Grouping keeps your audio wiring intact. You are changing structure and interface, not sound.

Nested modules

Section titled “Nested modules”

Nested modules are supported.

If you group multiple top-level items and some of them are already modules, blzr creates a parent module around that selection.

Module Inspector workflow

Section titled “Module Inspector workflow”

When you select a module, the inspector gives you:

  • Module name field.
  • Read-only topology preview with minimap.
  • Controls to expose/unexpose ports and parameters.
  • UI controls for exposed parameter label, range (min/max), and step.

These inspector edits are UI metadata. They do not change the underlying audio graph topology.

Why modules matter

Section titled “Why modules matter”

The series bible treats this as a core rule: complexity should move inside modules so the main graph stays readable.

That means a patch can start as raw primitives and later become a reusable building block.

Two ways people use modules

Section titled “Two ways people use modules”
  • A patch designer builds the internals.
  • A sound designer uses the cleaner external controls.

Both are working with the same synthesis system, just at different levels of abstraction.

Next steps

Section titled “Next steps”