This content is currently under development. If you are an editor, enter your password.
From Score to Mix — A Complete Walkthrough
You have the tools. Strings, woodwinds, brass, percussion, voice leading, programming, mixing — eleven chapters of technique. This chapter is where you use them all on a single piece of music, from the first read of the score through the final mix bus.
The piece is “It Is Well With My Soul,” a hymn that works well for this purpose because it starts simple — four-part SATB harmony, no rhythmic complexity, every voice moving in whole notes and half notes — and the orchestration decisions are what make it interesting. The melody is not the challenge. The arrangement is.
This chapter follows that project through its stages, not as a step-by-step tutorial but as a walkthrough of the decisions that arise when you take a piece from notation to audio. Along the way, it connects to concepts from every earlier chapter in this guide.
Starting From the Score
Choosing the Source
“It Is Well With My Soul” exists in dozens of published arrangements — simple piano/vocal hymnal versions, SATB choir settings, full orchestral arrangements. It works well as a study piece because the harmonic language is rich enough to sustain orchestral treatment but simple enough that the arranging decisions remain the focus. The notes are not the challenge. What to do with them is.
The starting point was a standard hymnal voicing: soprano melody, alto, tenor, and bass in traditional SATB spacing. Four voices, four lines, every chord in root position or first inversion. Clean. Predictable. The kind of material that sits on the page and waits for you to make something out of it.
Reading the Hymn
Before you orchestrate anything, you need to understand what you are orchestrating. With a hymn, that means identifying:
- The harmonic rhythm. How often do the chords change? In a hymn, typically every beat or every half bar. This tells you how active your inner voices need to be.
- The cadential structure. Where are the phrase endings? Hymns are phrase-based music — four bars, cadence, four bars, cadence. Your orchestration should breathe with these phrases, not fight against them.
- The emotional arc. Even a hymn has dynamic shape. “It Is Well With My Soul” builds from a quiet, personal first verse to a broader, more declarative final verse. That arc needs to be reflected in the orchestration — not just in the dynamics, but in which instruments are playing.
Choosing a Voicing Strategy
The SATB hymnal setting gives you four voices. An orchestra gives you dozens of instruments. The first decision is mapping: which instruments carry which voices, and how does that mapping change across the piece?
Start with strings. The string section maps directly onto SATB — Violin I takes the soprano, Violin II the alto, viola the tenor, cello the bass — and this gives you a working arrangement almost immediately. The bass can double the cello an octave lower for weight, or it can sit out during quiet passages and enter as the arrangement builds.
This is the template technique from Chapter 1 at work. You built a template with all your instruments routed, panned, and ready. Now you use it. The strings go in first because they are the foundation, and once the strings sound right, you know the harmonic and melodic material is working before you start adding color.
MIDI Programming
Getting the Notes In
There are two approaches to entering the notes.
From notation software: If you have the score in Dorico, MuseScore, Finale, or a similar program, you can export MIDI and import it into your DAW. The advantage is accuracy — every note is exactly where the score says it should be, with correct pitches, correct durations, and correct timing. The disadvantage is that the result sounds mechanical, because notation software exports quantized MIDI with flat velocity and no expression data. You will need to program all the performance details after import.
Direct MIDI input: Playing the parts into your DAW from a keyboard, either in real time or step-by-step. This approach introduces performance imperfections — timing variations, velocity differences, natural phrasing — that can sound more musical than a rigid import. The tradeoff is accuracy. If you are working from a score, you need to check every note against the original, especially for transposing instruments.
Both methods work. Step input from the score is precise but lifeless. Real-time input is expressive but error-prone. Either way, the raw notes are just the starting point.
Applying Articulations
Once the notes are in, they need to sound like instruments, not like a keyboard triggering samples. This is where your work from the programming chapters pays off.
For strings in a hymn arrangement:
-
Legato is the default articulation for sustained passages. Long notes connecting smoothly, one bow stroke flowing into the next. In BBC Symphony Orchestra, select the legato patch and make sure the note endings overlap slightly so the library’s legato scripting engages. If notes are separated by even a few ticks, the library may trigger a new bow attack on each note rather than a smooth connection.
-
Staccato or spiccato might appear in a rhythmically active passage — a descant, a countermelody, a pizzicato bass line in a lighter verse. Switch articulations using keyswitches or by loading multiple articulation patches on separate tracks.
For brass, the same principles apply but the stakes are higher. A brass chord with flat velocity and no expression data sounds like a keyboard preset. Real brass players breathe, swell into notes, and taper off at the end of phrases. Your CC data needs to replicate that shape.
CC Data: Expression, Modulation, Volume
Continuous Controller data — MIDI messages that control parameters like expression (CC11), modulation (CC1), and volume (CC7) in real time. Used to shape the dynamics and timbral evolution of virtual instrument performances.
This is the work that separates a rough MIDI sketch from a convincing mockup. CC programming is the single biggest factor in whether a virtual orchestra sounds real or robotic.
For a hymn arrangement, the CC programming follows the phrase structure:
CC11 (Expression) controls the dynamic level of each note. In a hymn, each phrase has a natural contour — it grows toward the middle and tapers at the cadence. Program this by drawing CC11 curves that rise and fall with the phrase. Do not draw straight lines. Real dynamics are never perfectly linear.
CC1 (Modulation) controls timbral intensity in most orchestral libraries. Higher modulation values produce a brighter, more intense tone (more bow pressure on strings, more air on winds). Coordinate this with expression — when a phrase swells, both expression and modulation should rise together, but they do not have to move in lockstep. Sometimes the tone brightens (modulation up) while the volume stays relatively constant, creating a sense of increasing intensity without getting louder.
CC7 (Volume) sets the overall level of the instrument and is generally left static once set during the template stage. Use CC11 for musical dynamics, not CC7. If you use CC7 for performance dynamics, you will fight with your mix faders later.
Spend real time on this. Program expression and modulation for chord progressions until drawing curves that follow musical phrases becomes second nature.
Velocity
Velocity affects the initial attack of each note. In most orchestral libraries, velocity changes both the volume and the character of the attack — a high-velocity string note has a sharper, more aggressive bow attack, while a low-velocity note has a softer, gentler start.
For a hymn, velocity should be relatively consistent within a phrase, with subtle variations on stressed beats and cadential notes. The expressiveness comes from the CC data, not from wild velocity swings. Batch-edit velocity to establish a baseline (see the velocity batch editing section in Chapter 6), then go through and make individual adjustments where a note needs to speak differently.
Building the Arrangement
Verse by Verse
A hymn has multiple verses, and the simplest way to make a full orchestral arrangement from hymn material is to orchestrate each verse differently. This creates a natural arc — the arrangement grows as the piece progresses, adding instruments, complexity, and weight.
A common shape for a four-verse hymn:
- Verse 1: Strings alone. SATB voicing, simple and exposed. Let the melody carry the verse with minimal accompaniment. This establishes the material and gives the listener the hymn in its simplest form.
- Verse 2: Add woodwinds. Maybe the oboe takes the melody while the strings shift to sustained pads underneath. Or the flute doubles the violin melody an octave higher while the clarinet fills in the alto line. The texture thickens but remains lyrical.
- Verse 3: Add brass. Not at full volume — horns sustaining harmonic tones underneath the strings and woodwinds, adding warmth and weight. Or a trumpet carrying the melody with the strings providing harmonic support beneath. This is where the arrangement starts to feel substantial.
- Verse 4: Full orchestra. All sections engaged, percussion reinforcing the strong beats, the melody doubled across multiple instruments for maximum projection. This is the climax of the arrangement. The timpani enters, the brass opens up, and the full weight of the orchestra lands.
This is not the only way to structure it. You might start with a solo instrument — a viola solo opening the piece over sparse accompaniment — and build from there. You might drop the texture back for a middle verse — full orchestra for verse 2, stripped back to solo clarinet for verse 3, then full return for verse 4. The point is that the orchestration tells a story that parallels the text.
Texture and Weight Across Sections
Each section of the orchestra has a different weight. Adding horns to a string passage does not just add volume — it changes the harmonic density, the timbral center, the sense of physical space. You learned this in the individual section chapters, but now you need to manage it across sections simultaneously.
When all four sections play at once, the natural tendency is toward thickness. Every instrument adds overtones, every doubled note adds energy, and the result can become a wall of sound that lacks definition. The antidote is selective scoring — even in a tutti passage, not every instrument needs to play every beat. Rests within a section during a tutti create space for other sections to be heard.
Apply this to “It Is Well.” The full orchestra should play together only at specific moments — the final cadence of the last verse, the climax of the bridge. Everything leading up to those moments involves careful addition and subtraction of instruments. The full hit is powerful precisely because the listener has been hearing something less than full for most of the piece.
The Mix
Setting Up the Session
Your orchestral template from Chapter 1 should already have the routing structure you need: section buses for strings, woodwinds, brass, and percussion, an orchestra bus, a solo bus, and a reverb bus with a hall reverb on a pre-fader send.
For “It Is Well,” the routing followed this structure:
- Individual instrument tracks route to section buses
- Section buses route to an orchestra bus
- The orchestra bus routes to the stereo output
- A solo bus (used for the featured viola in the opening) routes independently to stereo output
- A reverb bus (convolution reverb with a small-to-medium concert hall IR) receives pre-fader sends from each section bus
- If there is a vocal, it gets its own vocal bus with its own reverb send, separate from the orchestral routing
Build this routing structure from scratch before you touch a fader. A common question at this stage: why should the reverb send tap the signal before the fader rather than after? The answer, as covered in Chapter 11, is spatial consistency. When you automate the orchestra bus to create dynamic swells, the reverb level stays constant, maintaining the illusion that the orchestra is in a fixed physical space. The room does not get bigger when the orchestra plays louder.
Levels
Start with the strings. They are the foundation. Get the string section balanced internally — Violin I, Violin II, viola, cello, bass sounding like a cohesive section — before bringing in anything else. Then add woodwinds and balance them against the strings. Then brass. Then percussion last.
When you compare your mix to a professional reference, one of the biggest differences is often in how the stems are grouped. Routing with fewer buses and more individual processing gives you less control at the section level. The lesson: routing decisions are mixing decisions. How you organize your session determines what tools you have available later.
Reverb
One reverb for the whole orchestra. Load a convolution reverb with a small-to-medium concert hall impulse response — something that creates a realistic hall sound with enough tail to provide depth and cohesion without washing out detail. Space Designer, Valhalla Room, Altiverb, or any quality convolution reverb with well-recorded hall IRs will work.
A common mistake: using individual reverbs on different sections, which creates a disjointed spatial impression. The instruments need to feel like they are in a room together, not pasted next to each other. Multiple reverbs mean multiple rooms, and an orchestra does not play in multiple rooms.
Automation
Automate at the bus level, not the track level. The orchestra bus gets volume automation that follows the emotional arc of the piece — rising into swells, pulling back for quiet passages. The section buses get individual automation only when a section needs to move independently of the rest of the orchestra.
A common pitfall is drawing step-like automation — volume up for a section, volume down for the next — which sounds blocky, like someone is switching between presets. Good orchestral automation looks like breathing: smooth curves that rise and fall with the music, tied to the inhale and exhale of the phrase structure. That approach, described in Chapter 11, produces dynamics that feel conducted rather than edited.
The automation should follow the arrangement’s arc. Verse 1 (strings alone) sits at a lower level. As instruments enter in subsequent verses, the bus levels come up. The final verse at full orchestra is the loudest, with the automation peaking at the climactic cadence and easing back for the closing bars.
EQ, Compression, and the Mix Bus
Keep mix bus processing minimal: a multiband compressor on a gentle preset and a limiter. The arrangement does the heavy lifting. If the brass is too loud, the fix belongs in the orchestration (adjusting the dynamic marking or the voicing), not in the EQ.
This is the advantage of being both the composer and the mixer — you can fix problems in the source material. If a frequency range is building up, you can go back to the MIDI and thin out the section that is causing the buildup. A mix engineer working with recorded stems does not have that option. You do.
Try this exercise: bounce your orchestral arrangement to stems — recorded audio, not MIDI — and mix the piece from the audio only. You cannot change the notes. You cannot adjust velocity. Every balance problem must be solved with faders, EQ, compression, and routing.
Working with stems forces you to hear what is actually there and respond to it, rather than going back to fix it in the MIDI. Both skills matter. But the stems exercise teaches something that MIDI programming alone cannot: the sound of a real orchestra is not hyper-detailed. You hear the wash of the orchestra, and then whatever is important at a particular moment comes forward. That instinct — the understanding that blend is part of the sound — comes from listening to live orchestral music, and it should shape your approach to the mix.
A Recommended Study Path
The material in this guide follows a deliberate arc. If you are working through it on your own, here is how the pieces fit together:
Phase 1: Score literacy and instruments. Start with Chapters 1-3. Build your template, learn to read a score, and get to know the sections. A good first exercise: mock up a passage from Stravinsky’s “Rite of Spring” — specifically the “Dance of the Young Girls.” Enter it into your DAW from the published score. Deal with transposing instruments, read complex rhythms, and confront the reality that orchestral notation is a specialized skill. This is not about creating a polished mockup. It is about learning to translate notation into MIDI.
Phase 2: Voice leading and string programming. Chapters 4-6. Three styles of string voicing (open spacing, closed spacing, and three-part higher voicings), the rules of voice leading, and then the practical application: programming chord progressions with correct CC data. Write 30-60 seconds of string chord progressions and program expression and modulation data for each note.
Phase 3: Arrangement and mixing. Pick a hymn — “It Is Well With My Soul,” “Be Thou My Vision,” “Amazing Grace” — and orchestrate it. Build your own mix session, apply your own routing decisions, choose your own reverb, and produce your own mix. Then compare against a professional orchestral recording. Common issues that surface at this stage: timpani too loud at the climax, reverb space too large, percussion instruments (like glockenspiel) sitting in front of the strings instead of behind them. These are the kinds of problems that only become visible when you compare your work against a reference.
Phase 4: Winds and brass. Chapters 7-9. Write chord progressions for brass choir — horns, trumpets, trombones, and tuba — applying the doubling ratio (two horns equal one trombone in volume) and the spacing rules from the brass chapter. Adjust voicings, add expression data, and hear how modulation changes the brass tone.
Phase 5: Full score and revision. Chapters 10-12. Bring everything together. Revise your arrangement. Mix it again. Compare it to a professional recording again. Each revision will be better than the last.
Approaching Your Own Projects
This walkthrough provides a template for how to approach any orchestral arrangement:
1. Start with the material. Understand the harmonic structure, the phrase structure, and the emotional arc before you touch your DAW. If the source material is a hymn, a lead sheet, a piano reduction, or a melody with chord symbols, spend time with it on paper first. Identify the cadences, the climactic moments, the quiet passages.
2. Map the voices. Decide which instruments carry which lines. Start with strings as the foundation, because the SATB mapping is direct and you can hear whether the voice leading works before you add color.
3. Build in layers. Enter the strings first and get them sounding right — notes, articulations, CC data, everything. Then add woodwinds. Then brass. Then percussion. Each layer builds on the one before it, and if something does not sound right at the string stage, adding more instruments will not fix it.
4. Program the performance. CC data is not optional. Expression, modulation, and velocity shape every note. A piece with correct notes but flat CC data sounds like a MIDI file, not like an orchestra. Budget time for this — it takes longer than entering the notes, and it is where the arrangement comes to life.
5. Mix in sections. Balance the string section internally before bringing in woodwinds. Balance the strings-plus-woodwinds against each other before bringing in brass. Add percussion last. This layered approach keeps you from chasing your tail trying to balance everything at once.
6. Automate for dynamics. The musical arc — the swells, the pullbacks, the climactic moments — happens in the automation, not in the CC data. CC data shapes individual phrases. Bus automation shapes the overall dynamic arc of the piece. Both are necessary.
7. Compare and revise. Play your mix for someone. Compare it against a professional recording. Listen for the differences in depth, balance, and spatial coherence. Then go back and make changes. Revise multiple times over several weeks. Each revision will be better than the last because you will have fresh ears on the problems.
What to Practice
- Take a hymn — “It Is Well With My Soul,” “Be Thou My Vision,” “Amazing Grace,” or any hymn with a published SATB setting — and orchestrate it from scratch. Start with strings only. Get the strings sounding musical with proper articulations and CC data before adding anything else.
- Once the string arrangement works, add one section at a time. Try adding woodwinds first for one version, and brass first for a different version. Notice how the order of addition changes the character of the arrangement.
- Mix a piece twice: once with MIDI (where you can go back and change notes), and once with bounced stems (where the audio is fixed and you can only use mix tools). Pay attention to what you reach for in each scenario. The first teaches composition-as-mixing. The second teaches mixing as a standalone discipline.
- Record your bus automation in real time rather than drawing it. Play the piece and ride the orchestra bus fader with your hand, breathing with the music. Compare the result to automation you draw manually. The real-time version will usually feel more natural.
- Find a full orchestral score at IMSLP for a piece you know well — something you have listened to many times. Follow the score while listening to a recording. Notice which instruments carry the melody at each moment, which provide harmonic support, and which are resting. Then look at the score vertically at climactic moments: what is every section doing? How does the balance on the page translate to the balance in the recording?
- If you have completed the Mixing and Synthesis Tools, revisit the routing and bus concepts in the context of orchestral mixing. The principles are the same. The application is different.
This Course
- 1. The Orchestral Template
- 2. Reading the Orchestra
- 3. Meet the Sections
- 4. Voice Leading Fundamentals
- 5. Writing for Strings
- 6. Programming Strings
- 7. Writing for Woodwinds
- 8. Writing for Brass
- 9. Programming Woodwinds and Brass
- 10. Percussion and the Full Score
- 11. Orchestral Mixing
- 12. From Score to Mix — A Complete Walkthrough
- 13. Sources and Further Reading
Upcoming Events
Feedback or corrections
© 2026 Beat Kitchen School — beatkitchen.io. Licensed under CC BY-NC-SA 4.0. Free to share and adapt for non-commercial purposes with attribution.