If your MIDI keyboard feels stiff, lifeless, or unresponsive to how hard you play, the velocity curve is almost always the culprit. Learning how to set up velocity curves on a MIDI keyboard transforms a flat, robotic performance into one that breathes with expression and dynamics. The good news is that once you understand what velocity values actually do, the setup process becomes a straightforward tweak you can apply in any DAW or directly on the keyboard itself.
A velocity curve is simply a mapping between how hard you press a key and the MIDI velocity value (0 to 127) that gets sent to your software. Most keyboards and DAWs let you reshape that mapping so soft presses produce the dynamics you expect, loud hits reach full velocity, and the overall feel matches your playing style. In this guide, our team walks through the curve types, the setup steps for every major DAW, hardware versus software adjustments, and the troubleshooting fixes for the most common complaints we hear from producers.
Table of Contents
What Is MIDI Velocity and Why It Matters
MIDI velocity is a numeric value from 0 to 127 that encodes how hard or fast a key is pressed when a Note On message fires. That single number drives volume, brightness, sample layer selection, and sometimes articulation switches inside your virtual instruments. Without velocity response, every note you play hits at the same intensity, which is why performances sound mechanical and flat.
The value comes from a physical measurement. Inside most velocity-sensitive keybeds, two contact points sit under each key. The keyboard measures the time difference between the first and second contact closing as the key travels down. A faster press produces a shorter time gap, which translates to a higher velocity value. This is why semi-weighted and hammer-action keys tend to feel more expressive than cheap synth-action mini keys. They have more travel and a more reliable sensing mechanism.
Why this matters in practice: sample libraries switch between soft, medium, and hard-recorded layers based on incoming velocity. A piano library recorded at 16 velocity layers sounds completely different at velocity 40 versus velocity 110. Drum kits map velocity to different single-hit samples so ghost notes and accents feel natural. If your keyboard cannot generate the full 0 to 127 range, or if the curve compresses everything into the middle, you lose access to those softer and louder layers entirely.
Understanding Velocity Curves
A velocity curve is a graph with input on the X axis and output on the Y axis. Input represents what your fingers physically produce. Output represents the MIDI value that reaches your DAW. On a perfectly linear curve, an input of 50 percent maps to an output of 50 percent, so pressing the key halfway gives you velocity 64. Reshaping that line is how you fix keyboards that feel too soft, too loud, or inconsistent across the range.
Most controllers ship with a default linear curve plus a handful of presets like Soft, Hard, Wide, and Fixed. The curve editor inside your DAW works the same way but gives you finer control, often with draggable points along the line. Some DAWs and standalone tools like VelPro even let you draw a unique curve for every individual note on the keyboard, which solves the problem of certain keys sensing harder or softer than their neighbors.
The key insight is that velocity curves are a translation layer between your physical technique and your software. The same keyboard can feel completely different with two curve settings, and the right choice depends on your keybed quality, your playing style, and the instrument you are triggering. There is no universally correct curve, only the one that makes your performance feel natural.
Types of Velocity Curves Explained
Velocity curves fall into a small set of shapes, and knowing what each one does tells you when to reach for it. Here are the five you will encounter on most keyboards and DAWs.
Linear Velocity Curve
A linear curve produces output that matches input in a straight, proportional line. If you press with 30 percent force, you get roughly velocity 38. This is the most neutral starting point and the one our team recommends testing first, because it gives you an honest picture of how your keybed actually responds before you start compensating.
Convex (Soft) Velocity Curve
A convex curve bows upward, meaning small inputs already produce relatively high velocity values. This makes a stiff or heavy keybed feel more sensitive and easier to play softly, which is useful for cheap mini controllers that struggle to register gentle presses. The trade-off is that you lose resolution in the loud range because the curve flattens near the top.
Concave (Hard) Velocity Curve
A concave curve bows downward, so you need to press harder to reach higher velocities. This tames a keyboard that feels too sensitive or that jumps to maximum velocity too easily. Heavy-handed players and drum programmers often prefer this shape because it gives them more headroom for accents.
Saturated (Logarithmic) Velocity Curve
A saturated curve applies a logarithmic or S-shaped mapping that compresses the extremes while expanding the middle. This is popular for orchestral sample libraries where most expressive playing happens in the 40 to 100 range and you rarely need the very bottom or very top. It keeps soft notes audible without letting every accidental hard hit max out at 127.
Fixed Velocity
Fixed velocity ignores input entirely and sends the same value on every Note On, often 100 or 127. This is useful for electronic music where you want uniform drum hits or steady synth stabs, but it is also the setting users accidentally enable and then wonder why their keyboard feels lifeless. If your dynamics suddenly vanish, check whether a Fixed or Constant velocity mode got switched on.
How to Set Up Velocity Curves in Your DAW
The most flexible place to adjust velocity is inside your DAW, because you can change curves per track, per instrument, or even per note in the piano roll. The steps below cover the four DAWs producers ask us about most often. The general workflow is the same in every case: find the velocity processing section, pick or draw a curve, then test by playing and watching the incoming values.
How to Set Up Velocity Curves in Logic Pro
Logic Pro handles velocity curves through MIDI plug-ins on a software instrument track. Open the Track inspector, click the MIDI FX slot, and choose Velocity Processor. The Velocity Processor plug-in gives you a curve editor with draggable points, plus an Output Scale knob to compress or expand the range. Drag the curve upward in the low input zone if soft notes are too quiet, or flatten the top if loud hits keep pinning at 127.
For global curve changes across all tracks, use the Environment window. Create a Transformer object, set its conditions to affect Note events, and apply a Velocity operation with the Scale or Add mode. Cable your physical input through the Transformer before it reaches the sequencer input. This gives every track the same remapped velocity without touching individual instruments.
How to Change MIDI Keyboard Sensitivity in FL Studio
FL Studio gives you two main options. The quickest is the built-in Velocity control on the Channel Rack wrapper for each instrument. Click the wrench icon on a plugin wrapper, find the Velocity section under the Misc tab, and drag the Velocity knob or adjust the curve graph to reshape how incoming velocity scales the sound.
For keyboard-level remapping, open the MIDI Settings panel from the Options menu, select your controller in the input list, and use the Velocity curve dropdown. FL Studio offers Linear, Brisk, Slow, and Custom options. Custom opens a small graph where you can drag points to draw your own curve. This adjustment applies to all incoming MIDI from that controller before it reaches any plugin.
How to Adjust MIDI Keyboard Sensitivity in Ableton Live
Ableton Live applies velocity curves at the instrument level rather than globally. On any MIDI track, drop the Velocity MIDI effect before your instrument. The Velocity device has a simple slider for overall scaling plus an Invert button and a Drive control that compresses the curve toward the extremes. Combine it with the Velocity device’s Comp(ression) knob to bring soft notes up without capping loud notes.
If you want a true curve editor in Live, use a Max for Live device like Velocity Curve or install a third-party MIDI tool. Stock Live does not expose a draggable curve graph on the keyboard input itself, so the Velocity MIDI effect plus compression is the practical workaround for most users.
How to Set Up Velocity Curves in Cubase
Cubase gives you the MIDI Modifiers panel, which is one of the most powerful velocity tools in any DAW. Select your MIDI or instrument track, open the Inspector, and expand the MIDI Modifiers section. Here you find Velocity Shift, Velocity Compression, and Velocity Limit controls. Compression below 100 percent expands the curve so quieter inputs reach higher velocities, while values above 100 percent compress the dynamic range.
For more detailed curve editing, use the Logical Editor or the Input Transformer. These let you set conditional rules that remap velocity based on note range, channel, or any other MIDI attribute. Cubase power users often build a preset that boosts velocity below 60 and tames anything above 110, which solves the bunching problem cheap controllers suffer from.
How to Set Up Velocity Curves on Windows and Mac
Before the signal reaches your DAW, both Windows and Mac give you ways to test and sometimes shape incoming MIDI. Neither operating system has a built-in global velocity curve editor, but the tools below help you verify your keyboard is sending the right values and apply a fix if needed.
Windows Setup
On Windows, install MIDI-OX (free) to monitor incoming Note On velocity values in real time. Play softly, medium, and hard, then check whether the values span the full 0 to 127 range. If your keyboard tops out around 100 or 110, you know the curve needs a boost in the upper range. MIDI-OX can also remap velocity using its data mapping feature, though most users prefer to do this inside the DAW for flexibility.
If your keyboard came with a manufacturer utility (such as the Arturia MIDI Control Center, M-Audio Preset Editor, or Novation Components), install it. These apps often expose a hardware velocity curve setting that persists across all software, which is cleaner than remapping inside every DAW you use.
Mac Setup
On Mac, use the free Audio MIDI Setup utility to confirm your keyboard is recognized, then use a tool like Snoize MIDI Monitor to watch incoming velocity values. The workflow is the same as on Windows: play across the dynamic range and note where the values cluster.
For actual curve editing on Mac, the cleanest path is the manufacturer utility mentioned above or a DAW-level adjustment. Mac does not include a system-wide MIDI velocity remapper, so if you switch between Logic, Ableton, and standalone instruments, set the curve on the keyboard hardware itself for consistency.
Hardware vs Software Velocity Curve Settings
You can adjust velocity curves in two places: on the keyboard itself, or inside your DAW. Each approach has trade-offs, and the right choice depends on how you work.
Hardware curves live in your keyboard firmware or a companion editor app. They apply to every app that receives MIDI from the controller, which is ideal if you use multiple DAWs or standalone instruments. The downside is limited granularity. Most hardware editors offer a handful of presets and maybe a few user curves, not the fine-grained point editing you get in software.
Software curves inside your DAW are more flexible and reversible. You can save different curves per project, per instrument, or per track. The limitation is that they only affect that specific DAW, so you have to redo the setup if you switch software. Our team generally recommends setting a sensible default on the hardware side and then fine-tuning inside the DAW when a specific instrument demands it.
For users who want a hardware-only solution that works with any setup, the MIDI Solutions Velocity Converter is a small box that sits between your keyboard and computer and remaps velocity in real time. Forum users who need a set-and-forget fix trust it, though it adds cost and cabling to your rig.
Choosing the Right Curve for Your Playing Style
The curve you settle on depends on what you play and what instrument you trigger. Here is how our team approaches the most common scenarios.
For piano and acoustic instrument libraries, start with linear and adjust based on the sample layers you hear. If soft notes disappear, nudge the low end of the curve up. If every loud hit sounds the same, flatten the top so you have headroom for true fortissimo. Orchestral and film scoring libraries often benefit from a slightly saturated curve that keeps the expressive midrange detailed.
For drum programming, a concave or hard curve works well because it gives you clean separation between ghost notes, normal hits, and accents. You want quiet taps to stay quiet and hard hits to spike, which is exactly what a downward-bowing curve produces. Many producers also layer a fixed-velocity kick or snare alongside dynamic drums for consistency.
For synths and electronic pads, fixed velocity is a valid creative choice when you want uniform stabs. If you want expression, a convex curve on a cheap mini keybed can compensate for stiff keys that barely register soft presses. Trust your ears over the graph. If the performance feels musical and the dynamics sit right in the mix, the curve is correct.
Troubleshooting Common Velocity Issues
Forum discussions reveal a handful of recurring velocity problems. Here are the fixes our team reaches for first.
Notes sound the same loudness no matter how hard you play. This usually means Fixed Velocity is enabled on the keyboard or in the DAW. Check the controller manual for a velocity mode button or a setting in the editor app, then verify the DAW is not set to a constant velocity input mode. In FL Studio, for example, the typing keyboard input has a fixed velocity toggle that catches people off guard.
Velocities bunch up between 80 and 110 and never reach 127. This is common on budget 25-key controllers with limited sensing hardware. Fix it by applying a convex curve in your DAW that expands the upper range, or use a velocity compression setting above 100 percent in Cubase MIDI Modifiers. MIDI-OX or MIDI Monitor will confirm whether the keyboard itself is the bottleneck.
Soft notes do not trigger at all. Many sample libraries have a minimum velocity threshold below which no sound plays. If your curve sends values under 20 for soft presses, raise the floor using a Velocity Limit or Output Scale control. Alternatively, shift the entire curve up slightly so the quietest playable note still lands around velocity 25.
The keyboard feels inconsistent across different octaves. Individual keys on older or cheaper controllers can drift in sensitivity. A per-note curve editor like VelPro or a Cubase Input Transformer rule lets you compensate key by key. If only one or two keys are affected, the hardware may need cleaning or the sensor may be failing.
Switching keyboards changes the feel of every project. Different keybeds produce different raw velocity ranges, so a curve dialed in for one controller will not translate. Set a hardware curve on each keyboard so both output a similar range, or save DAW-specific velocity presets per controller and swap them when you change hardware.
MPE as an Alternative to Traditional Velocity
MIDI Polyphonic Expression, or MPE, is a newer approach that gives each note its own MIDI channel and continuous expression data. Instead of relying on a single velocity value captured at the moment of key press, MPE-capable controllers send ongoing pressure, slide, and lift information per note. This lets you shape a note after the initial strike, which traditional velocity cannot do.
MPE does not replace velocity curves, but it reduces how much you depend on them for expression. If you work with MPE-aware instruments in Logic Pro, Ableton Live, or Bitwig, a lot of the dynamic shading that used to come from velocity now comes from pressure and release gestures. Film composers told us they often bypass velocity entirely and use CC#1 mod wheel or CC#11 expression for dynamics on orchestral libraries, since those controls are continuous rather than fixed at note onset.
If your keyboard supports MPE, experiment with combining a simple linear velocity curve for the initial attack with per-note pressure for sustain expression. You may find you need less aggressive velocity tweaking once continuous controllers take over the expressive heavy lifting.
Frequently Asked Questions
How do I set up velocity curves on my MIDI keyboard?
To set up velocity curves, start by testing your keyboard’s raw velocity range using a monitor tool like MIDI-OX or MIDI Monitor. Then open your DAW’s velocity processor (Velocity Processor in Logic Pro, Velocity MIDI effect in Ableton, MIDI Modifiers in Cubase, or the MIDI Settings velocity curve in FL Studio) and adjust the curve so soft presses reach roughly velocity 30, medium presses sit around 70, and hard hits reach 120 or higher. Test with the instrument you plan to play and fine-tune by ear.
Which velocity curve should I use with my controller keyboard?
Start with a linear curve to see how your keybed naturally responds. If soft notes are too quiet, switch to a convex or soft curve. If loud notes max out too easily, try a concave or hard curve. For orchestral and acoustic sample libraries, a slightly saturated curve often works best because it keeps the expressive midrange detailed. For drums, a concave curve gives clean separation between ghost notes and accents.
How do I change MIDI keyboard sensitivity in FL Studio?
In FL Studio, open Options and select MIDI Settings, then choose your controller from the input list. Use the Velocity curve dropdown to pick Linear, Brisk, Slow, or Custom. Custom opens a graph where you drag points to draw your own curve. You can also adjust velocity per instrument using the Velocity control under the Misc tab in the plugin wrapper.
Why is my MIDI keyboard not responding to dynamics?
The most common cause is Fixed Velocity being enabled on the keyboard or in the DAW. Check your controller’s manual for a velocity mode toggle, and verify your DAW is not set to constant velocity input. Other causes include a velocity curve that compresses everything into a narrow range, a sample library with a high minimum velocity threshold, or a failing key sensor on older hardware.
How do I set up velocity curves on a MIDI keyboard on Windows and Mac?
Neither Windows nor Mac includes a built-in global velocity curve editor. On Windows, use MIDI-OX to monitor and remap velocity. On Mac, use MIDI Monitor to check values and adjust the curve in your DAW or the keyboard manufacturer’s editor app. Setting the curve on the keyboard hardware itself is the most consistent option if you use multiple DAWs.
Conclusion
Setting up velocity curves on a MIDI keyboard is the single biggest improvement you can make to how expressive your performances feel. Start with a linear curve, test your raw velocity range, then shape the mapping in your DAW or on the keyboard hardware until soft, medium, and loud hits all land where you expect. The steps in this guide work across Logic Pro, FL Studio, Ableton Live, and Cubase, and the troubleshooting section covers the issues producers hit most often.
Your next step is to pick one instrument you know well, dial in a curve that feels right, and save it as a preset. Once you have a baseline that matches your playing style, every future project starts from a place that already feels musical. Knowing how to set up velocity curves on a MIDI keyboard gives you that foundation for every production you take on in 2026 and beyond.