Why Your Strings Sound Fake, and It Is Not the Library You Bought

Louis Raveton
By Louis Raveton

Louis works across immersive scores (Venice Biennale, LVMH) and animation (Canal+), while producing Downtempo and Electro-Dub as Monsieur Shwill and Flagada. He treats his sample drive like a record collection, constantly hunting for the perfect 'imperfect' texture

Do This Now

  • 1 Bounce your legato patch to audio and measure grid to transient. Most lyrical legato speaks 60 to 110ms late, and that number is the one you correct against.
  • 2 Set negative track delay per articulation, not per instrument. Legato around -90ms, sustains -60ms, marcato -30ms, spiccato -10ms, pizzicato 0.
  • 3 Stagger section entries by 8 to 18ms. First violins early, basses last, in the order a real section actually speaks.
  • 4 Record the notes, then the CC1 ride, then the note ends. Three passes beat one heroic take that gets none of them right.
  • 5 Shorten long note-offs by 20 to 40ms so the release sample has room to sound before the next chord lands.

Playing connects you to YouTube, which may set cookies.

The measurement and the offset, done on screen. “Orchestral Programming Tutorial - Negative Delay” by Master The Score, on YouTube. Playing it loads the video from Google.

You bought the good library. You read the roundups, you spent the money, you loaded the patch, and the mockup still sounds like a mockup. The tone is right and the room is right, and something is still wrong.

It is almost never the samples. It is when the notes start.

A sampled string section gives itself away in the first 100 milliseconds of every phrase, before any question of tone or reverb arises. Fix that and the same library you already own sounds like a different product.

Measure What Your Legato Patch Actually Does

Every sampled note begins before it has a pitch. The engineer started the recording as the bow moved, so the file opens with rosin and pressure and hair, and the note you actually hear arrives some distance into the sample.

That distance is a real number and you can read it in thirty seconds. Bounce a single sustained note from your legato patch to audio, starting exactly on a bar line, and zoom in until you can see the waveform. Measure from the bar line to the point where the waveform stops being noise and starts being a periodic tone.

On lyrical legato patches, expect 60 to 110ms. On sustains without the legato transition, 40 to 70ms. On spiccato and staccato, 5 to 20ms. Those are the numbers your ear has been complaining about.

The annoyance here is that the figure is not constant across the instrument. Low notes on a bass patch speak later than high notes on a violin patch, sometimes by 30ms, because the string physically takes longer to settle. Measure at the register you actually write in rather than at C3 out of habit.

Set Negative Track Delay Per Articulation, Not Per Instrument

This is the single change that does the most, and most people apply it at the wrong level.

The common approach is one track delay per instrument: violins get -60ms, cellos get -60ms, done. That fails the moment the part switches articulation, because the legato you corrected for and the spiccato on the same track need offsets that differ by 80ms. Correct one and you break the other.

So split articulations onto their own tracks, or use a DAW that allows delay per MIDI channel, and set each one against its own measured value.

Settings to Dial In
Lyrical legato
-90ms
Sustains
-60ms
Marcato
-30ms
Spiccato
-10ms

Treat those as a starting point, not a prescription. They come from measuring a handful of Kontakt orchestral patches, and your library will differ.

The friction is real and worth knowing before you commit. Cubase exposes track delay in milliseconds in the inspector, Logic hides it under the track header's advanced parameters, and Pro Tools handles it differently again through delay compensation. In all of them, negative delay means the DAW must look ahead, so a very large negative value on a track that also carries live input will fight you.

Playing connects you to YouTube, which may set cookies.

The per-articulation setup from the second section, in one DAW. “Negative Delay in Cubase - Tightening Up Your Strings” by Yuggoth Productions, on YouTube. Playing it loads the video from Google.

Stagger the Section Entries in the Order They Actually Speak

Once every articulation lands where you asked, a second problem becomes audible: the whole section starts at exactly the same instant, which no real section has ever done.

Sixteen players do not begin together. The lighter instruments speak first because there is less string to move, and the spread across a full section is something like 8 to 18ms from first violins to basses. That spread is not random, it is ordered, which is why the humanize button does not fix it.

Set it as a fixed offset per section, on top of the articulation delay:

Settings to Dial In
First violins
+0ms
Second violins
+5ms
Violas
+9ms
Cellos
+13ms
Basses
+18ms

Reach for randomisation only inside a section, and keep it small, around 4ms either side. Anything larger and a unison line starts to flam.

Here is the mistake I made for two years. I used the DAW humanize function, which randomises note start and velocity together, and on a library where CC1 carries the dynamics the velocity half of that does nothing at all while the timing half applies the same random spread to a solo cello and a full section. The result sounded less mechanical and no more like an orchestra.

