Programming a Strum That Sounds Like a Hand, Not a Chord

Felix Ward
By Felix Ward

Felix is an indie-folk songwriter and session guitarist who values vibe over perfection. He looks for tools that potentialize 'happy accidents' and offer immediate inspiration. If a plugin requires reading a 100-page manual, he's probably already moved on.

Do This Now

  • 1 Spread the six notes of a strum across 15 to 35ms. Simultaneous notes are the single loudest tell in a programmed guitar part.
  • 2 Reverse the spread on upstrokes. A downstroke hits the low string first, an upstroke hits the high string first, and the order is what the ear reads as direction.
  • 3 Alternate down and up with the bar, not with the notes. A guitarist's hand keeps moving through the rests, so which stroke lands where is decided by the tempo, not by your pattern.
  • 4 Give upstrokes fewer strings and lower velocity. Most upstrokes catch only the top three or four strings, which is why they sound lighter.
  • 5 Leave the fret noise in. Chord-change squeaks are the thing listeners cannot name and always miss when absent.

Playing connects you to YouTube, which may set cookies.

The stroke-by-stroke mechanics, worked through in a sampler. “6 Easy Steps to Programming Realistic Acoustic Guitar Strums | Ample Guitar Martin” by HIFIMIDI, on YouTube. Playing it loads the video from Google.

A chord played on a keyboard is six notes at the same instant. A chord played on a guitar is six notes arriving one after another, in a direction, at different volumes, with the hand still moving afterwards.

Every difference in that sentence is programmable, and most MIDI guitar parts implement none of them.

Spread the Strum Before Anything Else

A pick crossing six strings takes real time. Fifteen to thirty-five milliseconds is the working range, tighter on aggressive fast playing and wider on a slow open ballad strum.

Take your block chord and offset each note from the one below it by three to six milliseconds. That is the entire technique and it does more than everything else on this page combined.

Settings to Dial In
Strum spread
15 to 35ms total
Per-string offset
3 to 6ms
Fast aggressive
12 to 18ms
Slow ballad
35 to 45ms

The friction is that quantising afterwards destroys it, which people do without thinking when tidying a part. Quantise the first note of each strum only, or lock the offsets into the pattern before you go anywhere near the grid.

Playing connects you to YouTube, which may set cookies.

Pattern building rather than single strums, which is the next problem. “How to make guitar patterns - tips / techniques for more realistic guitars (FREE MIDI)” by Splice, on YouTube. Playing it loads the video from Google.

Make the Direction Audible

A downstroke starts at the lowest string. An upstroke starts at the highest. Reversing the note order is most of what tells a listener which one they just heard.

Upstrokes also differ in coverage. A player pushing back up usually catches only the top three or four strings rather than all six, because the hand is already travelling away from the bass. So an upstroke has no low note, fewer notes overall, and a lower velocity.

Program that literally. Downstroke: six notes, low to high, full velocity. Upstroke: three or four notes, high to low, velocity ten to twenty points under.

The mistake is treating up and down as the same event flipped. They are different gestures producing different chords, and copying the downstroke backwards gives you a strange full-voiced upstroke that no guitarist plays.

Assign Strokes to the Pulse, Not to Your Pattern

Here is the one that separates a part that grooves from a part that is merely accurate.

A strumming hand does not stop. It keeps moving down-up-down-up in constant eighths or sixteenths through the whole bar, and where the pattern has a rest the hand simply misses the strings. That means the direction of any given strum is decided by where it falls in the bar, not by what you wrote before it.

So map the pulse first. If you are in eighths, every downbeat and every offbeat has a fixed direction, and any strum landing on beat two and a half is an upstroke whether or not the previous strum was a downstroke.

Getting this wrong is why patterns that look correct feel wrong. The notes are right, the accents are right, and the physical logic underneath is impossible, which the ear registers as stiffness without being able to say why.

Leave the Noise In

Fret noise is the detail people remove because it sounds like a mistake, and it is the detail whose absence they notice.

Every chord change on a wound string produces a squeak as the fingers slide. Every strum has pick attack before the note. A hand resting back on the strings damps them with a dull thud rather than silence.

Most libraries sample all three and put them on a control you can turn down. Turn it up instead, then pull it back only if it is genuinely distracting in the mix. Position the fret noise just before the chord change rather than on it, because the hand moves before the strum lands.

The catch is exposure. Fret noise sitting under a full arrangement is texture, and the same amount on a solo guitar in a quiet cue is a distraction. Automate it rather than setting it once.

Vary the Chord, Not Only the Velocity

The last thing, and it is the one that survives repeated listening.

A guitarist does not play the same six strings every time. Some strums catch five, some catch four, the bass note changes as the thumb moves, and a fast passage drops notes the hand did not reach.

So edit the chords themselves across a repeated pattern. Drop the lowest string on a couple of strums, drop the top on others, and let one or two land on only three notes. Velocity variation alone gives you the same chord at different volumes, which is a fader move rather than a performance.

Where the library models it, palm muting is the strongest version of this. A muted strum is a different sound rather than a quieter one, and alternating muted and open strokes is most of what rhythm guitar actually is.

The check that catches everything above: loop four bars and listen for whether anything repeats exactly. If any two strums are identical, a hand did not play them.

Related Articles

Frequently Asked Questions

How much should I spread the notes of a strum?

Between 15 and 35 milliseconds from the first string to the last, depending on tempo and intensity. A slow ballad strum can stretch to 40 or more, and a fast aggressive one tightens toward 12. Anything under about 10 milliseconds starts reading as a keyboard chord, and exactly simultaneous notes always do.

What is the difference between a downstroke and an upstroke in MIDI?

The order the strings arrive in, and how many of them do. A downstroke starts at the lowest string and moves up, so the bass note leads. An upstroke starts at the highest string and usually catches only the top three or four, so it is lighter and has no low end. Reversing the note order in your DAW is most of what makes an upstroke sound like one.

Do I need a dedicated strumming engine to do this?

No, but it saves hours. A strumming engine handles the spread, the direction and the string selection from a single chord, which is the whole of what this guide describes. Programming it by hand on a note-by-note library gives you more control and costs far more time, and it is worth doing at least once to understand what the engine is doing for you.

Why does my strumming pattern sound stiff even with the notes spread?

Usually because the strumming hand stops between chords in your part and never stops in reality. A guitarist keeps the hand moving in a constant down-up motion through the whole bar, and simply misses the strings on the beats where nothing sounds. If your pattern assigns directions to the notes you wrote rather than to the underlying pulse, the strokes will land in the wrong direction and the groove will feel wrong without sounding obviously wrong.

Should I quantise guitar strumming?

Quantise the start of each strum and never the notes inside it. The first string of a strum can sit on the grid, and the remaining five have to arrive after it in order. Quantising everything collapses the spread that makes it a strum, which is the most common way people undo their own work in this area.

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

Felix Ward

Felix is an indie-folk songwriter and session guitarist who values vibe over perfection. He looks for tools that potentialize 'happy accidents' and offer immediate inspiration. If a plugin requires reading a 100-page manual, he's probably already moved on.