To normalize MIDI velocity, first find the notes that are unexpectedly weak or strong, then move those values into a useful range while preserving the accents that make the phrase feel played. Do not set every note to one number. A good result sounds consistent in context, not mechanically identical.
Know what you are changing
Velocity is a per-note MIDI value, normally from 1 to 127, that describes performance dynamics. Many instruments use a higher value for a louder or brighter attack and a lower value for a softer one, but the exact response depends on the sound you load. A piano patch may change both volume and tone across its velocity range, while a simple synth patch may barely react. That is why velocity cleanup must be checked by ear with a suitable instrument.
People use normalize to mean several different jobs: raise notes that are nearly inaudible, pull down accidental spikes, narrow an erratic range, or give repeated notes a more stable pattern. Decide which problem you have before touching the lane. If the rhythm or pitch is wrong, fix that separately; velocity cannot repair a late note or a wrong melody.
Keep the original and choose a listening sound
Save an untouched copy of the MIDI file before editing. Then open the working copy in SongSprig's MIDI Editor and choose a playback instrument close to the part's intended role. It does not need to be the final sound, but a piano line should not be judged through a drum kit, and a bass phrase should use a sound with a clear low-register response. Play the full part once without making changes.
- Note where a phrase disappears, jumps forward, or changes character for no musical reason.
- Listen for repeated patterns that should feel related but have very different attacks.
- Mark intentional accents, pickups, ghost notes, and crescendos so you do not erase them.
- Separate velocity problems from timing, note-length, and pitch problems before the first edit.
Set a range for each musical role
There is no universal correct velocity. Use a small set of starting ranges for the part in front of you, then adjust by ear. For a straightforward melodic draft, main notes might sit around 70–90, clear accents around 90–105, and softer pickups around 50–70. These are working zones, not mastering targets. A drum performance, orchestral library, or highly responsive piano can need very different values.
- Main notes: make the ordinary pulse reliable enough to hear without dominating the phrase.
- Accents: keep only the notes that define the groove, downbeat, or melodic peak clearly above the baseline.
- Pickups and passing notes: leave them softer when they lead into a stronger destination.
- Ghost notes: preserve the contrast if they are part of the feel; raise them only when they vanish completely on the chosen sound.
The distance between roles matters more than any single number. If the baseline is 82 and an accent is 96, the phrase may still feel natural. If every note is 100, there is no dynamic clue left for the instrument to interpret.
Edit one short phrase at a time
In the MIDI Editor, the lower velocity lane shows one vertical bar for each note. Play a short phrase, find the bar under the problem note, and click higher or lower in that bar to set a new value. The current editor changes one note at a time, so it is best suited to correcting a melody, bass line, converted idea, or another focused part rather than flattening a large orchestral arrangement in one action.
- Start with the loudest accidental spike because it can hide every quieter decision.
- Next, raise only the notes that disappear inside an otherwise clear phrase.
- Compare repeated phrases and align their ordinary notes before adjusting expressive accents.
- Use playback after every few changes. Undo immediately when the contour becomes less convincing.
- Leave acceptable notes alone. Correcting the obvious outliers often solves the problem faster than redrawing the whole lane.
Use a before-and-after pattern, not a flat target
Suppose an eight-note piano phrase arrives with velocities of 42, 118, 67, 125, 58, 64, 121, and 48. The second and fourth notes leap out, the first and last almost disappear, and nothing in the melody explains those jumps. Setting all eight notes to 90 would remove the accidents, but it would also remove the phrase shape.
A more useful pass could be 58, 82, 74, 98, 70, 76, 94, and 62. The fourth note remains the main peak, the seventh keeps a smaller accent, and the opening and ending become audible without sounding equally strong. Treat those values as an example of the decision pattern, not a preset to copy into every file.
Handle common MIDI sources differently
- Audio-to-MIDI conversion: fix isolated spikes and dropouts first. The conversion may have useful pitch and timing even when its dynamics are uneven.
- Keyboard performance: preserve hand-shaped accents and phrase direction. Narrow only the accidental extremes caused by an uneven take or controller response.
- Programmed melody: add small, intentional differences around repeated notes so the part does not feel stamped at one level.
- Drums: judge each kit piece separately. A quiet hi-hat and a quiet kick do not serve the same role, and the same velocity can trigger different samples.
- Chords: check notes that start together. One overly strong chord tone can change the perceived voicing even when every pitch is correct.
Check the edit on two passes
First, listen quietly. Unexpected spikes remain obvious at low playback levels, while notes that vanish may still need a small lift. Second, listen at your normal working level and focus on the phrase rather than the numbers. If you notice the intended accents but stop noticing the repairs, the range is doing its job.
If the final production will use another instrument, audition that sound before treating the edit as finished. Velocity can switch sample layers, change filter response, or do very little depending on the instrument. The same MIDI values can therefore feel balanced on one patch and exaggerated on another.
Common mistakes
- Setting every note to 100 and calling the file normalized.
- Chasing exact values before choosing a playback sound.
- Raising all quiet notes even when some are intentional pickups or ghost notes.
- Fixing pitch, timing, note length, and velocity in the same pass, then losing track of what improved.
- Editing every note in a long file instead of repairing the phrases that actually sound uneven.
- Overwriting the source file before comparing the new performance with the original.
Completion check
- No accidental note jumps out or disappears in the main phrases.
- Repeated patterns have a related baseline without becoming exact copies.
- Accents, pickups, ghost notes, and crescendos still have an audible purpose.
- The chosen playback instrument responds naturally across the edited range.
- A quiet-volume listen and a normal-volume listen both pass.
- The original MIDI remains untouched, and the edited file has been exported with a clear new name.
Open the MIDI Editor when you have a focused part with a few uneven notes. Correct the outliers, keep the musical hierarchy, compare against the untouched file, and export as soon as the phrase feels steady without losing its movement.