25 lines
1.1 KiB
HTML
25 lines
1.1 KiB
HTML
|
---
|
||
|
|
layout: default
|
||
|
|
title: Session Templates
|
||
|
|
---
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<p>Session templates are a way to store the setup of a session for future (re)use. They do not store any <em>data</em> but do store (for example):</p>
|
||
|
|
<ul>
|
||
|
|
<li>The number of tracks and busses, along with their names
|
||
|
|
</li>
|
||
|
|
<li>The plugins present on each track or bus (if any)
|
||
|
|
</li>
|
||
|
|
<li>All I/O connections
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<h3>Creating a Session Template</h3>
|
||
|
|
<p>Choose <code>Session > Save Template</code>. A dialog will appear to ask you for the name of the new template.</p>
|
||
|
|
<h3>Using a Session Template</h3>
|
||
|
|
<p>In the New Session dialog, choose the desired template from the combo selector.</p>
|
||
|
|
<p>Note that you can also use an existing session as a template, without saving it as one. This is available as an option in the New Session dialog. Doing this will not alter the existing session at all, but will use its track, bus and plugin configuration just like a template.</p>
|
||
|
|
<p>See also <a href="/missing">Track & Bus templates</a> for information on templates for individual tracks or busses.</p>
|
||
|
|
|