Record the Line, the Dynamics and the Note Ends Separately

Three passes, in this order, on every part that matters.

Pass one is notes only. Play or draw the pitches and rhythm with the mod wheel parked around 60, and do not touch it. You are establishing the line, and nothing else.

Pass two is the CC1 ride. Play the phrase again with your hand on the wheel and your ears on the shape, ignoring the keyboard entirely. A fader with a long throw is easier than a wheel for slow swells, and either beats drawing the curve with a mouse, which produces the ramp shape that says mockup more loudly than anything else on this page.

Pass three is note ends, and it is the one everyone skips. A real bow releases a note over 100 to 200ms. A sample cut off at the note-off gets its release layer chopped, so shorten your long note-offs by 20 to 40ms and give the release somewhere to sound.

The catch on that third pass is legato. Sampled legato transitions usually require the notes to overlap, so if you shorten aggressively across a phrase you will break the transition and get a re-attack on every note instead. Shorten the last note of a phrase and the notes before a rest, and leave the interior of a legato line alone.

Test It at Half Speed Before You Trust It

Bad timing hides at tempo and cannot hide at half speed.

Drop the session to 50% and listen to eight bars. Attacks that felt acceptable at 120bpm turn into obvious little clusters of notes arriving at the wrong moment, and the parts that are genuinely wrong separate themselves from the parts you were only worried about. Then take it back to tempo and fix the ones you heard.

The other cheap test is to mute everything except strings and percussion. Percussion samples are near-instant, so any string part still fighting its attack delay will drag audibly against the grid that the percussion is defining. If the strings sit against a marked-up snare, they will sit against anything.

Both tests take under five minutes and neither requires you to trust your memory of what an orchestra sounds like, which after nine hours in the same room is not worth much anyway.

What This Does Not Fix

Timing is the largest single tell, and it is not the only one. Once note starts are correct you will start hearing the things underneath: a CC1 ride that is a straight ramp rather than a shape, block chords where a real orchestra would divide the line, one reverb doing the work of a hall and a room together.

Those are separate problems with separate fixes, and none of them are audible while the timing is wrong, because the ear is busy with the rhythm and never gets to the tone.

Start here. It costs an evening, it applies to every library you already own, and it does not require you to buy anything.

Related Articles

Frequently Asked Questions

Why do my sampled strings sound late even though the MIDI is on the grid?

Because the sample itself starts with the physical noise of a bow taking hold, and that takes time. The recording engineer captured the note from the moment the bow moved, not from the moment it produced pitch. On a lyrical legato patch the audible pitch typically arrives 60 to 110ms after the MIDI note, so MIDI that looks correct sounds late.

What negative track delay should I use for strings?

There is no single figure, because it depends on the articulation and the library. Measure it rather than copying a number: bounce the patch, find the gap between the grid line and the audible pitch, and set track delay to that value as a negative. As a starting point, lyrical legato needs around -90ms, sustains around -60ms, marcato around -30ms and spiccato around -10ms.

Should I use my DAW's humanize function on orchestral MIDI?

Not on its own. Humanize randomises note starts and velocity together, and on a library where CC1 carries the dynamics the velocity randomisation does nothing useful while the timing randomisation is applied evenly across every part. Real sections are not randomly out of time, they are consistently ordered, with the lighter instruments speaking first.

Is it better to fix timing with track delay or by moving the MIDI notes?

Track delay, in almost every case. Moving notes leaves you with a MIDI part that no longer lines up with the score, which makes editing, printing and handing the session to an orchestrator harder for no benefit. Track delay corrects the sound while leaving the notation honest.

Does this still matter if I only write short ostinatos?

Less, but it does not disappear. Spiccato and staccato samples still carry 5 to 20ms of pre-attack, and at 150bpm a 20ms error is around 5% of a sixteenth note, which is enough to smear the rhythm against a percussion part that is exactly on the grid. The fix is smaller, not unnecessary.

Why do my strings sound worse after I fix the timing?

Usually because the timing was hiding a dynamics problem. Once every note starts where you expect, the ear stops working on the rhythm and starts listening to the line, and a flat CC1 ride that was previously masked becomes obvious. That is progress, not regression.

More Guides

All Guides →

New reviews, no noise

Occasional email when we publish something worth your time. No daily digest, no vendor press releases.

We store only your address, never sell it, and delete it as soon as you unsubscribe. See our privacy policy.

Written By

Louis Raveton

Louis works across immersive scores (Venice Biennale, LVMH) and animation (Canal+), while producing Downtempo and Electro-Dub as Monsieur Shwill and Flagada. He treats his sample drive like a record collection, constantly hunting for the perfect 'imperfect' texture