MIDI note velocity is sent with each Note On message, while channel volume travels as a separate Control Change value. Both can make an instrument quieter or louder, but they reach different parts of the performance and can change the sound differently.
MIDI volume vs velocity gets confusing because a simple synth may map velocity mostly to gain, making both controls appear similar. Swap to a sampled piano, drum instrument, or expressive synth and velocity can alter timbre, attack, sample choice, filter movement, or another destination.
The broader split between performance instructions and rendered sound is the same reason audio and MIDI serve different purposes inside a DAW. Here, velocity describes an individual note event, while MIDI volume control and expression can keep changing after the note starts.
An instrument decides what the incoming number does. A sampler may select or crossfade recordings made at different playing strengths, while a synth may route velocity into amplitude, filter cutoff, envelope depth, or several destinations. A badly matched velocity curve can make or break a piano VST because final output level cannot repair a controller that bunches most notes into the wrong response range.
MIDI note volume is therefore a sloppy label for velocity. Lowering velocity might make a snare quieter, but it can also trigger a softer sample with a different attack and tone. Measured MIDI velocity behavior across commercial synthesizers found no single de facto relationship between velocity and output amplitude.
Velocity is fixed when the note begins. Editing it cannot create a smooth crescendo halfway through a held string or pad note because the original Note On has already happened. Continuous movement needs controller data, host automation, or another modulation source that stays active while the note sounds.
MIDI volume vs expression matters when a part needs stable balance and moving dynamics. A MIDI CC 11 expression lane can swell a sustained sound without rewriting its original velocity, while CC7 can establish the channel's overall MIDI volume range. A MIDI expression fader or pedal can keep sending CC11 values as the performance moves.
A MIDI expression message remains controller data rather than becoming part of the note itself. Imported sequences can carry these values with pan, sustain, modulation, and other controls, which is one reason the same MIDI file can sound wildly different through another sound engine. The receiving instrument still decides how each controller affects the sound.
MIDI modulation vs expression is not a universal recipe. CC1 is assigned to modulation and CC11 to expression, but a plugin or sample library can map those sources to different internal destinations. Checking the instrument's own MIDI map is safer than assuming every library uses the same dynamic scheme.
To automate MIDI volume before audio leaves the instrument, controller data must reach the correct destination. MIDI ports, channels, and tracks do different jobs, so a perfect CC lane can control nothing when the track is routed to the wrong channel or endpoint.
Host automation is separate again. Some plugins expose parameters directly to the DAW while also accepting MIDI controllers, so host automation or MIDI CC messages can drive the same plug-in parameter through different paths. Once you move the DAW's audio fader, you are changing the rendered audio level rather than the velocity, CC7, or CC11 data that shaped the instrument upstream.
Use velocity when the note's attack, articulation, or tone should change. Use CC11 when a sustained performance needs expression, CC7 when MIDI channel balance needs adjustment, and the audio fader when the final mix level is what you want to move.
MIDI volume vs velocity gets confusing because a simple synth may map velocity mostly to gain, making both controls appear similar. Swap to a sampled piano, drum instrument, or expressive synth and velocity can alter timbre, attack, sample choice, filter movement, or another destination.
The broader split between performance instructions and rendered sound is the same reason audio and MIDI serve different purposes inside a DAW. Here, velocity describes an individual note event, while MIDI volume control and expression can keep changing after the note starts.
Velocity belongs to the note attack
In MIDI 1.0, Note On carries a note number and velocity value, and a Note On with velocity zero functions as Note Off. For a practical answer to what MIDI velocity is, treat it as a per-note performance value rather than a miniature mixer fader.An instrument decides what the incoming number does. A sampler may select or crossfade recordings made at different playing strengths, while a synth may route velocity into amplitude, filter cutoff, envelope depth, or several destinations. A badly matched velocity curve can make or break a piano VST because final output level cannot repair a controller that bunches most notes into the wrong response range.
MIDI note volume is therefore a sloppy label for velocity. Lowering velocity might make a snare quieter, but it can also trigger a softer sample with a different attack and tone. Measured MIDI velocity behavior across commercial synthesizers found no single de facto relationship between velocity and output amplitude.
Velocity is fixed when the note begins. Editing it cannot create a smooth crescendo halfway through a held string or pad note because the original Note On has already happened. Continuous movement needs controller data, host automation, or another modulation source that stays active while the note sounds.
CC7 and CC11 can move during a note
Standard MIDI volume control uses CC7 Channel Volume, while MIDI expression control uses CC11 Expression. Both use values from 0 to 127 in MIDI 1.0, but General MIDI guidance gives them different jobs. CC7 handles the broader channel level, and CC11 handles expression within it.MIDI volume vs expression matters when a part needs stable balance and moving dynamics. A MIDI CC 11 expression lane can swell a sustained sound without rewriting its original velocity, while CC7 can establish the channel's overall MIDI volume range. A MIDI expression fader or pedal can keep sending CC11 values as the performance moves.
A MIDI expression message remains controller data rather than becoming part of the note itself. Imported sequences can carry these values with pan, sustain, modulation, and other controls, which is one reason the same MIDI file can sound wildly different through another sound engine. The receiving instrument still decides how each controller affects the sound.
MIDI modulation vs expression is not a universal recipe. CC1 is assigned to modulation and CC11 to expression, but a plugin or sample library can map those sources to different internal destinations. Checking the instrument's own MIDI map is safer than assuming every library uses the same dynamic scheme.
DAW automation sits on another layer
MIDI volume automation can mean drawing CC7, riding CC11, automating a plugin parameter through the host, or moving the audio channel fader after the instrument has generated sound. Those routes can produce a similar level change while editing different data.To automate MIDI volume before audio leaves the instrument, controller data must reach the correct destination. MIDI ports, channels, and tracks do different jobs, so a perfect CC lane can control nothing when the track is routed to the wrong channel or endpoint.
Host automation is separate again. Some plugins expose parameters directly to the DAW while also accepting MIDI controllers, so host automation or MIDI CC messages can drive the same plug-in parameter through different paths. Once you move the DAW's audio fader, you are changing the rendered audio level rather than the velocity, CC7, or CC11 data that shaped the instrument upstream.
Use velocity when the note's attack, articulation, or tone should change. Use CC11 when a sustained performance needs expression, CC7 when MIDI channel balance needs adjustment, and the audio fader when the final mix level is what you want to move.
