Every song remembers: version history for a studio with an assistant in it
Music apps have never needed version control. One where a cybernetic assistant works beside you does. Here is how every AudioCortex song keeps its own past: checkpoints, moments, an honest history, and an assistant that asks first.
Music software has never really needed version control. You save, maybe Save As “final_v3_REAL”, and move on. Code review, blame, branches, protected history: those are tools for software teams, built for a world where many hands touch the same work and someone has to answer who changed this, and why?
AudioCortex is a new kind of music app. You can do everything in it yourself, but Oscilla, the cybernetic assistant, can also work in your song: lay down lanes, patch cards in Nodes, turn knobs, bounce. An assistant is fast and never tires. It does exactly what it is asked, it forgets what it was doing between sessions, and sometimes it’s wrong. That is precisely the situation version control was invented for.
So we took the ideas from software and gave them to songs.
A song keeps itself
In Tracks, ⋯ ▸ Save as Song… turns a loose set into a song. From then on the song keeps everything inside itself: its bounces as numbered versions in its Renders folder, its Nodes patch, its knobs and Song Map, its moments, and the history of every change. Your own sound files stay exactly where they are.
Checkpoints and Moments
File ▸ Checkpoint… (⌥⌘S) keeps the whole song as it is right now: the project, the Nodes patch, the knobs, the Tracks lanes, the Song Map, even the loop. You don’t have to remember to do it. A checkpoint is also made when you quit with changes, and once a day while you work.
File ▸ Moments… lists them. Play a moment, compare two of them (or a moment and now), and restore. A restore always keeps the song you had first, as a checkpoint of its own, so going back can itself be undone. You don’t have to take the whole moment either: bring back a single lane, playing the audio that moment kept, and leave the rest of today’s work alone.
A history that tells the truth
File ▸ History… shows every change to the song, newest first, and who made it: your edits by hand (what moved, from what to what), the assistant’s actions, presses from the phone. Filter by author to see only what Oscilla did this afternoon, or only what you did.
The credit is honest. Every change is written to the song’s journal before it is made. If someone edits the song’s files outside the app, that is recorded as an outside edit when the song next opens. A long bounce records only its own render, so an edit you make while it runs is never lost. A change nobody claims is marked unknown and protected, just like yours.
Your assistant asks first
Tick Agent patches wait for my OK in the History window, and a new patch from your assistant no longer replaces yours. It waits under Proposals, where you can audition it, accept it or reject it. Think of it as a pull request for your sound.
Why this matters
When an assistant works in your music, trust doesn’t come from the assistant being perfect. It comes from always being able to see what happened, who did it, and how to get back. Every song in AudioCortex can answer those three questions.
Checkpoints, Moments, History and Save as Song are in the beta now. Download it and press ⌥⌘S.