3 Jul
2011
3 Jul
'11
10:20 p.m.
On Sun, Jul 3, 2011 at 4:14 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
Quite unrelated to all of this, I do have a question
about Ardour's 'Save' semantics.
wrong context, but OK ...
There are:
(1) 'Save'
(2) 'Save as'
(3) 'Snapshot'
and
(4) 'Periodic safety backups' (option)
and
(5) the 'save' as performed by 'Quit' or closing the main
window, in case "Save and quit" is selected from the dialog.
How do they all interact ? I could possibly find out with
some hours of experimentation, but I assume this has been
defined (and maybe documented) somehow.
In particular:
- Is there any difference between (2) and (3) except that
the one suggests a name and the other doesn't ? For both
the dialog says 'Name of New Snapshot'.
They both store session state in a file with a different basename than
the main session file. "Save as" additionally switches the current
"name" of the session to the newly chosen name, so that all future (1)
saves will be the new files. "Snapshot" does not do this, so that all
future (1) saves will continue to be to the normal, default session
file.
(4) saves the current session name (as possibly modified by "Save as")
.ardour.bak. This file exists purely for the use of the skilled user.
Ardour does not load it, check for its existence, etc, etc.
(5) is the same as (1).
Or put otherwise, is a snapshot made by (2) or (3)
guaranteed
not to modified later by (1), (4), (5), or not ?
a snapshot made by (3) will not be modified by 1, 2, 4 or 5. a
"snapshot" made by (2) will be modified by subsequent 1 or 5.
there is another potential saved state too, but you don't need to know
about that :)
--p