简体中文
EnglishWhat Are Synthesizers and How Do You Choose a Software Synth?
Updated
A synthesizer is an instrument that generates audio electronically rather than by vibrating a physical string or column of air. You shape that raw electronic signal into a usable sound using filters, envelopes, and modulation. If you make music on a computer, a software synthesizer (a VST/AU/AAX plugin) gives you that same signal path inside your DAW, usually with more voices, more modulation options, and instant recall of every setting than a comparably priced hardware unit. Choose a software synth by matching its synthesis method and preset library to the sound you actually want, then confirm it runs comfortably on your machine and in your plugin format.
How a Synthesizer Makes Sound
Almost every synth, hardware or software, follows the same basic chain:
- Oscillator (VCO/DCO/digital) — generates the raw tone. Waveform choice (saw, square, sine, wavetable, sample) sets the basic character.
- Filter (VCF) — removes or emphasizes frequencies. A low-pass filter that closes over time is the classic "warm synth" move.
- Amplifier (VCA) — controls loudness.
- Envelope (ADSR) — how a sound starts, sustains, and fades. Attack, Decay, Sustain, Release.
- LFO and modulation matrix — slow or fast movement applied to pitch, filter, or anything else, which is what makes a patch sound alive rather than static.
If you understand those five blocks, you can read the front panel of nearly any synth, from a vintage analog clone to a modern wavetable instrument.
Main Synthesis Methods and What They're Good For
| Method | How it works | Typical strengths |
|---|---|---|
| Subtractive | Rich waveform, then filter it down | Basses, leads, pads; the classic analog sound |
| Additive | Builds tone from many sine partials | Bells, metallic and evolving textures |
| FM | One oscillator modulates another's frequency | Electric pianos, bright digital leads, percussive tones |
| Wavetable | Scans through stored single-cycle waveforms | Modern EDM, cinematic movement, morphing pads |
| Physical modeling | Simulates strings, tubes, or membranes | Realistic plucked and blown instruments |
| Granular / sample-based | Plays and scatters recorded audio | Textures, atmospheres, sound design |
Many modern synths blend methods. u-he's lineup, for example, spans several of these: Zebra 3 is a modular-style hybrid, Diva models classic analog circuits, Hive 2 targets fast, CPU-friendly production work, Repro recreates a specific vintage two-oscillator design, and Bazille is a semi-modular system for complex patching. That range exists precisely because no single method covers every job.
Hardware vs. Software Synthesizers
Software synths win on cost per voice, total recall (your patch saves with the project), unlimited instances, and integration with your DAW's automation. They also let you run several different synth engines without buying several keyboards.
Hardware synths win on hands-on control, zero CPU load, and a fixed, predictable workflow that some players find more inspiring. They also work with no computer at all.
The practical rule: if you produce in a DAW, start with software. Add hardware later if you find yourself wanting physical knobs or a computer-free setup. The two aren't mutually exclusive — plenty of studios run software synths sequenced from a hardware keyboard.
How to Choose a Software Synth
Work through these in order, because the first two eliminate most options quickly.
1. Match the synthesis type to your target sound
- Want warm analog basses and pads? Look at subtractive/analog-modeling synths.
- Want glassy digital leads and electric pianos? Look at FM.
- Want modern, morphing, cinematic movement? Look at wavetable.
- Want to build unusual patches from scratch? Look at semi-modular or modular-style instruments.
2. Check the preset library and soundset ecosystem
Presets are how you learn a synth and how you get to a usable sound fast under deadline. A synth with a large, well-organized factory library and third-party soundsets is easier to live with. u-he, for instance, maintains soundsets for specific instruments — Blue Flamingo for Repro-5, Strobos for Bazille, Sugar & Spice for Hive 2 — so a given synth's usefulness grows over time rather than staying fixed at purchase.
3. Confirm compatibility before anything else
- Plugin format: VST3, AU, AAX, or standalone. Check what your DAW accepts.
- OS and CPU architecture: confirm the current version supports your system.
- CPU cost: wavetable and modular synths can be heavy. If you run many instances, a lighter engine matters more than a marginally better filter.
4. Weigh CPU load against depth
A deep modular synth can do almost anything but may limit you to a few instances. A streamlined synth may sound narrower but let you run twenty tracks. Decide based on whether you're a sound designer or a producer working fast.
5. Try before committing
Most vendors offer demo versions or free instruments. u-he's freeware line — Zebralette 3, Podolski, Triple Cheese, TyrellN6, and others — lets you evaluate the company's sound and workflow at no cost before buying a flagship product. Use demos to test CPU load in a real project, not just to audition presets.
6. Check the update and support record
A synth is a long-term tool. Regular version updates (u-he, for example, ships point releases like Zebra 3.0.2) and an active user community or forum are signs the instrument will keep working as your OS and DAW change.
A Quick Decision Path
- "I just need good sounds fast." Pick a synth with a strong preset library and simple interface — a subtractive or wavetable workhorse.
- "I want to design sounds from scratch." Pick a semi-modular or modular-style synth with a deep modulation matrix.
- "I'm recreating a specific vintage character." Pick an analog-modeling synth built around that circuit.
- "My CPU is already maxed." Pick a lightweight engine and lean on presets rather than many voices.
- "I'm not sure yet." Start with free instruments, learn the signal chain, then buy the one whose demos you kept reaching for.
The synth matters less than learning one instrument deeply. Pick a method that fits your music, confirm it runs on your system, and spend your time learning its filter and modulation behavior — that knowledge transfers to every synth you use afterward.