Adding doc about Cleaning up Sessions

diff --git a/_manual/07_working-with-sessions/10_cleaning_up.html b/_manual/07_working-with-sessions/10_cleaning_up.html
new file mode 100644 (file)
index 0000000..63cb5be
--- /dev/null
+++ b/_manual/07_working-with-sessions/10_cleaning_up.html
@@ -0,0 +1,67 @@
+---
+layout: default
+title: Cleaning up Sessions
+---                        
+  
+<p>Recording and editing any serious session might leave the session with some
+  unused or misplaced files here and there. Ardour can help deal with this clutter thanks
+  to the tools located in the <kbd class="menu">Session &gt; Clean-up</kbd> menu.
+</p>
+
+<h2>Bring all media into session folder</h2>
+
+<p>When <a href="/adding-pre-existing-material/">importing media files</a>, if
+  the <kbd class="option">Copy files to session</kbd> hasn't been checked, Ardour uses
+  the source file from its original destination, which can help avoiding file duplication.
+  Nevertheless, when the session needs to be archived or transfered to another computer, moving
+  the session folder won't move those <em>external</em> files as they are not in the folder, as seen
+  in <a href="/working-with-sessions/backup-and-sharing-of-sessions/">Backup and sharing of sessions</a>.
+</p>
+
+<p>Using the <kbd class="menu">Bring all media into session folder</kbd> menu ensures
+  that all media files used in the session are located inside the session's folder, hence avoiding
+  any missing files when copied.
+</p>
+  
+<h2>Reset Peak Files</h2>
+
+<p>Ardour represents audio waveforms with peak files, that are graphical images generated from the
+  sound files. This generation can be time and CPU consuming, so it uses a cache of the generated
+  images to speed up the display process.
+</p>
+
+<p>Using the <kbd class="menu">Reset Peak Files</kbd> menu allows to reset this cache, which frees up disk space.
+  note, though, that displaying waveforms requires these peak files, so they'll be recreated by Ardour, 
+  consuming CPU and time. It can prove useful if some waveforms are not used anymore, or if a graphical glitch happens.
+</p>
+
+<h2>Clean-up Unused Sources...</h2>
+
+<p>Recording usually lefts behind a lot of unused takes, be it in midi or audio form, that can clutter
+  the Region List, and eat up a lot of hard drive space. While its generally a good practice to keep as
+  many things as possible while recording, when transferring or archiving the session, some clean up can
+  help a lot in reducing the sessions clutter and size.
+<p>
+
+<p>Selecting <kbd class="menu">Clean-up Unused Sources...</kbd> will force Ardour to detect those unused waveforms
+  by looking for unused regions, and (through a prompt) for unused playlists. The media files won't be destroyed, though.
+  At this stage, they are just copied in a particular place of the session path (namely, in the <code>dead sounds/</code>
+  sub-folder).
+</p>
+
+<h2>Flush Wastebasket</h2>
+
+<p>Although Ardour is a <em>non-destructive</em> audio-editors, it allows for a very careful destruction of unused media materials.
+  This function is closely linked to the previous one. When the unused sources have been cleaned up and quarantined, the 
+  <kbd class="menu">Flush Wastebasket</kbd> menu will allow for their physical destruction.
+</p>
+
+<p>As a safeguarding mechanism though, Flushing the wastebasket in impossible in the same working session as the Cleaning up of unused sources :
+  the user needs to close the session and reload it before flushing. It allows to test the playback of the session and ensure both that Ardour didn't commit
+  any mistake (unlikely, but better safe than sorry), and that the user is absolutely sure of what he does.
+</p>
+
+<p class="warning">Notice that all media destroyed this way is not sent to the system's <em>trash can</em> but permanently deleted. 
+  If a file is mistakenly destroyed this way, the user will have to rely on data recovery techniques to try getting it back.
+</p>
+