Why Your Orchestral Mockup Sounds Fake, and How to Fix It
- Hagai Davidoff
- Jun 13
- 6 min read
A practical guide for composers working in Cubase
By Hagai Davidoff, Steinberg Certified Trainer, composer and sound designer.
The short answer: your mockup sounds fake because of how the samples are performed, not what notes you wrote. Flat dynamics, missing articulations, mechanical timing, and poor voicing account for nearly every case of "sounds like MIDI." This guide covers all four, explains the fix for each, and introduces the workflow that prevents the problems from building in the first place.
The Problem Is Not Your Samples
Most composers assume a more expensive sample library will fix their mockup. It will not.
A mid-range library performed well will always sound more convincing than a premium library performed badly. The difference between a mockup that sounds like a machine and one that sounds like an orchestra is not in the samples. It is in the performance decisions made after the notes are in the MIDI editor.
This matters because it changes where you invest your time. Learning to perform samples is a learnable, improvable skill. Buying better gear is a purchase that solves nothing if the underlying problem is not addressed.
Start With a Workflow: The SSO Method
Before fixing individual elements, the work needs structure. Without a clear workflow, a large orchestral session in Cubase becomes unmanageable quickly: dozens of tracks, automation that drifts, a sketch that falls apart the moment you try to expand it.
The SSO method divides orchestral production into three stages.
Sketch. Write the full musical idea on piano or a single lead instrument. Do not think about orchestration yet. This is where the music happens: harmony, melody, structure, rhythm.
Short Score. Divide the sketch across functional roles: bass line, accompaniment, melody, filler. You are not choosing instruments yet. You are identifying what each part does.
Orchestrate. Now assign instruments to roles. Cellos on the bass line. Horns on the accompaniment. First violins on the melody. This is also where the performance work begins: dynamics, articulations, humanization.
The sequence matters because it prevents the most common mistake in orchestral production, which is orchestrating while composing. When you do both at once, both suffer. Composing decisions get contaminated by performance concerns, and performance decisions get made before the musical shape is clear enough to make them well.
Hear the Method in Action
Before getting into the four specific problems, listen to the same theme orchestrated seven different ways. Each version makes different decisions about instrumentation, dynamics, and voicing. That range of possibility is what the third stage of SSO opens up.
The Four Suspects
When an orchestral mockup sounds unconvincing, it is almost always one of four things, or a combination.
Flat dynamics. Real musicians do not play at a constant volume. Every phrase breathes. There is a rise toward the peak and a fall at the end. A sample played at fixed velocity sounds dead because no human player performs that way. In serious orchestral libraries, CC1 controls dynamics and CC11 controls expression. Drawing these curves manually along every phrase is the single most impactful change you can make to a mockup. Nothing else comes close for the time invested.
Missing articulations. A violin can play legato, staccato, spiccato, pizzicato, marcato, and several other modes, each sounding completely different. Playing everything on a generic sustain patch loses the entire vocabulary of the instrument. Cubase handles this better than most DAWs through Expression Maps: write the articulation directly on the note, and Cubase switches the library's keyswitch automatically. If you are doing orchestral work in Cubase and not using Expression Maps, you are doing the job the hard way.
Mechanical timing. When every note lands exactly on the grid, the ear hears a machine. Real players push and pull by microseconds. The fix is humanization: move notes slightly off the grid, vary velocity between adjacent notes, and use round-robin samples where the library supports them. The ear is very sensitive to exact repetition. If the same sample fires twice in a row, it registers as synthetic immediately.
Wrong voicing. How the chord is distributed across instruments matters. Intervals in the bass register need to be open. Intervals in the upper register can be close. Doubling instruments in the wrong octaves, placing horns and strings at the same pitch and dynamic, or writing outside an instrument's strong range are all mistakes that reveal the amateur. This is classical orchestration knowledge applied to digital production. There are no shortcuts.
Fixing Dynamics First
Of the four suspects, flat dynamics causes the largest share of unconvincing mockups and has the most immediate fix.
The approach: draw CC1 curves on every orchestral track as a dedicated pass after the notes are in. Not note by note, but phrase by phrase. Identify where each phrase peaks. Draw the curve up toward that point and back down at the end. Do the same with CC11 for strings. This single pass transforms a static, mechanical texture into something that breathes.
Once the dynamics are working, articulations become the priority. The goal is never to sound realistic by default. It is to sound right at each moment. The moment a phrase needs staccato, a legato patch sounds wrong regardless of how well the dynamics are drawn.
The Cubase Advantage
Cubase has specific tools that make this workflow more efficient than most DAWs.
Expression Maps let you assign articulations in the score editor rather than managing keyswitches manually across the piano roll. For a large session with string patches carrying twelve articulations each, this is the difference between a session that stays manageable and one that does not.
The MIDI editor handles CC lane editing cleanly. Multiple CC lanes visible at once, precise curve control, and the ability to scale automation relative to existing values without overwriting them are all features that matter when you are doing detailed performance work.
The track template system lets you save a fully configured orchestral session with all routing, sends, groups, and instrument assignments in place. The first session takes time to build. Every session after that starts from a working template.
FAQ
What is an orchestral mockup?
An orchestral mockup is a virtual production of an orchestral composition built from sample libraries instead of live players. The composer writes the notes, then performs the samples using dynamics, articulations, and timing adjustments to make the result sound like a real orchestra.
Why does my orchestral mockup sound fake?
Nearly always because of flat dynamics, missing articulations, mechanical timing, or wrong voicing. Flat dynamics is the most common cause. Drawing CC1 curves along every phrase is the single change that improves most mockups the most.
Do I need expensive sample libraries to make a convincing mockup?
No. A mid-range library performed well outperforms an expensive library performed badly. The decision of which library to buy matters less than learning to perform whatever library you already have.
Which DAW is best for orchestral mockup work?
Any professional DAW can produce convincing orchestral mockups. Cubase has specific advantages for this workflow: Expression Maps for articulation management, a clean MIDI editing environment, and a strong template system. These become significant time-savers at scale.
How long does it take to learn orchestral mockup production?
With a clear method, a convincing result is achievable within a few weeks of consistent work. Without a method, it is common to spend years on the same wall of flat, plastic-sounding output. The bottleneck is almost never talent or hardware. It is structured practice on the right problems.
Do I need to read music to write orchestral music in the box?
It helps, but it is not required to get started. Most of what separates a convincing mockup from a fake-sounding one is in the performance, not in the theory. You can work on both in parallel.
What is The Cubase Method?
The Cubase Method is a course built around the complete workflow for working in Cubase at a professional level: session architecture, the SSO method applied to orchestral and hybrid production, and the performance and mixing techniques that close the gap between a mockup and a score. Launching in 2027.
The Gap Between Knowing and Hearing
Understanding what CC1 does is not the same as knowing when a phrase needs a sharper dynamic rise, when an articulation change is masking a voicing problem, or when adding one more layer makes the mix thicker rather than more convincing. Those are listening skills. They develop through practice on real material.
The Cubase Method covers the complete workflow from session setup through orchestral production and mix, which is the same system behind the production in the video above. If you are working toward that level of control in Cubase, the course is built around the problems you are already running into. Details and early access at The Cubase Method.
Comments