Many musicians record an MPE performance, bounce it to audio, and move on. That works for the finished track, but it throws away the most valuable part: the gesture data that produced the sound. Keeping the raw MIDI alongside your audio gives you freedom to change instruments, fix small mistakes, and revisit ideas years later. Here is why it matters and how to build a simple archiving habit.
What an MPE take actually contains
A normal MIDI clip holds notes, velocities, and a few controller moves. An MPE clip also holds per-note pitch bend, pressure, and slide for every note, usually spread across many channels. That data describes how your fingers moved. Audio only records what one particular sound did in response.
If you later decide the patch is wrong, an audio file cannot be re-voiced. The MIDI can. Replace the instrument, keep the performance, and the same gestures drive a new sound. For an overview of the underlying standard, see the MIDI Association and our introduction, What is MPE?
Reasons to keep the MIDI
- Re-voicing. Swap a synth for a different one, or an orchestral library for a physical modeling plugin, without replaying the part.
- Editing. Correct a single stray pitch glide or smooth a pressure spike instead of rerecording a whole take.
- Future compatibility. New synths and updates frequently improve MPE handling. Old takes can sound better on newer engines.
- Learning. Looking back at your own expression curves shows how your technique develops over time.
Check that your DAW stores it properly
Before relying on any clip, confirm that your host keeps the per-note data. Some hosts handle MPE natively, while others need a setting enabled or a particular track type. Play a short phrase with obvious pitch glides, then reopen the project and check that the glides survive. Documentation from Ableton, Bitwig, and Apple Logic Pro explains how each handles multi-channel MIDI. If you discover a problem, our roundup of DAW MPE support is a good place to compare options.
Export a standard MIDI file as a backup
Project files can become unreadable when plugins disappear or hosts change. A standalone MIDI file is much more durable. Export each important MPE clip as a MIDI file and store it with the project. Make sure the export retains all channels instead of merging them into one, then test by importing the file into a fresh project.
A simple naming and folder system
You do not need an elaborate archive. A consistent structure is enough:
- One folder per project, with subfolders for audio and MIDI.
- File names that include the date, the controller used, and the instrument, for example "2026-11-02_osmose_strings-idea".
- A short text note listing the pitch bend range and any special settings, because mismatched ranges are a common reason old takes sound wrong when reopened.
Capture mistakes too
Some of your best material is accidental. A slip of the finger can create an interesting glide or a surprising swell. If you record continuously while sketching, you will have the raw material to extract those moments later. Storage is cheap, and MPE data is small compared with audio.
The takeaway
Treat your MPE MIDI as source material, not scrap. Bounce audio for convenience, but keep the original performance, export a backup file, and note the settings you used. In a few months, when you want a different sound for the same phrase, you will be glad that your hands' work was saved and not just the sound it made.