Understand projects, tracks, and versions
See how Mixhaus groups your work and which version is current.
How Mixhaus groups your work
| Level | What it is | Where you see it |
|---|---|---|
| Project | A workspace for a client or release, with its tracks and review and delivery workflow. | Projects and the project detail page |
| Track | A reusable audio item in Library. One track can have many versions. | Library and the track workspace |
| Version | One uploaded bounce of a track, with its own version number, name, date, size, audio metadata, and review status. | Version History and Revision timeline |
A project includes tracks. It does not turn each version into a separate track. Keep every bounce for one piece of audio on the same track.
This example shows one project track, its active version, feedback, and the full revision timeline.
What a project shows
On a project's Overview, each track row uses that track's active version. Mixhaus uses the version name when one exists. If it does not, the row falls back to the track display name or filename.
The project row does not list every version. Open the track's Version History for a compact list, or open the track workspace to see the full Revision timeline.
Active and current versions
You may see both Active and Current in Mixhaus. They refer to the same selected version. The track timeline marks it Active. Metadata views may call it Current.
Every track has one active version. A successful manual audio upload makes the new version active automatically. To switch back, open Version History or Revision timeline, select an older version, and choose Make Active or Make active version.
Changing the active version does not delete or rewrite the others. It changes which version appears as current in the project and which version current track actions use.
Review status belongs to a version
Each version has its own revision status:
- Draft means the version has been uploaded but is not in a client review.
- In review means that version was selected and sent for review.
- Needs changes means a reviewer asked for changes to that version.
- Approved means a reviewer approved that version.
The project Review & Delivery view can also show Changes requested or Delivered. Those describe the wider project workflow. They are not extra revision status values on a version.
If version 1 was approved and you upload version 2, version 1 stays Approved and version 2 starts as Draft. Feedback and decisions stay attached to the exact version the client heard. A later upload does not change an earlier review.
Find the full history
Open a track's action menu in a project or Library, then select Version History. In the track workspace, use Revision timeline. Both views put the newest versions first.
Each version can show its name or a fallback such as Version 2, its date, duration, size, BPM, key, and status. Depending on your access, you can play, download, compare, rename, edit tempo and key, open feedback, add stems, or delete a non-active version. Viewers can read the history but cannot upload or change the active version.
Mixhaus will not let you delete the active version. Choose another version as active first if you need to remove it.
Expected result
A project has one row for each track, one active version for each track, and a history of the older versions. The project row tells you what is current. The timeline tells you what changed and keeps the review record with the version it belongs to.
What happens next
When the next bounce is ready, upload it from the existing track's version action. If client review is available on your plan, check the new active version in Review & Delivery and send that exact version.
For a complete first pass through project setup, review, approval, and delivery, follow Run your first project in Mixhaus.
Common problems
The project has a separate row for every bounce
Those files were added as tracks instead of versions. Keep the original track and upload later bounces with Upload New Version or New version. Remove unwanted project items so the project list stays clear.
Active and Current look like different things
They are two labels for the same track pointer. The timeline uses Active. A metadata view can use Current. To change it, choose an older version and select Make active version.
A new draft changed the project status
The new upload becomes active, so the project now follows that version's Draft status. The older approved version still keeps its approval and review record. Send the new version when it is ready, or make the approved version active again.
I cannot delete a version
Mixhaus locks the active version. Make another version active first, then return to Version History and delete the old one if you still need to.