13 Jun
2012
13 Jun
'12
1:45 a.m.
On Tue, Jun 12, 2012 at 08:05:13AM -0400, Joe Hartley wrote:
On Tue, 12 Jun 2012 09:20:01 +0200
Atte André Jensen <atte(a)email.dk> wrote:
I made a habit of putting all my .ardour files in git when recording/mixing, and "git
commit -a" as often as I would save.
Then when I'd do something stupid, like move a fader on a group, realize it was a
group, hit UNDO, and then realize that undo doesn't undo fader moves, and then curse
and grind my teeth-- a mistake I made constantly--, I could just go "git reset
--hard" and get back to where it was.
-ken
When working with ardour projects, I'd like
to backup the project, in
case I'd like to go back a step in the mixing process. There won't be
added new audio files to the projects from now on. Will it make sense to
store old copies of the .ardour files? Are all information regarding
mixer levels, plugins and cuts in the audio files contained in the
.ardour file?
Yes, the .ardour file stores all the information about the session,
and it does make sense to keep older versions, but for easy session
and backup management, it makes sense to take snapshots along the
way and use those if/when you want to go back to an earlier point.
Taking a snapshot creates an .ardour file with the snapshot name
rather than the session name, allowing you to go back to that mix.