Alexandre Prokoudine
608be06e83
Mostly requires an updated screenshot, the old text wasn't deniying the possibility of stem-exporting MIDI data as MIDI data.
30 lines
1.3 KiB
HTML
30 lines
1.3 KiB
HTML
|
|
<figure class="right">
|
|
<img src="/images/export-dialog-stem-export.png" width="500px" alt="Stem export">
|
|
<figcaption>
|
|
The Stem Export dialog
|
|
</figcaption>
|
|
</figure>
|
|
|
|
<p>
|
|
<dfn>Stem exporting</dfn> allows to transfer files between different systems and
|
|
programs by exporting each track individually, including silence, to keep them
|
|
in sync. All data will be lost except the actual audio/MIDI.
|
|
This is one of the most common methods of interchange because it works between
|
|
all DAWs.
|
|
</p>
|
|
<p>
|
|
The <kbd class="window">Stem Export</kbd> window, accessed via the
|
|
<kbd class="menu">Session > Export > Stem Export…</kbd> menu,
|
|
is very similar to the <a href="@@export-dialog">Export dialog</a>, except the
|
|
'Channels' tab appears slightly differently: in this case each chosen channel
|
|
(track or bus) is exported to its own file, instead of all channels being mixed together into a single file.
|
|
</p>
|
|
<p>
|
|
The exported tracks or busses can, by checking <kbd class="option">Apply
|
|
track/bus processing</kbd>, be exported with the effects/processors applied,
|
|
so that the destination system does not need those effects plugins.
|
|
</p>
|
|
<p>
|
|
The toolbar in the Stem Export window also provides a quick way to select either audio or MIDI tracks or busses.
|
|
</p> |