Versions

Audyn tracks every .als file in a project folder as a version. No manual setup is needed.

How versions are detected

Every .als file inside a project folder is a version. Audyn finds them during scanning and sorts them by modification date. The oldest file becomes version 1, and so on. The most recently modified file is the "current" version.

My Track/ ├── My Track.als ← v1 (earliest) ├── My Track v2.als ← v2 ├── My Track drums.als ← v3 └── My Track final.als ← v4 (current)

Version numbers follow the chronological order of file modifications, not file names. The file name is displayed as the version label. You can reorder versions manually if needed.

Version timeline

The Versions tab shows all versions in chronological order. Each entry displays the file name, date, file size, and key metadata. Changes from the previous version are highlighted, so you can see at a glance when the BPM changed, tracks were added, or plugins were swapped.

Each version's metadata is stored independently. This means you can compare the exact state of your project at any point in its history.

Current version

The current (or "head") version is the one whose metadata appears in the main project list. This is typically the most recently saved .als file. You can manually designate a different file as the current version if needed.

This is useful when you've saved an experimental version after your main working file and want the project list to reflect the main version's metadata.

Example

You're working on a track called "Sunset". Over three studio sessions, you save different iterations:

Sunset/ ├── Sunset.als ← Session 1: 120 BPM, Dm, 8 tracks ├── Sunset v2.als ← Session 2: 124 BPM, Dm, 12 tracks └── Sunset final mix.als ← Session 3: 124 BPM, Dm, 14 tracks

Audyn creates one project called "Sunset" with 3 versions. The timeline shows the BPM changed from 120 to 124 between sessions 1 and 2, and the track count grew from 8 to 14 over time. The current version is "Sunset final mix.als".

Snapshots

A snapshot is a saved copy of a version that you create on purpose. Use them to mark a milestone before a major change, to preserve a client-approved state, or to have a safety net before destructive edits.

Unlike automatic version tracking (which follows every .als file), snapshots are intentional. Common labels include "pre-mix", "client approved v2", or "before stems export".

Snapshot creation is a Pro feature.

Comparing two versions

Select any two versions and compare them side by side. Audyn shows exactly what changed between them:

  • Tracks added, removed, or renamed
  • Plugins and effects added or removed
  • BPM, key, or time signature changes
  • Clips added, removed, or repositioned
  • Sample references changed
Version comparison is a Pro feature.

Version tags and notes

Each version can be labeled with a color-coded tag (e.g., "milestone", "draft", "approved") and annotated with notes. Notes save automatically as you type. Both tags and notes are searchable.