FM Synthesis and Creative Code: More Similar Than You Think
Exploring the surprising parallels between frequency modulation synthesis and software architecture, and why thinking across disciplines makes both better.
Two Worlds, One Pattern
At first glance, FM synthesis and software development couldn’t seem more different. One produces sound waves; the other produces applications. One lives in the frequency domain; the other in the logic domain.
But spend enough time in both worlds, and you start seeing the same patterns everywhere.
Modulation is Composition
In FM synthesis, you have operators, simple oscillators that generate basic waveforms. Alone, each one is unremarkable. A sine wave. A saw wave. Nothing special.
The magic happens when you connect them. One operator modulates the frequency of another, and suddenly you get timbres of extraordinary complexity. Chain four operators together with feedback, and you can create everything from electric pianos to metallic percussion to evolving pads.
Software works the same way. Individual functions are simple. A sort here, a filter there. But composition, connecting small, focused units into larger systems, is where the real power lives.
// FM synthesis, conceptually:
output = sin(carrierFreq + modulationIndex * sin(modulatorFreq * t))
// Software composition, conceptually:
output = transform(filter(sort(data)))Both are about combining simple things to create complex results.
Feedback Loops
FM synthesizers often include feedback paths, where an operator’s output routes back to modulate itself. Used sparingly, this adds warmth and character. Used aggressively, it creates noise and chaos.
Software has the same dynamic. Feedback loops (recursion, event-driven architectures, reactive state) are incredibly powerful when controlled. But without careful management, they create the developer’s equivalent of noise: infinite loops, race conditions, and cascading failures.
The lesson from FM synthesis is clear: feedback is a feature, not a bug, but it demands respect and intentional design.
Preset Banks vs. Libraries
Every FM synthesizer ships with preset banks, carefully designed starting points that demonstrate the engine’s capabilities. Good presets aren’t just sounds; they’re examples of what’s possible.
Software libraries serve the same function. A well-documented library with good examples isn’t just a tool, it’s an invitation to explore. It shows you what’s possible and gives you a foundation to build on.
The Takeaway
Thinking across disciplines isn’t about forced metaphors. It’s about recognizing that problem-solving patterns are universal. The same principles that make a great FM patch (simple components, thoughtful composition, controlled feedback) make great software.
And vice versa. The engineering mindset (systematic debugging, version control, iterative refinement) makes for better music production.
That’s the Fractured Mosaic philosophy: let every discipline inform every other one.
What patterns do you see across your own disciplines? We’d love to hear about it.