Begin with the unfinished part

Before buying another small computer or synth, describe what remains unfinished in your present setup. Perhaps the sound exists but needs physical controls. Perhaps the controller feels right but the engine cannot respond independently to each finger. Perhaps you want a self-contained processor for one microphone. These are different problems, and the cheapest board is not necessarily the shortest route to solving any of them.

Make a complete list rather than comparing headline prices. Include the audio interface or codec, power, enclosure, display if needed, connectors, controller and software licences. Add the time required for assembly, configuration and repair. Avoid assigning a monetary value to every hour; simply be honest about which kind of work you enjoy. A project that teaches you useful electronics can be worth its effort even when an existing product would be quicker.

Three practical starting points

A finished device with an extension route suits a player who likes its physical layout. Move with RNBO Takeover and the FM-1 with its development ecosystem are examples to investigate, each with its own constraints. You inherit a particular set of buttons, controls and connections. That can be productive: the instrument already has a body, and the creative work becomes deciding what that body should do.

An integrated kit suits someone who wants to understand and assemble a complete instrument without designing every board. Zynthian publishes hardware documentation and offers its official kit as the most supported route into its platform. A development board and breakout suit someone who wants to build more of the instrument. Electrosmith’s Daisy Pod, for example, brings a Seed together with controls and audio connections so that initial programming does not require a bare breadboard setup.

Read the path from example to performance

Open the documentation before opening the shopping basket. Find the first working audio example, the current build or flashing procedure, the control reference and the recovery route. Check whether those instructions match the exact board revision and operating system you own. A clear example that you can modify is often more valuable than a long list of theoretical capabilities. The important question is whether you can trace a plausible route from purchase to your first playable test.

Look at the licence and project structure if you intend to distribute a modification. An open application may depend on a binary engine; a published schematic may not include every mechanical file; a personal-use build may have different requirements from a distributed one. These details do not make a platform unsuitable by themselves. They tell you which part of the instrument you can realistically extend and share.

Set a completion test before expanding

Define the first finished version in musical terms: one expressive voice with two independent gestures, a vocal delay with a clear function, or a four-part texture that starts reliably. Limit the physical controls to those needed for that version. Then test a complete short performance. If you cannot finish a piece because the instrument keeps demanding another configuration change, consider whether the next improvement should simplify the interface.

Choose an MPE-capable system only after checking both the input path and the receiving engine. A USB port and a polyphonic synth do not establish per-note expression. Similarly, choose an audio-reactive visual tool around the inputs and edition you need. Buy what makes the intended gesture possible now, with a documented route for the next change. The best platform is the one whose constraints you can turn into a musical practice you want to repeat.

Take it into a session

Try this.

Compare two candidate platforms using the same one-sentence instrument brief. List everything needed for the first playable version, the first official example you would run, and the part you would modify. Choose only after that path is concrete.

Listen back

  • Which parts do you want to build, and which do you want already solved?
  • Can you find a documented example close to your intended sound or gesture?
  • What would count as a finished first instrument?
Open the studio →