Learn — By WATMM Desk —

Orchestral mockups basics with sample libraries

An orchestral mockup is a MIDI performance played by sampled instruments, and it sounds real or fake mostly because of how you control it, not which library you own. This guide explains velocity layers, round robins, keyswitches and legato, the difference between velocity and the mod wheel, and a practical order of work for a first mockup. Sources checked on 31 Oct 2026.

Key facts

  • Libraries record each note at several intensities (velocity layers) and crossfade between them; a fully featured orchestral instrument can easily have half a dozen round robins per note.
  • Velocity is fixed when a note starts, so a crescendo inside a held note needs a continuous controller; Project SAM links the mod wheel (CC1) to dynamics crossfading by default.
  • Keyswitches are real MIDI notes at the very bottom or top of the range that choose the playing technique, so they are recorded in your MIDI sequence.
  • Spitfire Audio BBC Symphony Orchestra Discover has one dynamic layer and no round robins, according to Sound On Sound, so the mod wheel and velocity carry the dynamics.

An orchestral mockup is a piece of orchestral music performed by sampled instruments that you play or draw in as MIDI. Done well, it is a convincing demo of what live players could do. Done badly, it is a row of obviously identical notes. The gap between the two is mostly technique. This guide covers the handful of ideas that explain how sample libraries behave, then gives an order of work for your first mockup.

You will need a DAW and a MIDI source. If you are still choosing, our what is a DAW guide covers the basics, and MIDI controller basics helps with the keyboard side.

What is actually inside a sample library

A sample library is a large set of recordings of real instruments, mapped to MIDI notes. Sound On Sound walks through why it is so big: record every note at several loudness levels and several playing styles, and the file count climbs fast. Its example of a simple virtual violin ends up at "around 18,000 audio files".

Three mechanisms make those files behave like an instrument.

Velocity layers. The same note is recorded quiet and loud, and the sampler picks a layer from the MIDI velocity. Sound On Sound's example plays the quiet version for velocities below about 50. To avoid an audible jump between layers, the sampler can crossfade between them for "a smoother transition".

Round robins. Play the same sample twice in a row and your ear catches it, the so-called "machine gun" effect. Libraries record several takes of each note and cycle through them. Sound On Sound says "a fully-featured orchestral instrument could easily have half a dozen round robins", and some of EastWest's string instruments have as many as 16. Some instruments also offer a round robin reset button so playback is identical each time.

Keyswitches. One instrument holds many articulations, such as sustained, staccato and pizzicato. Project SAM assigns each articulation a keyswitch, and notes that "since keyswitches are actual MIDI notes, they will be recorded as part of your MIDI sequence." Sound On Sound says many libraries use "the very lowest or highest MIDI notes" for this, and admits that remembering which key does what "is far from intuitive".

Our take: keyswitches are a data-entry problem. If you place them a beat before the note they change, and keep them on their own MIDI lane or track, you can edit them without touching the notes.

Velocity is not dynamics

This is the idea that fixes the most mockups. Velocity is measured once, when the key goes down. It cannot change a note after it starts. Project SAM puts it plainly: changing the dynamic level after the start of a note, for a crescendo or diminuendo, "is not possible using velocity".

So most sustained orchestral patches use a continuous controller instead. In Project SAM's libraries the modulation wheel, CC1, is "linked by default to cross-fade dynamics", and expression, CC11, is "linked by default to a secondary amp modulator that can be used alongside volume". Their naming helps too: sounds with dynamics on velocity often carry a VEL suffix, and sounds with dynamics on a controller carry MOD or DYN.

What this means in practice:

  • For long notes (strings, brass, woodwind sustains), draw the dynamics as a CC1 curve. A flat line sounds like a synthesiser; a gentle swell into the note and a taper at the end sounds like breath or bow.
  • For short notes (staccato, pizzicato), velocity usually selects the layer, so vary it.
  • Treat CC11 as a finishing control for balance, not as the main dynamic.

Defaults differ between products. Project SAM documents its own mapping; for any other library, check its manual or use MIDI learn before you assume CC1 does the same thing.

Legato, and why some libraries sound smoother

Joining notes smoothly is the hardest thing to fake. Sound On Sound describes the simple approach as cutting off the beginning of the second note and crossfading into it from the first. The more convincing method records real note-to-note transitions; it credits Vienna Symphonic Library with pioneering this "true legato" approach in 2002.

For your own work, the lesson is to use the legato articulation for connected melodic lines and a separate short or sustained articulation for repeated notes. Mixing them up is a common reason a line sounds stilted.

A free library shows the limits clearly

Free and entry-level libraries are useful teachers because they make trade-offs visible. Sound On Sound's review of Spitfire Audio's BBC Symphony Orchestra Discover lists 33 instruments and 47 articulations in a 200MB download, and says it has "no round-robin samples and only a single dynamic layer". The reviewer's advice is to "make good use of the mod wheel and velocity to provide as much by way of dynamics as you can". It also has a single, well-chosen mic position.

That is a good illustration of the point of this guide. With one dynamic layer, the library cannot do the work for you, so your CC1 and velocity programming matter more, and you hear the result of every choice. Moving to a bigger library later adds layers and variation, but the same habits still apply.

An order of work for a first mockup

This is our recommended workflow, not a standard. It is built from the mechanisms above.

  1. Write it playable. Sketch the parts as MIDI first, and check each line sits in the real range of the instrument. A sampler will happily play a note a violin cannot.
  2. Pick articulations. Start with sustains and one short articulation per section. Add keyswitch changes only where the music needs them.
  3. Draw dynamics. Add CC1 curves to every sustained part before anything else. Match phrases: rise toward the peak, ease after.
  4. Humanise timing and velocity. Nudge notes slightly off the grid, and move velocities by small amounts. Strings that start slowly need their notes placed a little early.
  5. Balance, then space. Set levels with CC11 or the mixer, then use mic positions or one shared reverb to put the sections on one stage. Project SAM's library has Direct, Ambient and Wide mics and a mic crossfader that morphs between drier and more ambient mixes, and the same close-to-far thinking applies if you only have one reverb.
  6. Check against a reference. Compare with a real recording of similar music. Our reference tracks for mixing guide covers how, and arrangement basics for producers helps with scoring decisions.

Common mistakes

  • Every note at velocity 100. The result is a flat, grid-locked part.
  • Dynamics on velocity for long notes. The note will start at one loudness and stay there.
  • Too many layers of the same line. Doubling a part can hide weak programming for a moment, but it adds mud. Fix the single line first.
  • Chasing a bigger library. A larger library gives you more recorded material. It does not supply the phrasing, which is still your job.

Where this leaves you

Mockups sound real when they behave like performances: swelling, breathing and connecting. A library supplies the recordings and the controls; you supply the performance. Learn the four mechanisms (velocity layers, round robins, keyswitches, legato), put dynamics on a controller, and your first mockup will sound better than the library's price would suggest.

Sources checked on 31 Oct 2026.

Sources

  1. Getting started: library basics, Project SAM (primary source). Accessed 31 Oct 2026.
  2. How virtual instruments work, Sound On Sound. Accessed 31 Oct 2026.
  3. Spitfire Audio BBC Symphony Orchestra Discover (review), Sound On Sound. Accessed 31 Oct 2026.

Researched with AI assistance, written and checked by WATMM Desk.

Subscribe to We are the music makers

One email a week: the music-tech and AI-in-music news that mattered, and what we think about it.

Sign-ups open soon.