Recording an MPE performance live from a controller captures nuance that's genuinely hard to program from scratch — but it also captures every inconsistency in the take. Bitwig Studio's note editor lets you go back into a recorded performance and reshape individual expression curves directly, without re-tracking the gesture on hardware. Here's how to actually use it.
Finding the Expression Lanes
Once MPE data is recorded onto a track — whether from a ROLI Seaboard, a LinnStrument, or Expressive E's Osmose — opening the note editor reveals separate lanes for each expression type Bitwig tracks per note: pitch, pressure, gain, and slide (timbre/Y-axis). Selecting a single note isolates its curves from the rest of the phrase, so adjustments don't bleed into neighboring notes the way global automation would.
Reshaping Pressure Without Re-Recording
Pressure curves are the most commonly hand-edited lane, since they drive filter movement, volume swells, or timbral brightness on most MPE-responsive instruments. Clicking directly on a note's pressure lane lets you drag control points to smooth out an inconsistent squeeze, exaggerate a swell that was too subtle when played live, or flatten a curve entirely for a note that should stay static. Because this happens directly on the recorded note rather than through a separate automation lane, the edit stays locked to that note even if you move it earlier or later in the arrangement.
Gain and Slide Curves Work the Same Way
The same click-and-drag approach applies to gain (per-note volume shaping independent of velocity) and slide, the Y-axis data most controllers use for continuous timbral movement. A common workflow is recording a rough pass live to capture the overall gesture shape, then going note by note to clean up the specific curves that didn't land — tightening a slide that overshot, or adding a gain swell to a note that felt flat in the original take.
Why This Matters for Audio Events Too
Bitwig extends this same on-note editing to audio events, not just MIDI notes, which is a meaningful detail for anyone building expressive parts out of sampled or resampled material rather than purely synthesized instruments. The same pressure and gain-shaping workflow applies whether the underlying sound source is a soft synth or a recorded audio clip.
A Faster Path Than Re-Tracking
The practical value here is speed. Before this level of on-note editing existed, fixing one bad gesture in an otherwise good take usually meant re-recording the whole phrase from the controller and hoping the rest came out cleaner. Editing curves directly cuts that down to adjusting just the note that needs it — a workflow closer to editing MIDI velocity or automation than to re-performing a part.
Getting the Most Out of It
A few habits make this workflow faster in practice. Record a full take first rather than trying to get every gesture perfect on the first pass — it's faster to fix two or three notes afterward than to re-record an entire phrase chasing a single clean take. Zoom in on the note editor before adjusting curves; expression data is dense enough that small drags at a zoomed-out view can overshoot. And compare a hand-edited curve against a well-played reference note nearby, since Bitwig's curves are easy to over-smooth into something that reads as programmed rather than performed.
For composers and sound designers doing detailed MPE work rather than pure live performance, this kind of precise, per-note editing is often what separates a rough sketch from a finished part — and it's available without needing a second, cleaner take from the controller at all.