Using a transcribed piano MIDI in your DAW
A transcription is a recording of a human performance, not a programmed part. That single fact explains almost everything that surprises people in the first ten minutes after importing one.
First, check the pedal actually arrived
Before you conclude that a transcription has no sustain data, check that your DAW imported it. Controller data such as CC64 travels in the file alongside the notes, but not every DAW reads it in on import, and some put it somewhere less obvious than the piano roll.
Where to look:
| Cubase, Reaper, Studio One | The controller lanes underneath the piano roll in the MIDI editor. Choose the lane for CC64, sometimes listed as Sustain or Damper Pedal. |
|---|---|
| Logic Pro | The automation view inside the region, or the Event List, which shows every controller message as a line of text and is the most reliable way to confirm the data is there at all. |
| Ableton Live | Live has historically been unforgiving about controller data in imported MIDI files. If the sustain envelope looks empty after import, check the file in another editor before assuming the pedal is missing from it. |
| Anything else | An Event List or equivalent text view is the ground truth. If CC64 messages appear there, the file has them. |
The CC64 guide explains what the numbers mean and what a healthy pedal track looks like.
Do not quantise it by reflex
The notes will not sit on the grid, and they are not supposed to. A pianist plays a chord with a few milliseconds between the notes, pushes ahead in a phrase and pulls back at a cadence, and all of that is in the file. Quantising flattens the very thing that makes it sound played.
The right decision depends on what you are making:
- Driving a sampled piano. Leave the timing alone. That is where the realism lives.
- Layering with a programmed track. You need a tempo map, not quantisation. Most DAWs can derive tempo from the performance, which lets the grid follow the player instead of forcing the player onto the grid.
- Heading to notation. Here you do need quantisation, because a score has no way to write "slightly late". Do it as the last step, on a copy, after the notes are correct.
Match the velocities to your instrument
Velocity is a number, and every piano library interprets it differently. A file that sounds beautifully balanced on one instrument can sound harsh or lifeless on another, without a single note having changed.
If the result feels too aggressive, compress the velocity range rather than lowering the track volume: the point is the ratio between loud and quiet notes, not the overall level. If it feels lifeless, expand the range before you reach for the mix. Most DAWs have a velocity scale or compand function that does this over a whole selection at once. The velocity guide covers what a realistic spread looks like.
The four things worth fixing by hand
- Extra notes at the bottom. Low piano notes have dense overtones and a transcriber sometimes writes a harmonic as its own key. The bottom octave repays a look first.
- Merged notes in fast passages. Where notes crowd together, some get lost. Slow the audio to half speed and compare.
- Pedal changes a fraction early or late. Nudge them; do not redraw the lane. The shape is usually right.
- Note ends under a held pedal. How long a note is written to last, while the pedal holds it anyway, is partly a judgement call. If a passage sounds cluttered, shortening notes under the pedal is usually the fix, not removing the pedal.
What the file will not do for you
It arrives as one track containing both hands, because that is what the recording contained. Splitting it into two staves, working out which voice is which, and adding fingering or dynamic markings are notation tasks, and they come after the MIDI, whatever tool produced it.
Transcribe a recording