Version history for music projects. Save an arrangement, compare what changed, and recover an earlier version without overwriting your current work.
why I built it
I produce music, and wanted a straightforward way to revisit earlier ideas in a project. Trackline grew out of that need: keeping a history of the work without manually duplicating the entire project folder each time.
Versions have names and notes, making it easier to find a particular arrangement or experiment. Comparisons show which files changed; for Waveform sessions, they also show details such as tempo and time signature. Restore as Copy rebuilds an earlier version in a separate folder, leaving the current project untouched.
I developed the project with substantial AI assistance, directing the product and testing it with real Waveform sessions. A shared Rust engine handles storage and recovery for both the Tauri desktop application and the command-line tool.
storing unchanged audio once
Different arrangements often use the same audio files. Trackline identifies file contents with BLAKE3 hashes and stores identical contents once. Each version records which files it contains and references those stored objects.
Benchmarks revealed that unchanged files were still being written to temporary storage before their existing objects were found. The revised implementation hashes the source and verifies the stored object first, skipping those writes when both match.
In recorded September benchmarks, median time to save an unchanged version fell from 575 ms to 47 ms. The test used a 109-file, 24.45 MiB synthetic project on an M4 MacBook Air's internal SSD; it does not establish performance on large production sessions.
Deduplication works at file level: changing part of a large audio file still requires storing a new copy of the whole file.
recovering a complete project
A restore should produce a complete, verified project. Trackline checks the selected version and its stored files, rebuilds them in a temporary folder, and hashes the reconstructed files before moving the completed folder into place.
Verifying the output catches a file that changes after the initial check. Tests exercise this case, along with missing files, corruption and cancellation, to check that failed operations do not leave a partial project at the destination.
Storage cleanup also needs complete information. If a damaged version record makes it unclear which objects are still needed, Trackline stops cleanup rather than risk deleting shared content. Healthy versions remain accessible.
testing recovery
Rust tests check storage reuse, invalid paths, concurrent operations and recovery failures. Frontend tests cover command submission, history navigation and audio comparison controls.
For a manual check, I saved a Waveform project, changed it, then saved a second version. I restored the first version to a separate folder and successfully reopened it in Waveform.
where it stands
Trackline runs locally on macOS, with musical comparisons currently focused on Waveform. The next step is testing larger projects and external-drive recovery with other producers before public distribution.
Version history is stored beside the project. It protects access to earlier work, but losing the drive would lose that history too. Portable export lets it be copied to a separate location.