X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fstem-exports.html;h=6d9713073eec674bea027f5570d387385be34903;hb=a61fbacdfcb7a76fe425fada61f49fc85751e47a;hp=90ed1b2480c854f391f14a53928fcb7b66d75f26;hpb=081e7af0b6f6dec0ca685d3a538eacf20394c2cc;p=ardour-manual diff --git a/include/stem-exports.html b/include/stem-exports.html index 90ed1b2..6d97130 100644 --- a/include/stem-exports.html +++ b/include/stem-exports.html @@ -1,12 +1,28 @@ +
+ Stem export +
+ The Stem Export dialog +
+
+

- Stem exports are covered fully in the Export - chapter. A stem export creates one file per track, starting at the beginning of - the session. Each track can then be imported into another DAW. -

-

- All data will be lost except the actual audio/MIDI (no plugins, no automation). + Stem exporting allows to transfer files between different systems and + softwares 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.

+

+ The Stem Export window, accessed via the Session > + Export > Stem Export… menu, is very similar to the + Export dialog, 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. +

+

+ The exported tracks or busses can, by checking Apply + track/bus processing, be exported with the effects/processors applied, + so that the destination system does not need those effects plugins. +