Update/Rewrite 'Saving a Snapshot'

This commit is contained in:
Alexandre Prokoudine 2022-04-21 00:57:06 +03:00
parent 7409940cd8
commit d8efb4e7a8
7 changed files with 38 additions and 22 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 136 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 135 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

View File

@ -2,46 +2,62 @@
title = "Saving a snapshot" title = "Saving a snapshot"
chapter = false chapter = false
weight = 2 weight = 2
#pre = "<b>1. </b>"
+++ +++
Saving a **Snapshot** in Ardour is similar to saving your Session to a A _snapshot_ is a representation of the current state of a session at some point
new file, however using a Snapshot avoids overwriting the original in time. In a nutshell, it's like versioning your project by giving every
Session file. A Snapshot contains the current state of your work, while version a meaningful name.
sharing all the audio and data files of the Session.
Let's say you recorded a song in your home studio and you are trying different
arrangements to see which one works best. Instead of creating multiple sessions
and copying files between them, you can make snapshots every time you think you
have something worth preserving. At any point in time, you can save the current
state of the session and switch to an earlier snapshot to compare your
arrangements.
## Saving a Snapshot ## Saving a Snapshot
You can save a Snapshot via the menu: *Session > Snapshot* (shortcut "*Control*" + "*Shift*" + "*S*"). Ardour provides two commands in the _Session_ menu to create a snapshot:
![snapshots](en/Ardour4_Snapshot_Menu.png) **Snapshot (& keep working on current version)**
: You will create a new snapshot and continue working on the original version.
Mental model: "I think this is good enough, I might want returning to that
later, so I'll save a snapshot, undo, then carry on with my original idea
regardless".
By default the program will name the new Snapshot according to the **Snapshot (& switch to new version)**
current date and timestamp of your system. If you wish, you can change : You will create a new snapshot and switch to working on that version. Mental
the name to one that more meaningfully corresponds to the Session you model: "This is actually quite interesting, let's explore this idea further and
are working on. From the menu, you can also choose whether to save get back to the previous one if this turns out to be a dead end."
a snapshot and keep working on the present version, or save a snapshot
and switch immediately to that snapshot.
![snapshots](en/Ardour4_Snapshots_Name.png) ![snapshots](en/ardour7-snapshot-menu.png)
By default the program will name the new snapshot according to the current date
and timestamp of your system. If you wish, you can change the name to one that
more meaningfully corresponds to the session you are working on. From the menu,
you can also choose whether to save a snapshot and keep working on the present
version, or save a snapshot and switch immediately to that snapshot.
![snapshots](en/ardour7-snapshot-name.png)
## Recalling Snapshots ## Recalling Snapshots
You can recall a saved Snapshot via the '*Snapshots*' tab in the area on You can recall a saved snapshot via the _Snapshots_ tab in the area on the
the right: right:
![snapshot2](en/Ardour4_Snapshot_List.png) ![snapshot2](en/ardour7-snapshot-list.png)
There you see a few Snapshots that we created, and the '*my_session*' entry There you see a few snapshots that we created, and the _my\_session_ entry
represents the original state of our session. represents the original state of our session.
Click on any Snapshot from the list to reload it. Click on any snapshot from the list to reload it.
## Continuing ## Continuing
Sometimes it is helpful to have a default starting point for new Sometimes it is helpful to have a default starting point for new sessions, for
Sessions, for example for a set-up that you use all the time when starting a new project. To learn how example, for a setup that you use all the time when starting a new project. To
to do this, please continue to the next session called **Saving a Template**. learn how to do this, please continue to the next section called _Saving a
Template_.
Next: [SAVING A TEMPLATE](../saving-a-template) Next: [SAVING A TEMPLATE](../saving-a-template)