New session property

[ardour-manual] / include / stem-exports.html

diff --git a/include/stem-exports.html b/include/stem-exports.html
index 753a4e4c77486cd38a921d55e61087ac923831e4..92edf6fbeb4aaec8b64837b7338fe8d10539c348 100644 (file)
--- a/include/stem-exports.html
+++ b/include/stem-exports.html
@@ -1,11 +1,30 @@
 
+<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 exports</dfn> are covered fully in the <a href="@@mixdown">Export</a>
-  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.
-</p>
-<p>
-  All data will be lost except the actual audio/MIDI (no plugins, no automation).
+  <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 &gt; Export &gt; Stem Export&hellip;</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>
\ No newline at end of file