MIDI assigns the damper pedal to Control Change 64, with conventional on-off behavior switching between values 63 and 64. That rule lets an ordinary footswitch sustain notes, but it says nothing about the useful positions between fully released and fully depressed.
Half-pedaling uses those intermediate positions to vary how strongly dampers contact the strings. On a capable virtual piano, a partial lift can shorten decay and clear harmony without the sudden cutoff of a released switch. The result depends on the pedal, keyboard input, recorded MIDI, and sound engine all preserving the movement.
Set the keyboard's pedal socket to continuous mode, then run its endpoint calibration by moving through the complete travel without rushing. If pressing the pedal lowers the values, correct the polarity or inversion before touching the piano plugin, then repeat the endpoint test.
Open a MIDI monitor and press slowly, expecting multiple intermediate CC64 values rather than only 0 and 127 across its travel. If the hardware sends two values, no plugin or DAW can reconstruct continuous damper movement because the missing positions were never measured.
Hold the pedal at several positions while watching the monitor, pausing long enough to judge each resting value. Values should remain reasonably stable because a stream that flickers at rest can make the piano breathe or chatter even when your foot is still.
Some piano engines ship with continuous sustain disabled in their settings, so enable half-pedal behavior before judging the hardware. Even a highly responsive virtual grand cannot restore pedal detail that a switch, socket, or disabled receiver discarded during capture.
Record one slow pedal sweep into an empty MIDI region and inspect the CC64 lane. Look for the released value, the first change, the last gradual change, and any sudden jump to the maximum. Repeat the sweep several times because a stable gap points to mapping, while scattered values suggest noisy hardware or an unreliable connection.
Calibrate the keyboard first, then remap the range only if the source contains usable intermediate data. Scaling a pedal that sends 20 through 100 can restore practical endpoints. Scaling one that jumps directly from 80 to 127 merely stretches the existing discontinuity and may make the audible jump worse.
Keep the original sweep on a muted track before applying any remapping. It lets you compare corrected output against the source and prevents repeated edits from hiding whether the failure began in hardware or software.
Do not assume the sustain jack is always the best input. Some keyboards treat that socket strictly as a switch while allowing an expression socket to send continuous values. Assigning that input to CC64 can work, but only when the keyboard supports the pedal's wiring and the resulting direction, minimum, and maximum are verified.
Test with two slow chords that share no bass notes. Hold the first with full pedal, lift only far enough to hear its low end clear, then depress again as the second chord settles. If the sound cuts off, the plugin may treat CC64 as a switch or give your foot too little useful half-pedal range.
Recorded performances need the same care. Some editors display CC64 as stepped events even when many values were captured, while other workflows simplify sustain into off and on points. Inspect the data after recording and avoid deleting intermediate events unless the chosen piano genuinely ignores them.
Save the finished pedal mapping separately for each keyboard and piano engine. A range that feels natural in one plugin can trigger too early in another, while another pedal can reverse polarity or alter usable travel. Naming both devices in the preset prevents an old correction from quietly damaging a new setup.
Half-pedaling uses those intermediate positions to vary how strongly dampers contact the strings. On a capable virtual piano, a partial lift can shorten decay and clear harmony without the sudden cutoff of a released switch. The result depends on the pedal, keyboard input, recorded MIDI, and sound engine all preserving the movement.
Continuous control must survive the hardware chain
A switch pedal normally sends two states regardless of foot movement, while a continuous or half-damper model can provide changing values. Its connector alone proves little because the keyboard socket must accept continuous input, recognize the electrical design, and transmit the result as CC64.Set the keyboard's pedal socket to continuous mode, then run its endpoint calibration by moving through the complete travel without rushing. If pressing the pedal lowers the values, correct the polarity or inversion before touching the piano plugin, then repeat the endpoint test.
Open a MIDI monitor and press slowly, expecting multiple intermediate CC64 values rather than only 0 and 127 across its travel. If the hardware sends two values, no plugin or DAW can reconstruct continuous damper movement because the missing positions were never measured.
Hold the pedal at several positions while watching the monitor, pausing long enough to judge each resting value. Values should remain reasonably stable because a stream that flickers at rest can make the piano breathe or chatter even when your foot is still.
Some piano engines ship with continuous sustain disabled in their settings, so enable half-pedal behavior before judging the hardware. Even a highly responsive virtual grand cannot restore pedal detail that a switch, socket, or disabled receiver discarded during capture.
Range mismatches create hidden dead zones
Continuous output does not guarantee smooth results when a pedal covers only part of the range, jumps near the bottom, or reaches maximum too soon. Meanwhile, the plugin may begin its half-pedal effect above one threshold and reach full sustain below another, so identical data can feel different.Record one slow pedal sweep into an empty MIDI region and inspect the CC64 lane. Look for the released value, the first change, the last gradual change, and any sudden jump to the maximum. Repeat the sweep several times because a stable gap points to mapping, while scattered values suggest noisy hardware or an unreliable connection.
Calibrate the keyboard first, then remap the range only if the source contains usable intermediate data. Scaling a pedal that sends 20 through 100 can restore practical endpoints. Scaling one that jumps directly from 80 to 127 merely stretches the existing discontinuity and may make the audible jump worse.
Keep the original sweep on a muted track before applying any remapping. It lets you compare corrected output against the source and prevents repeated edits from hiding whether the failure began in hardware or software.
Do not assume the sustain jack is always the best input. Some keyboards treat that socket strictly as a switch while allowing an expression socket to send continuous values. Assigning that input to CC64 can work, but only when the keyboard supports the pedal's wiring and the resulting direction, minimum, and maximum are verified.
Pedal timing matters as much as pedal depth
Half-pedaling controls damper position, while delayed and repeated pedal movements control which decays are caught. Pressing after a chord begins but before the keys rise preserves the notes without smearing their initial attack into the previous harmony. Pressing after release may recover less direct decay while still exciting whatever sympathetic behavior the engine models.Test with two slow chords that share no bass notes. Hold the first with full pedal, lift only far enough to hear its low end clear, then depress again as the second chord settles. If the sound cuts off, the plugin may treat CC64 as a switch or give your foot too little useful half-pedal range.
Recorded performances need the same care. Some editors display CC64 as stepped events even when many values were captured, while other workflows simplify sustain into off and on points. Inspect the data after recording and avoid deleting intermediate events unless the chosen piano genuinely ignores them.
Save the finished pedal mapping separately for each keyboard and piano engine. A range that feels natural in one plugin can trigger too early in another, while another pedal can reverse polarity or alter usable travel. Naming both devices in the preset prevents an old correction from quietly damaging a new setup.
