manual/include/stem-exports.html


<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. 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.
</p>
Rearrangement and cleanup of Part I. This includes rewriting out all of the "you" language that was peppered throughout, fixing inconsistencies in layout, and removing <br>s wherever they were misused and unnecessary (which was quite a lot). 2017-02-25 00:30:29 -05:00
copy-editing chapter 7. 2014-02-04 19:17:18 -05:00			`<p>`
Rearrangement and cleanup of Part I. This includes rewriting out all of the "you" language that was peppered throughout, fixing inconsistencies in layout, and removing <br>s wherever they were misused and unnecessary (which was quite a lot). 2017-02-25 00:30:29 -05:00			`<dfn>Stem exports</dfn> are covered fully in the`
Catching the last non-unbreakable links 2017-02-17 08:46:43 -05:00			`<a href="@@mixdown">Export</a> chapter. A stem export creates one file`
copy-editing chapter 7. 2014-02-04 19:17:18 -05:00			`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.`
			`</p>`
Move content from _manual/ to include/. 2017-02-13 14:53:37 -05:00