X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fstem-exports.html;h=6d9713073eec674bea027f5570d387385be34903;hb=500fea9a1bb2e8f8b815b11ed26c88e32eb7e139;hp=cde2c11a7b380bad9467b0759e1381d595424c2f;hpb=94819e4ffb5316bb14d189f40bb615d08431fbc0;p=ardour-manual diff --git a/include/stem-exports.html b/include/stem-exports.html index cde2c11..6d97130 100644 --- a/include/stem-exports.html +++ b/include/stem-exports.html @@ -1,10 +1,28 @@ - + +
+ Stem export +
+ The Stem Export dialog +
+
+ +

+ 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. +

- Stem exports are covered fully in the - Export chapter. A stem export creates one file - per track, starting at the beginning of the session. You can then import - each track into another DAW and begin working on it. You lose all data - except the actual audio/MIDI (no plugins, no automation). This is one of - the most common methods of interchange because it works between all DAWs. + 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.