Managing Track Versions

Version control is essential for audio production workflows. Whether you’re iterating on a mix, receiving client feedback, or archiving milestones, Feedtracks’ version management system helps you track every evolution of your tracks.

What Are Track Versions?

In Feedtracks, track versions allow you to maintain multiple iterations of the same audio file while keeping them logically grouped together. This is different from uploading separate files—versions are explicitly linked and managed as a stack.

How Versions Work

When you upload a new version of a track:

• The track becomes part of a version stack
• Each version receives a version number (1, 2, 3, etc.)
• One version is marked as the current/latest version (position 0)
• All versions are stored as separate files
• Previous versions remain accessible at all times

Storage Considerations

Important: Each version is stored as a complete, separate file. If you have three versions of a 50MB track, you’re using 150MB of storage space. All versions count toward your storage quota.

Creating Your First Version

Initial Upload Creates Version 1

When you first upload a track, Feedtracks automatically:

1. Creates a new version stack for that track
2. Assigns it as Version 1
3. Sets it as the current version (position 0)
4. Generates a unique stack_id to group future versions

At this point, you have a single track with one version. The version stack is ready to accept new versions.

Uploading New Versions

From the Track Menu

1. Navigate to the track you want to version
2. Right-click on the track or click the More Actions menu (three dots)
3. Select Upload New Version
4. Choose the new audio file from your computer
5. The file is uploaded and added as the next version number

The newly uploaded version automatically becomes the current version (position 0), and the previous current version moves to position 1.

From Inside the Track View

1. Open the track by clicking on it
2. Look for the Versions section in the sidebar
3. Click Upload New Version
4. Select your file
5. The new version is added and set as current

Version Numbering

Versions are numbered sequentially:

• First upload: Version 1
• Second upload: Version 2
• Third upload: Version 3
• And so on…

Version numbers are never reused. If you delete Version 2, the next upload will still be Version 4 (not Version 2 again). This ensures version history is unambiguous.

Understanding Position vs. Version Number

Feedtracks uses two related but distinct concepts:

Version Number

• Incremental number assigned when the version is created
• Never changes after assignment
• Reflects chronological upload order
• Example: Version 1, Version 2, Version 3

Position

• Position 0 = Current/Latest version
• Position 1 = Previous version
• Position 2 = Version before that
• And so on…

When you upload a new version:

• The new version gets the next version number (e.g., Version 4)
• The new version is placed at position 0 (current)
• All other versions shift down (position 0 → 1, position 1 → 2, etc.)

Example Evolution

Initial upload:
- Version 1 (position 0) ← Current

After uploading Version 2:
- Version 2 (position 0) ← Current
- Version 1 (position 1)

After uploading Version 3:
- Version 3 (position 0) ← Current
- Version 2 (position 1)
- Version 1 (position 2)

Viewing Version History

Version List

Open any track with multiple versions to see the complete version history:

1. Click on the track to open the track view
2. Look for the Versions panel on the right side
3. You’ll see a list showing:
   • Version number
   • Upload date and time
   • File size
   • Uploader name
   • Current version indicator

Switching Between Versions

To listen to or work with a previous version:

1. In the version history panel, click on any version
2. The waveform and player update to show that version
3. You can play, download, or comment on the selected version

The version you’re viewing is highlighted in the version list.

Comparing Versions

One of Feedtracks’ most powerful features is the ability to compare multiple versions side-by-side with synchronized playback.

Opening Compare View

1. Open a track with multiple versions
2. Click the Compare Versions button
3. Select which versions you want to compare (you can select 2 or more)
4. Click Open Comparison

Using Compare View

In compare view, you’ll see:

• Multiple waveforms stacked vertically
• Synchronized playback: All selected versions play together in perfect sync
• Individual volume controls for each version
• Solo/mute buttons for each version
• A single playhead that moves across all waveforms

Compare View Use Cases

A/B Testing Mixes: Compare different mix approaches to hear subtle differences:

• Master bus compression on vs. off
• Different reverb settings
• EQ adjustments

Client Feedback Iterations: Play Version 1 (original) alongside Version 4 (after feedback) to demonstrate improvements.

Stem Comparison: If you’ve uploaded different versions of stems, compare them to ensure consistency.

Before/After Mastering: Compare the pre-master and mastered versions to hear the impact of mastering.

Setting a Version as Current

By default, the most recently uploaded version is the current version. However, you can manually change which version is current.

Why Change the Current Version?

• You uploaded a new version but prefer an earlier mix
• A client requests you roll back to a previous version
• You want to mark a specific version as the “approved” version

How to Set Current Version

1. Open the track
2. In the version history panel, find the version you want to set as current
3. Click the Set as Current button next to that version
4. The version moves to position 0, and all other positions adjust accordingly

The current version is what people see when they:

• Open the track from the drive view
• Access a public share link
• Add the track to a playlist

Moving Tracks with Versions

When you move a track between folders:

• All versions move together as a single unit
• The entire version stack is preserved
• Version numbers and positions remain unchanged
• Storage calculations update for both source and destination folders

