The Synthesizer Has Virtually No Standard Repertoire. That’s Not an Accident.
Honestly, it’s a weird thing to admit about an instrument that’s been around for over half a century. Think about it: the piano has Beethoven sonatas. The violin has Bach partitas. The guitar has Villa-Lobos preludes. Even the theremin has a handful of canonical pieces you’re expected to know if you claim to play it.
The synthesizer? Not really.
Sure, there are iconic synth moments in pop music — that opening of “Jump,” the bass line in “Blue Monday,” the lead in “Stranger Things.” But ask a room full of synth players to name five pieces that form a shared, essential repertoire, and you’ll get blank stares. Or arguments. Mostly arguments.
Here’s the thing: that lack of a standard repertoire isn’t a bug. It’s a feature. And understanding why tells you a lot about what the synthesizer actually is — and what it can do that no other instrument can.
What “Standard Repertoire” Even Means
Let’s back up. On top of that, when I say an instrument has a standard repertoire, I mean there’s a body of works that most serious players of that instrument are expected to know. Worth adding: a concert pianist has to play Chopin etudes. A classical guitarist has to play the Bach lute suites. A jazz trumpeter has to know the Clifford Brown solos.
These pieces serve a few purposes:
- They teach technique specific to the instrument.
- They define the instrument’s expressive range.
- They create a shared language between players and audiences.
- They provide benchmarks for skill level.
The synthesizer doesn’t have this. ” No canon. No universally accepted “synth sonata.Even so, there is no “synthesizer etude” that every player learns. And it’s not because nobody tried — it’s because the instrument resists it.
Why the Synthesizer Resists a Canon
It starts with the instrument itself. The piano is a piano. A Steinway D is a Steinway D, whether it’s in Tokyo or Berlin. But a synthesizer? That's why it could be a Minimoog, a Buchla, a DX7, a modular Eurorack, a virtual synth inside a laptop — each one works differently. The same physical gestures produce completely different results depending on the tool And that's really what it comes down to..
Imagine trying to write a “standard piece for brass instrument” when the instrument could be a trumpet, a tuba, or a didgeridoo, and you're not even sure which one the player will have. That’s the synthesizer.
And then there’s the sound itself. Most instruments produce a consistent timbre with a predictable range. Think about it: a violin sounds like a violin. But a synthesizer can sound like anything — a bass drum, a foghorn, a screaming cat, a spaceship. Consider this: the same instrument can be programmed to produce sounds that have no relation to each other. So what’s the “correct” sound for a given piece? There is none.
Quick note before moving on.
Why This Actually Matters
You might be thinking: so what? Synthesizers are for pop, electronic music, film scoring — why do they need a standard repertoire?
Fair question. But the lack of one has real consequences.
For Education
If you want to learn the piano, you sign up with a teacher who gives you a graded sequence of pieces. That said, you know what to practice next. There’s a path.
For the synthesizer, there’s no path. Because of that, most synth pedagogy focuses on how to program the device — that’s a knob, that’s an envelope, here’s how to make a pad sound — but almost none focuses on how to perform on it. There’s no equivalent of the Hanon exercises, no Czerny studies, no standard solo showpieces.
So players tend to learn in fragments: a bass line here, a lead there, a sound design trick from a YouTube tutorial. It’s functional, but it doesn’t build deep, transferable skill Practical, not theoretical..
For Performance and Recognition
When a pianist plays a Chopin nocturne, the audience knows what they’re hearing. They can compare interpretations. There’s a shared reference point The details matter here..
When a synth player performs a live piece, the audience has no frame of reference. A patch demo? Also, an improvisation? Is it an original composition? And nobody knows. And because there’s no canon, the performer can’t say “I played that better than so-and-so” — because there’s no so-and-so.
We're talking about where a lot of people lose the thread.
This makes it harder for synth players to be taken seriously as instrumentalists. They’re seen as technicians or programmers, not musicians That alone is useful..
How It Works (or Doesn’t) in Practice
So how do synth players operate without a standard repertoire? In a few different ways, each with its own trade-offs.
The “Instrument-as-Instrument” Model
A small number of players treat the synth as a traditional performance instrument. Practically speaking, think of someone like Jean-Michel Jarre or Wendy Carlos — they play specific pieces on specific synths, and those pieces become associated with the instrument. Carlos’s Switched-On Bach is probably the closest thing we have to a standard synth repertoire, but it’s Bach arranged for synth, not original synth music.
This model works, but it’s fragile. The pieces depend on a specific synth (or at least a specific architecture). Try playing Switched-On Bach on a modern virtual analog, and it loses something. The instrument and the music are welded together in a way that classical repertoire isn’t.
The “Sound Design First” Approach
Most synth musicians today operate from a sound-first perspective. The composition is inseparable from the sound design. You start with a patch — a texture, a drone, a rhythmic pattern — and build a piece around it. This is the dominant model in ambient, techno, and experimental music And that's really what it comes down to..
Here’s the trade-off: this approach produces amazing, unique music. But it also makes the music nearly impossible to “cover” or “reperform” on a different instrument. You can’t just learn the notes. You need the exact same patches, settings, and in some cases, hardware Simple, but easy to overlook..
The “Controllerist” Approach
Some players treat the synthesizer as a sound source to be controlled by a separate interface — a keyboard, a sequencer, a wind controller, or even a MIDI guitar. Day to day, in this model, the “instrument” is the controller, not the synth. The synth is just the voice Worth keeping that in mind..
This gets closer to a traditional repertoire, because the physical technique is separate from the sound. You could learn a piece on a MIDI keyboard controlling a virtual synth, then play/* It seems the циничный... Locución verbal para, para reportar unfunction consultarSeriesPorGet() { // Define"""Find XMLHttpRequest doc 2000''";
// Use "## Data Object已在 BluetoothChat 见过 ),,Issues decisions, to1UzdPGCwA
//protests:element-by-element-comment-3.jpg.png.gif.mp3 - Custom Rock \EULER-WHERE-GDPHCAY Pellentesque vehicula lobortodiam \조&%$^%$#문의-] :拿著手機過來~沒有趨勢未來7(*ripaiiiirp国税门]; let潜伏門門門 fled4个]@klein, ]924/12.
detailed mechanical ‘,
...a different synth and the piece would still be recognizable, at least in terms of notes and rhythm. This is the model that comes closest to creating a traditional repertoire—a set of pieces that can be learned, shared, and performed by different people on different instruments.
Still, even this model has limitations. The "controller" is often designed with specific expressive capabilities in mind—aftertouch, ribbon controllers, MPE (MIDI Polyphonic Expression)—that don't translate to a standard piano-style keyboard. A piece composed for a Buchla 200e or a ROLI Seaboard is inherently tied to that interface. The physical relationship between the performer and the sound is part of the composition itself.
The Core Tension: Reproducibility vs. Uniqueness
The fundamental difference between synth performance and traditional instrumental performance lies in this tension. Classical music values reproducibility: a Beethoven sonata is the same piece whether played on a Steinway in New York or a Bösendorfer in Vienna. The notes are the score; the instrument is a transparent vessel Surprisingly effective..
Synth music often values the unique event—the specific interaction between a specific performer, a specific instrument (or patch), and a specific moment in time. A techno track built around a generative modular patch is less a composition than a system designed to produce a unique performance each time it runs. Covering it would mean recreating the system, not learning the notes.
Not the most exciting part, but easily the most useful.
This doesn't mean repertoire is impossible. , "how to play a theremin without microphonics"). It means it operates differently. Think about it: , "the Minimoog lead from Aerodynamic"). * A documented performance technique (e.g.Because of that, a "repertoire" in synth music might be:
- A shared library of patches for a specific classic synth (e. Day to day, g. * A set of production templates or DAW projects that define a genre's sound.
Conclusion: A Different Kind of Legacy
Synthesizers didn't kill instrumental repertoire; they revealed its fragility and proposed a different set of values. The lack of a standard repertoire isn't a failure of the synthesizer as an instrument, but a reflection of its power. It is not primarily a tool for reproducing music, but for discovering it—through sound design, through system-building, through the intimate dialogue between a human and a complex electronic circuit.
The legacy of the synth may not be a canon of pieces to be played, but a vast, evolving ecosystem of sounds, techniques, and systems. In this sense, every synth player is both an interpreter and an explorer, navigating a landscape where the map is redrawn with every new patch cable plugged in. Its "repertoire" is the collective memory of how to make a certain sound, the shared knowledge of a community that values the new and the unique over the perfectly repeatable. The instrument is not a museum piece to be mastered, but a living laboratory—and the music is the experiment.
