Track versions of songs — how to keep revisions, edits, and variants organised

Two different things that people call "versions"

The confusion in most music version management comes from conflating two distinct concepts that need separate systems.

Production revisions are iterations of the same mix. You bounce a mix, your mixing engineer adjusts the low end and bounces again. That is revision 1 and revision 2 of the same track. The content is the same — same arrangement, same recording — but the processing is different. You might go through six or eight revisions before the final is approved. All of them should be retained because it is not always obvious which one is the right one until you compare.

Track variants are distinct functional versions of the same song. The instrumental exists because radio programmes need a version without vocals. The radio edit exists because streaming editorial playlists prefer a 3:30 runtime over a 7-minute extended. The club mix exists because the DJ version is structured differently for floor play. These are not iterations of the same thing — they are different products with different purposes.

Treating these the same creates the mess. Labelling them separately — and storing them in a system that understands the distinction — keeps it clean.

Why filenames are not a version control system

The standard approach to music version management is the filename. track_v2_final.wav. track_v3_MASTERED.wav. track_v3_MASTERED_2.wav. track_FINAL_use_this.wav.

This works for a single track in a single session. It breaks when:

You have multiple tracks. The FINAL convention applied across twenty tracks in an EP produces twenty files all called FINAL that are not all the same final.

You work with collaborators. They rename files according to their own convention. track_mix_v2_DT_edits.wav arrives and you do not know whether DT's edits are incorporated into your v3_final or not.

You come back to a project months later. The filename record has no timestamps, no notes, no indication of what changed between versions.

You need to find the approved version for a sync placement. The production folder has twelve files with variations of the same name and no obvious way to determine which was the approved master.

How TYFRA Vault handles version tracking

Vault uses two separate systems that correspond to the two distinct version concepts above.

Version labelling for specific delivery contexts

Different delivery contexts require specific version formats, and knowing which version to deliver for which context prevents expensive mistakes.

Radio and editorial playlists. Most radio stations and Spotify editorial playlists prefer tracks between 3:00 and 3:45. An extended mix that works for a club set is not the right version to pitch for editorial placement. Always have a radio edit.

DJ promotion. DJs typically want the full club mix or extended — they will create their own edit if needed. Sending a radio edit to a DJ campaign is a mismatch. Promo integration lets you select the specific version for each campaign without re-uploading.

Sync placements. Music supervisors typically need a 30-second edit for advertising, the full track for film and TV, and an instrumental for scenes where dialogue runs over music. Having these ready — clearly labelled and immediately shareable — removes friction from the placement process. Missing a sync deadline because you needed to create a version that should have existed already is avoidable.

Distribution. Distributors typically require separate uploads for each version (instrumental, explicit, clean). Vault's Products structure holds all versions together under one release container, ready for distributor export.

The metadata connection

Version tracking is only half of the version management problem. The other half is metadata — making sure the right information is attached to each version.

An instrumental needs a different ISRC than the vocal version. A remix has different production credits. A radio edit might have different P-line information if it was edited by a different engineer. Vault stores metadata per track and per version, so the instrumental version has its own ISRC and credits, separate from the main version's metadata.

Audio analysis (BPM and key detection) runs per version — useful for the club mix and radio edit separately, since editing for length sometimes affects the BPM displayed at the track level. All metadata entered in Vault travels with the file when it is used in Promo, exported for distribution, or referenced in Contracts.

Keeping the catalog clean over time

Version management is not just a production-time concern. As a catalog grows — EPs, albums, remixes, features, collaborations — the number of versions across the full catalog becomes significant. A catalog of twenty releases each with three or four versions is sixty or eighty files. Without a systematic approach, the catalog becomes difficult to navigate and impossible to audit.

Vault's smart tagging and folder structure make the catalog searchable by version type, genre, BPM range, or any metadata field — the same principles as organising music files at scale. The version history is permanent — even tracks from years ago have their full revision and variant record intact. When a sync opportunity comes in for a track from two years ago and the supervisor needs an instrumental, it is there.

Related on TYFRA