5 — Exporting Mixes
Export turns a sequence into audio. Everything you hear in the preview is baked in — splices, splits, sample and voice lanes, EQ moves, stem blends and tempo changes.
Exporting
On the Timeline, click Export ⤓. Choose your options, confirm, and the render runs. Finished files land in ~/Music/MixMind Exports and appear under Rendered mixes in DJ ▸ Mixes.
Options
| Option | Notes |
|---|---|
| Format | MP3 for sharing and upload, WAV for archives and further editing |
| Bit depth | 24-bit available for WAV — use it if the mix is going on for more work |
| Auto-gain | Levels the finished mix. Leave on unless you're mastering downstream |
| Tracklist (.txt) | Numbered running order with timestamps, key and BPM |
| CUE sheet | Chapter markers for players and broadcast systems that read CUE |
| Split per track | One file per track instead of one continuous mix |
Export is not the preview
Two things are deliberately different in an export, both in your favour:
Stems are re-separated at full quality. While you work, stems are small — mono, 22.05 kHz — which is fast and completely adequate for driving a blend you never hear in isolation. At export the engine separates again at full stereo, so the finished audio isn't limited by the working copies.
This is re-separation, not upsampling. Converting a small file to a bigger one recovers nothing; producing it again at full rate does.
The render is offline. It doesn't play in real time — it renders the exact graph as fast as the machine allows. A long mix with stem blends takes minutes, mostly in separation.
Tracklists
The .txt tracklist is a numbered running order with timestamps. It's what you paste into a SoundCloud or Mixcloud description, and it's the format the Training Center reads — so a tracklist you export can be fed back in to teach the system that set's style.
CUE sheets
A CUE sheet marks where each track starts inside one continuous audio file. Broadcast systems and some players use it to show track changes and let listeners skip. Export it alongside the audio and keep the two together — a CUE references its audio file by name.
Split per track
Renders each track as its own file, with its blends applied at the edges. Useful when you want the individual pieces for a radio system that schedules track by track, or to hand stems of a set to someone else.
Where files go
Everything lands in ~/Music/MixMind Exports. Mixx Intelligence writes there without asking each time, so a long export doesn't stall on a save dialog.
After exporting
Rendered audio is frozen. If a blend is wrong, don't edit the audio — open the sequence, fix the transition, and export again. See 3 — Manage Your DJ Mixes.
Mashup exports
The Mashup canvas exports to audio only, and can't be sideloaded into a DJ mix. To use a mashup inside a set, export it as a WAV, add that file to your library, and treat it as a track. See 10 — Mashup.