Programming Strings

Articulations: What They Are

An articulation is the way a note is played — not which note, but how. The same C4 on a violin sounds completely different depending on whether the bow draws across the string in a long connected stroke, bounces off in a short jab, or whether the player plucks the string with a finger instead of bowing at all.

BBC Symphony Orchestra includes separate samples for each articulation. You access them either by switching articulations within the plugin interface, by using keyswitches, or by loading each articulation on its own track. The choice between these approaches matters for your workflow, and we will get to that. First, the articulations themselves.

Legato

Legato is the default string sound — a long, connected bow stroke where notes flow into each other without gaps. When people picture strings in their head, they are usually hearing legato.

Programming legato in BBC Symphony Orchestra:

Overlap your MIDI notes. This is the single most important technique. For the plugin to trigger its legato transitions (the sampled sound of one note gliding into the next), the end of one note must overlap with the beginning of the next. Even a few ticks of overlap is enough. If notes are separated by any gap — even a tiny one — the plugin treats each note as a new bow stroke, and the legato illusion breaks.

How much overlap? Start with about 10-20 ticks (in a typical DAW resolution). Too much overlap and you get a smeared, indefinite transition. Too little and the plugin misses the legato trigger. Listen and adjust.

Note length matters. Legato notes should be long. Whole notes, half notes, quarter notes at moderate tempos. If you are writing eighth-note passages and want them legato, you need each note to sustain until (and slightly past) the attack of the next note. This takes manual editing in the piano roll — Logic’s default quantized note lengths often leave small gaps that break legato.

Velocity affects attack. Higher velocity produces a more aggressive bow attack. Lower velocity produces a gentler entry. For a smooth legato passage, keep velocities moderate and consistent — somewhere in the 60-90 range. Save high velocities (100+) for accented notes or the start of a phrase.

Staccato and Spiccato

Staccato and spiccato are both short articulations, but they are produced differently and sound different.

Programming short articulations:

MIDI note length is critical. For staccato and spiccato patches, your MIDI notes should be short — much shorter than the rhythmic value they represent. A staccato quarter note might have a MIDI duration of an eighth note or less. The sample itself has a built-in decay; your MIDI note just needs to trigger it and get out of the way. If your MIDI notes are too long, some patches will sustain past their natural cutoff point and lose the crisp, detached quality.

Velocity drives the character. Low velocity spiccato is delicate — a light bounce, almost playful. High velocity staccato is aggressive — a sharp jab. The dynamic range within short articulations is wide, and velocity is the primary tool for controlling it.

Rhythmic precision matters more here than in legato. A legato line can absorb minor timing inconsistencies because the notes overlap and flow. Short notes are exposed — each attack is audible, and if one note is ten ticks late, the listener hears it as a rhythmic hiccup. Quantize your short-note passages more carefully than your legato passages, or edit the timing by hand.

Pizzicato

Pizzicato is plucked, not bowed. The player reaches over the fingerboard and pulls the string with a finger, producing a short, rounded attack with minimal sustain. It sounds nothing like a bowed string — closer to a harp or a muted guitar than a violin.

Programming pizzicato:

Very short MIDI notes. Pizzicato samples have their own natural decay built in. Your MIDI note triggers the pluck; the sample handles the rest. Keep MIDI note lengths short — an eighth note or less at most tempos — so you are not fighting the sample’s envelope.

Velocity controls volume and brightness. A soft pizzicato (low velocity) is a gentle pluck. A hard pizzicato (high velocity) is more percussive, with a brighter attack. For rhythmic bass pizzicato lines, lean into higher velocities. For delicate upper-string pizzicato — the kind that sounds like raindrops — keep velocities in the 40-60 range.

Pizzicato does not overlap. Unlike legato, where overlap is essential, pizzicato notes should never overlap. Each pluck is a discrete event. Overlapping notes can cause sample retriggering artifacts or muddied attacks.

Use a separate track. Because pizzicato sounds and behaves so differently from bowed articulations, loading it on its own track (rather than switching to it via keyswitch mid-phrase) keeps your MIDI editing clean. You can see the pizzicato notes in their own region, adjust their velocities independently, and route the track to its own channel strip if you want different processing.

Tremolo

Tremolo is rapid repeated bowing on a single note — the bow moves back and forth quickly, creating a shimmering, sustained texture. It adds urgency, tension, or atmosphere depending on context. A tremolo pianissimo in the violins is one of the most evocative textures in orchestral music.

Programming tremolo:

Sustained MIDI notes. Tremolo patches handle the rapid repetition internally — you do not need to program individual repeated notes. Write a whole note and let the sample do the bowing. Your MIDI region should look like your legato region: long, sustained notes with smooth CC automation underneath.

