Session Versioning
Saving recoverable snapshots with clear names, so a good take survives the next round of edits and every change can be explained.
Related
Versioning is not renaming a file. It is making every important change recoverable, and being able to say what changed.
The problem
You want yesterday's mix back, but the save has already overwritten it. Final, final two, final two revised, and soon nobody knows which file is deliverable.
How it works
A version is a project snapshot; it holds the project file, its media and the plug-in state. The practice is simple. Save a new file at each key point, name it with a date, a number and one line about the change, and append rather than overwrite. Experimental work can branch, then merge back when confirmed.
Settings and judgement
Save one deliverable version each day, and one before each important recording or mix. Three to five recent versions are enough; archive older ones to cold storage. Note whether tempo, sounds or structure changed.
What to listen for
Compare two performances of the same work and hear differences in tempo, dynamics and reverb. A version is not just a filename; it records the choices of that moment.
Common misunderstandings
Versioning is not cloud backup. Backup prevents loss, versions prevent damage. More files are not safer either; unnamed copies only add confusion.
Listen in the library
All tracks from midicn-lib — inline badge is the license tier (C1 commercial / C2 non-commercial / C3 study only).
Sources
- 工程快照、分支与命名规则，依软件工程版本管理通识与 DAW 文档核查，未抄文本
- 交付版本的响度与文件归档做法，依母带与交付规范通识核查，未抄文本
Used for fact-checking only; all prose is original.