You cannot separate versions by moving only some versions to a different folder. Versions are permanently linked through their stack_id.

Deleting Versions

Deleting a Single Version

1. Open the track
2. In the version history panel, find the version you want to delete
3. Click the Delete Version button (trash icon)
4. Confirm the deletion

Important: Deleting a version:

• Permanently removes that version file from storage
• Frees up the storage space used by that version
• Cannot be undone (the file is not moved to trash)
• Does not affect other versions in the stack

Deleting the Current Version

If you delete the version at position 0 (current):

• The version at position 1 automatically becomes the new current version (moves to position 0)
• All other positions shift up

Deleting All Versions (Deleting the Track)

If you want to delete the entire track and all its versions:

1. Navigate to the track in the drive view
2. Right-click and select Move to Trash
3. The entire version stack is moved to trash
4. All versions are preserved during the 30-day trash retention period
5. Restoring from trash restores all versions

See Managing Trash for more information.

Version Storage and Quotas

How Version Storage Works

Each version file is stored separately in your S3 bucket:

• Version 1: track-123-v1.wav (50MB)
• Version 2: track-123-v2.wav (52MB)
• Version 3: track-123-v3.wav (48MB)

Total storage used: 150MB

All three versions count toward your storage quota.

Optimizing Version Storage

If you’re running low on storage:

1. Delete old versions you no longer need

   • Keep only the current version and 1-2 important milestones
   • Delete intermediate iterations

2. Archive old versions externally

   • Download old versions to your local backup
   • Delete them from Feedtracks to free space
   • Re-upload if needed in the future

3. Upgrade your plan

   • Fan: 10GB
   • Pro: 100GB
   • Studio: 1TB
   • See Upgrading Your Plan

Best Practices

1. Use Meaningful Version Comments

When uploading a new version, add a comment explaining what changed:

• “Reduced vocal reverb per client feedback”
• “Mastered version with LUFS -14”
• “Fixed timing issue in bridge section”

This creates a clear audit trail of your decision-making process.

2. Don’t Over-Version

Not every tiny tweak needs to be a new version. Consider versioning when:

• ✅ You’re about to share with a client
• ✅ You’ve completed a significant milestone (rough mix, final mix, master)
• ✅ You’re making major creative decisions
• ❌ You adjusted one knob slightly
• ❌ You’re just saving your work in progress

For quick saves, use your DAW’s save feature instead.

3. Mark Key Milestones as Current

When a version is approved or reaches a milestone:

• Set it as the current version
• Add a comment like “APPROVED BY CLIENT” or “FINAL MIX”
• Continue working on new versions without changing the current version

This preserves the approved state while allowing continued iteration.

4. Compare Before Replacing

Before uploading a new version:

• Save the current version number in your notes
• After uploading, use compare view to verify the new version is actually better
• If you prefer the old version, set it back as current

5. Clean Up Regularly

Every few weeks:

• Review your version stacks
• Delete versions you definitely won’t need again
• Archive important versions locally
• Free up storage space proactively

6. Version Naming in Your DAW

Before exporting from your DAW:

• Name your exports consistently (e.g., “Track-Name-v2-mastered.wav”)
• This helps you remember which DAW session corresponds to which Feedtracks version
• Consider including dates: “Track-Name-2024-03-15-v3.wav”

Troubleshooting

I can’t upload a new version

Possible causes:

• You’ve reached your storage quota
• You don’t have edit permissions for this track
• The file format is not supported

Solution:

• Check your storage usage in Settings
• Verify you have edit or admin permissions
• Ensure the file is a supported audio format (WAV, MP3, FLAC, etc.)

My versions are out of order

Possible causes:

• You’re looking at version numbers (chronological) instead of positions (current first)
• Someone manually changed the current version

Solution:

• The version at position 0 is always the current version
• Version numbers show upload order, not importance
• Check the version history for any “set as current” activities

Compare view isn’t syncing properly

Possible causes:

• Versions have different sample rates or lengths
• Browser performance issues with large files
• Network latency loading audio data

Solution:

• Ensure all versions are properly aligned (same start point)
• Try comparing fewer versions at once
• Use a more powerful computer for large files
• Check your internet connection speed

I deleted a version by mistake

Unfortunately: Individual version deletions are permanent and cannot be recovered.

Prevention:

• Always confirm you’re deleting the correct version
• Download important versions locally before deleting
• If you delete the wrong version, check if you still have the file on your computer to re-upload

Storage shows more usage than my current versions

Possible causes:

• You have items in trash (they still count toward storage for 30 days)
• Multiple version stacks across many tracks
• Blockchain certifications and artwork also use small amounts of storage

Solution:

• Empty trash to permanently free space
• Review and delete unnecessary versions
• Check Settings → Storage for a detailed breakdown

Related Articles

• Moving Tracks Between Folders
• Making and Managing Playlists
• Managing Trash and Recovery
• Upgrading Your Plan
• Blockchain Certification