How to Trace Carrier and Modulator Routes When Deconstructing an FM Preset
To trace an FM preset, start at the audio output, identify the operators feeding it, and work backward through every modulation connection. Then test individual routes while preserving the rest of the patch. This gives you a practical map of which operators contribute audible layers and which shape those layers.
This workflow is for a synth user who can open a preset’s algorithm or routing matrix and wants to understand it before editing. The aim is to identify the routes responsible for the attack, sustained tone, and changing texture—not simply label every operator.
What makes an operator a carrier or modulator?
An operator’s role follows its routing. A carrier contributes to the audible output; a modulator feeds another operator and changes its sound. Yamaha explains that carriers and modulators have the same basic components: an oscillator, amplifier, and envelope generator. Their connections determine their jobs. See Yamaha’s “FM 101, Part Three: The Magic of Modulation”.
Treat these as routing roles rather than permanent operator identities. In a flexible instrument, one operator may serve both roles: Native Instruments explicitly documents simultaneous carrier and modulator operation in the FM8 Operation Manual, section 4.11.1.
For your notes, use two distinct connection labels: “modulates” and “feeds audio.” For example, write “B modulates A; A feeds output.” Reserve a third label, “feedback,” for a return connection. This avoids confusing a modulation link with an ordinary audio mix connection.
What should you record before changing the preset?
Save a separate working copy and capture the routing view. Record the selected algorithm, enabled operators, operator levels, and any visible feedback amount. Keep the original available for comparison.
Choose a repeatable audition phrase. One useful starting point is a single note at a fixed velocity, held long enough to hear the sustain and then released. Use the same note and duration for every initial comparison. Add other pitches and velocities later, after you have mapped the basic paths.
Listen once with the complete preset, then temporarily bypass effects that obscure the sound you are investigating. Record every bypass so you can restore it. FM-X, for example, includes filters, effects, and EQ after its operator-based synthesis; the complete preset can therefore contain substantial shaping beyond the operator network. Yamaha describes this in the MONTAGE M Operation Manual: Tone generator block.
Write down one question to guide the session: “Which route creates the short bright attack?” is more useful than “How does this entire preset work?” Finish that question before moving to another feature.
How do you read an algorithm diagram or FM matrix?
First establish the display’s direction. In Yamaha’s conventional algorithm diagrams, carriers occupy the bottom row, with modulators above them and connecting lines showing their destinations. Yamaha’s FM 101 explanation illustrates this with separate modulator–carrier pairs. Do not infer a route from operator numbering alone.
A matrix needs a different reading method. In FM8, trace downward from the source operator and rightward toward the destination; their intersection holds the modulation amount. Preserve the sign as well as the value when recording connections, because FM8 supports positive and negative modulation amounts. See the FM8 Operation Manual, section 4.2.6.
Build your map in this order:
- Mark every active audio route reaching the output.
- Identify the operator supplying each route.
- Find every modulator feeding that operator.
- Continue backward through those modulators’ inputs.
- Mark shared sources, feedback connections, and intermediate processors separately.
Keep the first pass structural. Record what connects to what before interpreting why the preset sounds a particular way. A visible connection is a candidate explanation; the listening tests establish its contribution under your chosen playing conditions.
How do you isolate a carrier branch without changing its modulation?
For this workflow, a branch means one audible carrier together with the operators feeding it. To hear a branch, retain its upstream modulation and remove the other branches’ audio contributions wherever the instrument provides separate output controls.
Avoid treating an operator’s master level as interchangeable with its output send. In a flexible matrix, changing the operator itself may affect several destinations. Removing only its audio-output connection is the more focused test when you want to preserve its modulation elsewhere. This follows from FM8’s documented ability to route one operator as both carrier and modulator in the FM8 Operation Manual.
If the synth offers only operator on/off switches or shared level controls, inspect the map before using them. Check whether the operator feeds anything in the branch you want to retain. When it does, note that the test changes multiple paths and interpret the result accordingly.
Use a short comparison log:
| Test | Keep unchanged | Record |
|---|---|---|
| Isolate one audio branch | Its upstream modulation | Attack, body, sustain, release |
| Restore the full preset | Original levels and routing | Where that branch fits |
| Remove one modulation connection | Carrier audio route and other inputs | Which characteristic changes |
| Restore that connection | Original amount and sign | Whether the characteristic returns |
Compare at a similar listening level when possible, and write descriptions tied to time: “short metallic onset” or “steady low layer” is more actionable than “better” or “thinner.” These are observations to make during your session, not expected results for every preset.
How do you trace stacked modulators, shared routes, and feedback?
Follow every input recursively. If C modulates B and B modulates A, stopping at B leaves part of A’s upstream structure unexplained. Mark the full stack before testing individual links.
Consider this illustrative routing map, which is not a factory preset:
| Connection | Function in this example |
|---|---|
| A feeds output | Audible carrier branch |
| B modulates A | Direct modulation of A |
| C modulates B | Upstream modulation in the A branch |
| D feeds output | Second audible carrier branch |
| B modulates D | Shared modulation source |
| C feeds back to itself | Feedback within the upstream stack |
To investigate A, remove D’s audio contribution while preserving B. Then compare the original A branch with B-to-A removed. Restore it before testing C-to-B. Changing B’s overall level would also change its contribution to D once that branch returns, so record the affected destinations before making that broader edit.
Feedback deserves its own test. Yamaha defines self-feedback as an operator modulating itself in the MONTAGE M tone-generator documentation. Mark the loop, record its amount, temporarily reduce it, and compare the same phrase. Restore it before testing another connection.
For networks with loops, stop drawing when you reach an operator already on the map. Mark the return connection instead of tracing endlessly. The useful result is a finite diagram showing the loop and its exits toward audible branches.
Why does a connected route sometimes seem inactive?
After mapping the connections, inspect the conditions controlling them. A routing diagram shows possible paths; your test note reveals their behavior at a particular pitch, velocity, controller position, and moment in the envelope.
Ableton’s Operator documentation explains that a modulating oscillator’s level strongly affects timbre, while Fixed mode makes its frequency independent of played pitch. It also documents individual oscillator envelopes and velocity controls. These are useful checks when a route behaves differently across notes or over time. See the Live 12 Instrument Reference: Operator.
Use this diagnostic sequence rather than immediately increasing a level:
- Confirm that the destination still has a path to the audible output.
- Check the source’s enabled state, level, and envelope.
- Audition the beginning, held portion, and release separately.
- Repeat at a lower and higher velocity.
- Repeat at another pitch and inspect ratio or fixed-frequency settings.
- Move relevant controllers deliberately, recording their starting positions.
Keep the conclusion narrow. If removing a route produces no clear difference during a held note, record “no clear sustain contribution under this test.” Check the onset and other playing conditions before calling the route unused.
How do you turn the route map into a useful edit?
Choose the smallest change that matches your original question. If a particular modulation connection supplies the attack character you want to adjust, test its amount first. If the timing is the issue, inspect the source envelope next. If an entire audible layer needs balancing, work on that branch’s audio contribution.
For example, suppose your tests associate an illustrative B-to-A route with a brief bright onset. Compare a modest reduction of that connection against a separate version with a shorter B envelope. The first tests modulation depth; the second tests duration. Restore the baseline between versions so you can identify which change addresses your goal.
Reintroduce bypassed processing one stage at a time, then replay the phrase at several pitches and velocities. Finally, compare the edited copy with the original in the musical passage where you intend to use it.
Finish with a compact record: the output carriers, their upstream routes, any shared sources or feedback, the conditions you tested, and the parameter you changed. You now have a map that supports a specific edit and a repeatable way to investigate the next feature of the preset.