Update 'Save a Template'

This commit is contained in:
Alexandre Prokoudine 2022-04-21 02:04:08 +03:00
parent f9aef222d0
commit ef2e6346da
5 changed files with 33 additions and 31 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

View File

@ -2,53 +2,55 @@
title = "Saving a template" title = "Saving a template"
chapter = false chapter = false
weight = 3 weight = 3
#pre = "<b>1. </b>"
+++ +++
If you often go through the motions of setting up the same information If you often go through the motions of setting up the same information in each
in each new Session you create, such as the number of input and output new session you create, such as tracks/busses, their names and interconnections, what plugins with what settings you have in mixer channels
Channels, the number and names of Tracks or Busses, or the Routing, then etc., then you may wish to create a _template_ instead.
you may wish to create a Template of that information instead.
With a **Template**, you can save the state of a currently open Session With a _template_, you can save the state of a currently open session _without_
*without* all the Region information files. Templates are useful if, for all the region information files. Templates are useful if, for example, you're
example, you're doing extensive Routing on Tracks and Buses and want to doing extensive routing on tracks and busses and want to save the _Editor_
save the Editor Window's state for use in other Sessions. An example window's state for use in other sessions.
might be a Template to record Tracks of drums, bass, guitar and vocals,
each with their own input on the soundcard, which you might use as a An example might be a template to record tracks of drums, bass, guitar and
basis for each Session you created in that situation. vocals, each with their own input on the soundcard, which you might use as a
basis for each session you created in that situation.
## Save a Template ## Save a Template
You can save a new Template from the Main Menu: *Session > Save Template*. You are asked to give the new Template a name: You can save a new template from the main menu: `Session > Save Template`. You
are asked to give the new template a name and optionally provide a description that will show up in the _Session Setup_ dialog:
![template1](en/Ardour4_Save_Template_1.png) ![template1](en/ardour7-save-template.png)
## Load a Template ## Load a Template
When creating a new Session, you can load up a previously saved Template: When creating a new session, you can load up a previously saved template. All
you will need is to tell Ardour where on the disk to save the session:
![template2](en/Ardour4_Save_Template_2.png) ![template2](en/ardour7-session-setup.png)
In summary: Session Templates are a way to store the setup of a session for future use. They do not store any audio data but can store:
* The number of tracks and busses, along with their names.
* The plugins present on each track or bus (if any).
* All I/O connections.
## Conclusion ## Conclusion
Congratulations, you have reached the end of this introduction to Ardour! We hope that this tutorial has been useful for you to learn the key functions of Ardour. Congratulations, you have reached the end of this introduction to Ardour! We
hope that this tutorial has been useful for you to learn the key functions of
the program.
In the following section, the **Appendices**, we have included some In the following section, the **Appendices**, we have included some extra
extra information we thought would be useful to new users of Ardour, information we thought would be useful to new users of Ardour, including how to
including how to get [**Further Help**](../further-help), a [**Glossary**](../glossary) of technical terms get [**Further Help**](../further-help), a [**Glossary**](../glossary) of
used in this manual, some [**Links**](../links) to further information about Ardour technical terms used in this manual, some [**Links**](../links) to further
on the Internet and, last but not least, the [**Credits**](../credits) of those information about Ardour on the Internet and, last but not least, the
involved in creating this Free/Libre Open Source Software (FLOSS) Manual. [**Credits**](../credits) of those involved in creating this free/libre
open-source software (FLOSS) manual.
Thanks for reading, and if you have some knowledge about Ardour that is Thanks for reading, and if you have some knowledge about Ardour that is not
not included here, please feel free to propose changes (more info on how to do it: [**How to Contribute**](../how-to-contribute-0/). Also, this manual itself is fully open source and lives at [https://github.com/brunoruviaro/ardour4-tutorial](https://github.com/brunoruviaro/ardour4-tutorial). You can even fork it and create your own customized version of it! included here, please feel free to propose changes (more info on how to do it:
[_How to Contribute_](../how-to-contribute/). Also, this manual itself is fully
open-source and lives at
[GitHub](https://github.com/prokoudine/ardour-tutorial).
You can even fork it and create your own customized version of it!
**Appendices:** **Appendices:**
[FURTHER HELP](../further-help) || [FURTHER HELP](../further-help) ||