Overview
Orchestral samples are recorded by real players in real halls, so the raw material is not the problem. Mockups give themselves away through how the notes are triggered: every note starting at the same instant with the same shape, no sense of a bow running out, dynamics changing in steps rather than continuously, and a balance nobody in a hall would produce. Every one of those is fixable, and none of the fixes needs a better library.
What You Need
- Any orchestral library, including the one you already own
- A sequencer with a piano roll and continuous controller lanes
- A reference recording of real players performing something similar
- Headphones or monitors telling you the truth about reverb, which small speakers do not
Steps
Break up the note starts
Real players do not begin together to the millisecond, and the ones playing lower and heavier instruments start later. Move note starts apart by small amounts, more for basses and low brass, less for violins and flutes. A spread of twenty to sixty milliseconds across a chord removes the machine-gun quality immediately. Randomising slightly within a section helps further, because a section is a group of people rather than one loud person.
Fix the sample delay before you fix anything else
Many orchestral patches begin with the sound of the instrument starting, and the attack takes real time. A legato string patch might speak eighty milliseconds after the note is triggered. Play it on the beat and it arrives late. Every serious mockup pushes such notes earlier so the audible attack lands where intended, and a library with mixed patches needs a different offset per patch. This single correction fixes more perceived sloppiness than any amount of expression editing.
Write the dynamics as a curve, not as a value
The strongest tell of a mockup is dynamics arriving in steps. Real players change intensity continuously through a note and across a phrase. Draw the expression controller as a moving line rather than setting it once per note. A long held string note should swell and settle a little even when the score says nothing. Recording the controller live with a fader or a wheel produces better results than drawing, because a hand moves in ways a mouse does not.
Separate dynamics from volume
Two controls do different jobs and beginners collapse them into one. The expression or dynamics control changes which sample layer plays, so a louder value gives you a brighter, harder tone with more bow or more air. Volume changes level without changing tone. A crescendo made with volume alone gets louder without getting more intense, which is the sound of a recording being turned up rather than an orchestra playing harder. Use dynamics for the musical change and volume only for balance.
Give the strings bow changes and the winds breath
A string phrase running twelve bars without a bow change is physically impossible, and the ear knows even when the listener cannot say why. Break long lines with small dips in dynamics where a bow would turn. Wind and brass players breathe, so leave gaps at phrase ends rather than running lines together. These absences are what make a written line sound performed.
Balance the way a hall balances
Sample libraries deliver every section at a similar recorded level, which is nothing like a hall. Sixty strings are loud, two oboes are not, and a single horn cuts through both. Pull woodwinds up relative to strings in tutti passages, hold brass back until it needs to arrive, and let the strings carry more than feels right in isolation. Compare against a real recording rather than mixing to taste, because taste calibrated on mockups reproduces mockups.
Put everything in one room
Convincing orchestral sound comes largely from every instrument sharing an acoustic. Libraries recorded in different halls, or dry libraries with individual reverbs, place players in separate spaces and the result never coheres. Send everything to a single reverb representing the hall, adjust the amount per section by seating position rather than by taste, and keep the front-to-back sense: strings closer, percussion further away.
Pro Tips
- Listen to a real recording of the same instrumentation immediately before checking your mockup. Ears drift within minutes and a reference resets them.
- Record controller moves in a performance pass rather than drawing them. A hand on a fader produces motion no drawn curve reproduces convincingly.
- Solo a single line and ask whether a person is able to play it. Unplayable leaps, impossible ranges and lines with no breath are audible even inside a full texture.
- Keep a template with your offsets, balances and reverb sends already set. Rebuilding those decisions per project wastes the hours you should spend writing.
- Fewer instruments played convincingly beat a full orchestra played mechanically. A well-handled string quartet sounds real, and a whole mechanical orchestra sounds like a demo.
- Check the mockup on small speakers as well. Overdone reverb survives good monitors and turns to mud on a laptop, which is where most people will hear it.
Knowledge Base
What You'll Learn
The table below lists the tells in the order listeners notice them. The section after it covers the control confusion behind most unconvincing crescendos.
What gives a mockup away
| Tell | Why it happens | Fix |
|---|---|---|
| Notes start together to the millisecond | Quantised entry | Offset by instrument weight, 20 to 60 ms spread |
| Everything arrives late | Sample attack time not compensated | Push notes earlier per patch |
| Dynamics change in steps | One controller value per note | Draw or perform a continuous curve |
| Crescendo gets louder, not stronger | Volume used instead of dynamics | Use the dynamics control for intensity |
| Strings never change bow | Long lines written unbroken | Small dips where a bow would turn |
| Woodwinds vanish in tutti | Library balance, not hall balance | Raise winds, hold brass back |
| Sections sound like separate rooms | Different halls or separate reverbs | One shared reverb, sends by seating |
Dynamics against volume, the distinction worth learning first
Orchestral libraries record each instrument several times at different intensities, from quiet to loud. The dynamics control chooses between those recordings and blends them. Moving it does not only change how loud the result is, it changes the tone: more bow noise, more air, a harder attack, a brighter spectrum.
Volume is a fader. It changes level and nothing else. A quiet sample turned up is a quiet performance played back loudly, and it sounds exactly like one.
So a crescendo written with volume produces the sound of someone turning up a recording, while the same crescendo written with the dynamics control produces players leaning in. Almost every unconvincing swell comes from this confusion, and the fix costs nothing but knowing which lane to draw in.
Where This Fits
This sits under Scoring for Picture, the pillar for the composing side of the site. Tempo Maps and Hit Points covers getting the written cue to land on the edit, and Mixing a Full Song covers the balance and space decisions carrying over into a final mix.
FAQ
Q: Why do my orchestral mockups sound fake?
A: Usually four things at once: every note starting at the same instant, no compensation for sample attack time, dynamics moving in steps rather than curves, and each section sitting in a different acoustic. All four are fixable without changing library.
Q: What is the difference between the dynamics control and volume?
A: Dynamics chooses between recordings made at different intensities, so it changes tone as well as level. Volume only changes level. A crescendo made with volume sounds like a recording being turned up.
Q: How much should I offset note starts?
A: Roughly twenty to sixty milliseconds across a chord, with heavier and lower instruments later than lighter ones. Small random variation within a section helps, because a section is many players rather than one.
Q: Do I need an expensive library?
A: No. Technique separates convincing mockups from unconvincing ones far more than the library does. A modest library handled well beats an expensive one triggered mechanically.
Q: Should every instrument use the same reverb?
A: Broadly yes. A shared hall is most of what makes an orchestra sound like one ensemble. Vary the send amount by seating position rather than giving each section its own space.
Translate this page
- Español
- 简体中文
- हिन्दी
- العربية
- Português
- Français
- Deutsch
- 日本語
- Русский
- Bahasa Indonesia
- 한국어
- Italiano
- Türkçe
- Tiếng Việt
- Polski
- Nederlands
Machine translation provided by Google Translate, on Google’s servers. We do not check these translations and they will get technical terms wrong. The English page is the authoritative one. Following a link sends this page’s address to Google. Your browser may also offer to translate this page itself, which keeps the request on your device.