How to Export Separate Stems From OpenMPT? (October 2026) Guide

Ever finished a tracker module and wanted to remix it in a proper DAW, or hand the parts off to a mixing engineer? That’s where stem export comes in. In this guide, I’ll walk you through how to export separate stems from OpenMPT using Channel Mode and Instrument Mode, so you can pull individual tracks out of your module as clean audio files. No matter if you’re working on a game soundtrack, a chiptune album, or a remix, these steps will get your stems out of OpenMPT and into your next tool.

Understanding Channel Mode vs Instrument Mode in OpenMPT

Before you click any export button, you need to pick the right mode. OpenMPT offers two main ways to export separate stems, and they produce different results.

Channel Mode exports each pattern channel as its own audio file. A channel in OpenMPT is the playback lane where notes trigger instruments. If you have a drum sample on channel 1 and a bass on channel 2, Channel Mode gives you two separate files.

Instrument Mode exports each instrument as its own file. If multiple channels play the same instrument, they get mixed together into one stem. This is great when you want one clean file per sample library sound.

The choice depends on how you mixed in OpenMPT. If you layered instruments across channels for panning or volume shaping, Channel Mode preserves that. If you used one instrument per slot and want per-sound stems, Instrument Mode is cleaner. Pick the mode that matches how you want to mix the project later.

How to Export Separate Stems From OpenMPT Using Channel Mode

Channel Mode is the most common way to export separate stems from OpenMPT. Each of the 64 (or 32, depending on module type) channels renders to its own file, which keeps automation and panning intact.

Follow these steps to export stems using Channel Mode:

1. Open your module in OpenMPT and review the playback on the channels you want to export.
2. Click the File menu and select Stream Export.
3. In the export dialog, choose your output folder and file format (WAV, FLAC, MP3, or OGG).
4. Check the box labeled Channel Mode.
5. Set your sample rate and bit depth under the Render tab if needed.
6. Click Export and wait for OpenMPT to render each channel.

After the render finishes, OpenMPT drops one file per channel into your output folder. Files use the channel number as the prefix, so channel 1 becomes 01-Track.wav, channel 2 becomes 02-Track.wav, and so on. Empty channels still export, but they’re silent.

Tip: if your module has silence at the start, hold Shift and click the play position to set the export start point. This trims the leading silence from every stem.

How to Export Stems With Instrument Mode

Instrument Mode is the second build-in option for stem export and works best when you want one file per sample, not per playback lane.

Here’s the workflow for Instrument Mode export:

1. Open your module and go to File → Stream Export.
2. Select your output folder and preferred format.
3. Check the box labeled Instrument Mode instead of Channel Mode.
4. Adjust the render settings (sample rate, bit depth, normalize) as needed.
5. Click Export to render each instrument.

OpenMPT creates one file per instrument number. Files are named with the instrument slot, such as 01-Inst.wav, 02-Inst.wav, and so on. Any unused instrument slots still produce files, but they’re empty.

Instrument Mode is useful when you composed each instrument as a distinct sound and want clean per-sample stems for remixing. If you reused one instrument across multiple channels, all those notes land in the same output file.

File Format Options for OpenMPT Stem Export

OpenMPT supports several output formats for stem export, and the right choice depends on where the stems will go next.

WAV is the default for lossless quality. Pick this when you plan to import stems into a DAW for mixing or mastering. The files are larger, but the audio is uncompressed.

FLAC is a compressed lossless format. The files are smaller than WAV at the same quality, which helps when sharing stems over the internet.

MP3 uses lossy compression. Pick this only for previews or reference bounces. Avoid MP3 for final mixing, since the compression removes audio data that can affect your mix.

OGG Vorbis gives you better quality than MP3 at the same file size. Use it for previews or sharing demo bounces when MP3 isn’t required.

For mixing and mastering, always go with WAV or FLAC. Compressed formats make collaborative work harder because the DAW has to decode the audio in real time.

Render Settings: Sample Rate, Bit Depth, and Normalization

The Render tab in the Stream Export dialog controls the technical quality of your stems. Three settings matter most.

Sample rate sets how many times per second OpenMPT captures the audio. 44100 Hz matches CD quality and works for most projects. 48000 Hz is the standard for video and game audio. Match the sample rate of your target project to avoid resampling later.

Bit depth controls the dynamic range. 16-bit is the standard for CD and most consumer audio. 24-bit gives you more headroom for mixing and is the industry standard for production. Pick 32-bit float if you want extra headroom for quiet stems that will be heavily processed.

The normalize option raises the output volume so the loudest peak sits at 0 dB. This is helpful for sharing reference bounces, but turn it off when exporting for mixing. Normalizing pre-mix stems can cause clipping when the mixing engineer adds plugins and gain changes.

Additional options include slow render (more accurate but slower), dither (applies noise shaping when reducing bit depth), and write cue points (exports loop and marker positions as metadata).

Plugin Handling and Common Export Issues

VST plugins complicate stem export because OpenMPT handles them differently than built-in samples. By default, plugins don’t render to the exported audio unless you enable slow render.

OpenMPT’s Stream Export dialog has a Slow Render option. Turn this on whenever your module uses VST instruments or effects. Slow render processes the audio in real time, so plugins behave exactly as they do during live playback.

Common export issues come up in forum discussions. Users report that master effects like reverb and delay sometimes don’t appear on exported stems. This happens because OpenMPT processes effects at the channel level, not the master bus. If you want a wet signal on your stems, route the effect through a send channel and export that channel too.

Another issue is multi-song modules. OpenMPT only exports the first song in a .mptm file. If you need to export stems from additional songs, save each one as a separate module first. The same applies to .umx files with multiple soundtracks.

If you get silent or distorted stems, check the plugin buffer settings. Enable Clear plugin buffers in the export dialog to avoid leftover audio from a previous render.

Alternative: Using MIDI Export for Stems

Sometimes working with MIDI is faster than audio stems, especially when you want to reuse the notes themselves rather than the sounds. OpenMPT includes a MIDI Export option for this workflow.

Open the File menu and choose Export → MIDI. OpenMPT converts your module into a standard MIDI file. Each pattern channel becomes a MIDI track, and each note from your instruments becomes a MIDI note event.

MIDI export is useful for remixing because the notes stay editable. You can drop the MIDI file into a different DAW, swap the sounds, and reshape the arrangement without re-recording audio.

Keep in mind that MIDI export is a conversion, not a 1:1 copy. Volume commands, panning, and some effect commands don’t translate perfectly. You’ll need to clean up the MIDI before mixing. For pure audio stems, stick with Channel Mode or Instrument Mode.

Frequently Asked Questions

Conclusion

Exporting separate stems from OpenMPT comes down to picking the right mode and the right format. Channel Mode gives you one file per playback lane, which is perfect for preserving your mix decisions. Instrument Mode gives you one file per sound, which is cleaner for remixing.

For most production work, render to WAV at 24-bit and 44100 or 48000 Hz. Enable slow render if your module uses VST plugins, and route wet effects through a send channel if you want them on the stems. Use MIDI export only when you want to rework the notes themselves.

Now you have a workflow that works in 2026. Open up your module, run a Stream Export, and drop those stems into your DAW. If you hit a snag, the OpenMPT wiki and forum.openmpt.org are great resources for troubleshooting tricks.