CC data drives the intensity. A tremolo that stays at a flat dynamic level sounds mechanical. Real tremolo builds and recedes. Use expression (CC11) to shape the volume contour — start soft, swell to a peak, pull back. Even a subtle curve makes the difference between a static sample and a living texture.

Keyswitches work well for tremolo. Unlike pizzicato (which benefits from a separate track because of its fundamentally different behavior), tremolo is bowed and sustains like legato. If your passage alternates between sustained legato and tremolo — a common orchestral technique — keyswitches let you handle both on a single track. Place the keyswitch note at the point where the articulation changes.

Keyswitches vs. Separate Tracks

There are two ways to manage articulation changes in your template: keyswitches within a single track, or separate tracks for each articulation.

Keyswitches keep your track count low. One Violin I track handles legato, staccato, pizzicato, and tremolo — you switch between them by inserting keyswitch notes in the MIDI region. This works well for passages that alternate quickly between articulations, or when you want to see the complete Violin I part on a single lane.

The downside: your MIDI region gets cluttered with keyswitch notes mixed in among the actual music notes. Editing is harder because you have to distinguish between performance notes and control notes. And if a keyswitch note gets accidentally deleted or moved, the wrong articulation plays and you might not notice until you listen back.

Separate tracks give each articulation its own lane. You might have Violin I Legato, Violin I Staccato, Violin I Pizzicato as three separate tracks, each loading the corresponding patch. The MIDI region on each track contains only the notes for that articulation — no keyswitches, no confusion.

The downside: your track count increases. Five string instruments with four articulations each means twenty tracks. That is manageable with summing stacks (group all Violin I articulations under one stack), but it is more visual real estate in your arrange window.

Neither approach is wrong. Many composers use both depending on the piece. For learning, separate tracks are easier to work with because you can see exactly what each articulation is doing. As you get more comfortable, keyswitches can speed up your workflow for passages that switch articulations frequently.

Expression, Modulation, and Volume: The CC Trinity

Three MIDI continuous controllers do most of the work in making sampled strings sound real. Understanding what each one controls — and when to automate which — is the difference between a flat mockup and a performance.

CC11: Expression

Expression controls the dynamic level of the performance within the patch. It is your primary tool for shaping phrases — swelling into a downbeat, tapering off at the end of a phrase, creating a crescendo over four bars.

Think of Expression as the player’s bow pressure and speed. More pressure, faster bow = louder, more intense. Less pressure, slower bow = softer, more intimate. The sample library translates CC11 values into crossfades between dynamic layers — as you increase CC11, the library blends from its piano samples to its forte samples.

Automate Expression constantly. A flat CC11 line produces a flat, lifeless performance. Even a simple passage needs some contour — a slight swell toward the middle of a sustained note, a gentle taper at the end. Real string players never hold a perfectly static dynamic. Your automation should reflect that.

CC1: Modulation

Modulation controls vibrato intensity (and in some libraries, timbral variation) within BBC Symphony Orchestra. At low values, the tone is straight and pure. As you increase CC1, vibrato deepens and the sound becomes warmer, more expressive.

Use Modulation for emotional shaping. A sustained note might start with low CC1 (straight tone) and gradually increase as the note develops (adding vibrato as a player would). A passage that needs emotional intensity gets higher modulation. A cold, exposed passage gets lower modulation.

Modulation and Expression work together but control different things. Expression controls loudness. Modulation controls character. A note can be loud with no vibrato (high CC11, low CC1) or soft with deep vibrato (low CC11, high CC1). The combination of the two is what creates a specific emotional quality.

CC7: Volume

Volume is the overall level of the track — the equivalent of the fader on a mixing console. It does not affect the timbral quality of the sound the way Expression does. Turning CC7 down makes the signal quieter; it does not make the performance sound softer in the way a real player would play softer.

Use Volume sparingly for performance shaping. CC7 is a blunt tool compared to CC11. If you want a passage to get quieter, reach for Expression first — it changes the dynamic layer of the sample, which is how a real instrument gets quieter. Use CC7 for overall level management: balancing sections against each other, compensating for level differences between patches, or fading a section in and out of the arrangement. (For more on the relationship between volume, gain, and signal flow, see the Mixing and Synthesis Tools.)

Velocity Batch Editing

When you record MIDI from a keyboard, the velocities are all over the place. Some notes hit at 127, others at 40, depending on how your fingers happened to land. For string parts, inconsistent velocities create an uneven, bumpy performance where random notes stick out.

