Build the effect you're missing

You have an idea for an effect, but the processing behind it is unfamiliar. Start with one audible behavior, build the smallest useful version and learn how to check that it does what you intended.

6 lessons · Free guides · Learn at your own pace

Your lessons

Some programming familiarity helps. Sound and digital-audio foundations are available when you need them.

Translate the sound into a system

Signals and systems connect an audible intention to an operation. Define a small behavior before assembling a larger tool.

Build your own tools
  1. Signals and systemsLinearity, memory and why EQ and distortion behave so differently
  2. Anatomy of a Maru moduleDeclaration, ports, parameters, processor and face

Build the focused version

An effect needs a real processing path. Use the module’s shared contracts so its controls and sound describe the same behavior.

Build your own tools
  1. Build an effectFrom a musical promise to a working processor

What you can put into practice

Understand how to build and test a small effect with a clear musical purpose.

  • Turn the sound idea into a small problem

    Describe one audible behavior, choose an input that reveals it and connect the intention to a processing operation.

  • Learn the DSP through something useful

    Build a focused effect so signal concepts have a sound and a musical purpose attached to them.

  • Know what to check next

    Use repeatable comparisons, silence and extreme settings to distinguish a working behavior from a pleasing first impression.

One input, one purposeful change

Describe an effect in terms you can hear, trace its signal path and choose a repeatable comparison for its output.

  1. 1Describe one audible behavior

    Write down the change you want to hear. Choose a simple input that makes the difference easy to recognize.

    Signals and systems
  2. 2Build the smallest useful effect

    Implement that one change through the module’s processing path. Leave additional features until the first behavior works.

    Build an effect
  3. 3Try to prove yourself wrong

    Compare input and output, then try silence, loud input and extreme settings. Keep one repeatable check for the behavior you intended.

    Testing sound and behaviour

Listen for this: The intended change should be audible and repeatable without unexpected silence, clipping or unstable output at the settings you plan to use.

Common questions

How much programming experience do I need?
Some familiarity with code helps. Begin with one effect behavior and use the sound and digital-audio foundations whenever the signal concepts are unfamiliar.
How will I know I have built the effect I meant?
State the expected audible change before implementing it. Compare input and output on a repeatable example, then test silence and extreme settings as well as the version that sounds good.

Free guides, no account needed. Pick the lessons that interest you.

Start learning for free