The better approach: batch-edit the velocities after recording. Select all the notes in a phrase, bring them to a consistent base level (somewhere around 70-80 for most string passages), and then fine-tune individual notes that need accents or softer attacks.

In Logic Pro, you can select a range of notes in the piano roll, then use the velocity slider or the MIDI Transform window to set them all to a single value. From that uniform starting point, adjust individual notes up or down. An accented downbeat might go to 95. A pickup note leading into the phrase might drop to 55. The point is that you are making deliberate choices rather than living with whatever your keyboard happened to record.

This matters because velocity in BBC Symphony Orchestra affects the attack character — how aggressively the bow bites the string. Inconsistent velocities mean inconsistent attacks, and a passage where every note has a different bow attack sounds like five different players who have never rehearsed together.

The Slow-Attack Offset

String samples — especially legato patches — have a built-in attack time. The sample does not speak instantly the way a piano or a drum does. There is a ramp-up: the bow engages the string, the tone develops, and the full volume arrives a few milliseconds after the MIDI note triggers.

In isolation, this sounds natural. In context — when strings play alongside piano, harp, guitar, or any instrument with a fast attack — the strings sound late. The piano hits the beat precisely. The strings arrive a fraction of a second after. The result is a laggy, sluggish feeling that undermines the whole arrangement.

The fix: nudge the string MIDI notes earlier in time. Move them to the left on the piano roll so that their attack peaks align with the beat, rather than their MIDI note-on messages aligning with the beat.

How far to nudge depends on the patch and the tempo. Start with 20-40 milliseconds (which translates to different tick values depending on your tempo and resolution). Play the strings against a fast-attack instrument and listen. If the strings still sound late, nudge further. If they start sounding early — the attack arriving before the beat — pull them back. You are looking for the point where the perceived downbeat of the string note aligns with the piano’s downbeat.

This technique applies to any sustained instrument with a slow attack — not just strings. French horns, choir patches, and some synth pads all benefit from the same treatment. The principle is the same: compensate for the sample’s attack time so that the perceived onset lands on the beat.

Putting It Together

A realistic string mockup combines all of these elements:

1. Choose the right articulation for each passage. Sustained melodies get legato. Rhythmic figures get staccato or spiccato. Plucked bass lines get pizzicato. Atmospheric textures get tremolo.
2. Program the MIDI accurately — overlapping notes for legato, short notes for staccato and pizzicato, sustained notes for tremolo.
3. Draw CC automation on every track. Expression (CC11) shapes the phrase dynamics. Modulation (CC1) adds vibrato and warmth. Volume (CC7) balances the overall levels.
4. Batch-edit velocities to a consistent base, then adjust individual accents.
5. Offset slow-attack patches so strings land on the beat, not after it.
6. Listen against the full arrangement and adjust. A string part that sounds great in solo might be too loud, too busy, or sitting in the wrong register once the other instruments come in.

The CC automation is where most of the time goes. Expect to spend as much time drawing curves as you do writing notes — probably more. That ratio is normal. The notes are the architecture. The CC data is the performance.

What to Practice

• Load a legato patch on Violin I. Program a four-bar melody and experiment with MIDI note overlap. Start with no overlap (gaps between notes) and listen to how it sounds — each note will have a separate attack. Then add slight overlaps and listen for the legato transitions to engage. Find the overlap length that sounds most natural.
• Load a staccato patch. Program a repeated rhythmic figure — eighth notes on a single pitch. Vary the MIDI note length from very short (sixteenth note) to longer (quarter note). Listen for the point where the notes stop sounding detached and start sounding sustained. That boundary is where you lose the staccato character.
• Set up two tracks: Violin I Legato and Violin I Pizzicato. Write a passage that alternates between bowed and plucked sections. Now try the same thing with keyswitches on a single track. Compare the two workflows and decide which feels clearer to you.
• Take any string passage you have already programmed and draw CC11 (Expression) automation from scratch. Start with a curve that follows the musical phrasing — swell toward downbeats, taper at phrase endings. Then add CC1 (Modulation) on top — increase vibrato during sustained notes, reduce it on shorter notes. Listen to the difference between the automated version and a flat-line version. The gap should be obvious.
• Program a piano or harp part alongside a legato string line. Listen for the timing misalignment — the strings arriving late. Nudge the string notes earlier until the attacks align. Try different offset amounts (20ms, 40ms, 60ms) and listen for the sweet spot.
• Take a passage with mixed articulations (legato verse, staccato rhythm, pizzicato bass) and batch-edit the velocities. Set everything to 75, then go back and add intentional accents and soft notes. Play it back. Does it sound more cohesive than the unedited version?