Two hundred and forty-seven projects, three released. That is the folder the founder of this company was looking at the year he stopped blaming himself for it and started counting where, exactly, the other two hundred and forty-four had stopped. Not why. Where. Because “I lack discipline” is a diagnosis you cannot do anything with, and “the track dies the second time I open it” is one you can.
Once you count, the pattern is embarrassing in its simplicity. A track does not fade out over months. It dies at one of five specific points, always the same five, and the death takes about four seconds each time. This article is about those five points and the free software that keeps each one from closing. None of it makes the music better. All of it makes the music more likely to exist.
The first place: the second open
The first session on a new track is the easiest hour in music. You have a loop, the loop is good, and the whole thing rides on momentum. The second session, three days later, is where most tracks die, and they die in the first four seconds after the project loads.
The session opens. Forty channels, twelve of them muted, three named Audio 7. You do not remember what the bounce in your downloads folder was for. You do not remember whether the bridge was a plan or an accident. You have no idea what this track still needs, so you listen through it once, feel vaguely that it is not as good as you remembered, and open a new project instead, because the new project has no history and history is the thing that hurts.
This is not a motivation problem. It is a re-entry problem, and re-entry is a tooling problem, which is the good news.
The free tool is Vantom, and it is ours, so hold that against it as you see fit. It sits beside the DAW, reads every project file in place, and opens on the track you last touched: the tempo, the key, the notes you wrote for yourself at the end of the last session and the tasks you left open. The four seconds where the track dies become four seconds where you read “chorus needs the vocal chop, bass is too loud at 1:20” and get to work. It also keeps a history of every saved version, with the plugins each one loaded, so the question of what changed between Tuesday and today has an answer that is not your memory.
The habit that makes it work costs nothing and needs no app: before you close a session, write the next action. Not “worked on drop.” That is a diary entry and it helps nobody. “Drop needs a riser, try the white noise one.” The tool holds the note. The habit is yours. The notes article goes deeper into why the second version is the only one that survives a week.
The second place: the reference you never set
The second death is quieter. You have been on the track for a week. It sounds good. It sounds, in fact, a little too good, in the way a mix does when you have gone deaf to it, and one night you play it after a record you love and the bottom falls out. It is thin, or muddy, or somehow both, and you cannot hear why, so you open the EQ and make it worse for two hours.
The professionals never got here because they set a reference before the first session was over. A finished track in the same genre, on a muted channel, level-matched, so that at any moment a single solo button puts the two side by side. That is the entire technique, and it is free. What is also free is the pair of tools that make it work when your ears will not.
SPAN from Voxengo is the spectrum analyser you see in every mixing video. Put it on the master, put it on the reference channel, and the two curves will show you the low end you cannot hear on headphones and the three kilohertz you have stopped noticing. Youlean Loudness Meter gives you the other half: the integrated loudness of your track against the reference, so you stop comparing a quiet mix to a loud master and calling the difference “energy.”
Neither of them will tell you what to do. They will tell you what is true, which at 2am is the rarer thing. The wider list of free production software has the rest of the stack, if you are building one.
The third place: the deadline that was never set
The third death is the slowest. The track is essentially done. It has been essentially done for six weeks. Every session opens it, nudges a hi-hat, and closes it, because there is no moment at which it is required to be finished and so it never is.
This one is almost entirely about a decision, not a tool. The decision is to set a deadline for the bounce, not for the track. The track is never finished. The bounce is a file with a date on it, and a file with a date on it is a thing you can be late for.
Two free tools help at the edges. The first is any timer, and Vantom ships one that is built for this room: an ear fatigue timer that reminds you to stop before your judgement goes, because the hi-hat nudging happens after the second hour, never in the first. The second is the bounce itself, made at the end of every session whether the track deserves it or not. Vantom matches every bounce back to the session it came from and lines them up in the project, so six weeks of “essentially done” becomes six files you can play in a row. Playing them in a row is how you discover that version three was the one, and that everything since has been nudging.
The fourth place: the version nobody can find
The fourth death is the one with a filename. track_final.wav. track_final_v2.wav. track_FINAL_real.wav. track_FINAL_real_USE_THIS.wav. You made all of them, you know which one is the good one, and you knew that for about a day. Now there is a message from someone who wants to put it on a playlist and you are listening to four files at a quarter to midnight trying to hear the difference.
The free tool here is half a habit and half software. The habit is a naming scheme, and the article on keeping track of song versions lays one out that survives contact with a real month. The software is a history nobody had to write: every saved version of the project logged with a timestamp and the plugins it carried, every export matched back to the session it came from. That is what Vantom’s Auto-Changelog and Latest Exports do, for free, across every project on the drive, and the reason it matters is not tidiness. It is that on the night the playlist message arrives, the answer to “which one” takes five seconds instead of forty minutes, and forty minutes at a quarter to midnight is exactly the length of time it takes to decide the track is not good enough after all.
The fifth place: the wall before release
The last death is the one nobody warns you about, because by the time you reach it you are supposed to be done. The track is mixed. It is bounced. It is, by any reasonable standard, finished. And then it sits for four months, because releasing a track is a completely different job from making one, with different tools, different deadlines and a different kind of fear.
Artwork. A release date. The distributor’s checklist, with the ISRC codes and the metadata fields and the file format they want. The SoundCloud upload with the tags and the description. Each of those is small. Together they are a wall, and the wall is where the two hundred and forty-four went to wait.
The honest answer here is that the free tools thin out. SoundCloud itself is free to upload to, and Vantom publishes to it directly from the project, cover, tags and privacy included, which removes one trip through a browser. Beyond that, the release side is where this product stops being free, and it says so.
If you do not want the paid tool, the free version of the fifth step is a checklist in a text file and a calendar entry with the release date in it. That is genuinely enough. The wall is not the work. The wall is not knowing the work, and a list on a page is most of the way to knowing it.
What the five have in common
None of these tools make a better track. That was never the problem. The founder’s two hundred and forty-four unfinished projects were not bad; some of them were the best things he had made. They were unfinished because at one of five points a small, specific thing was missing, and in the four seconds it took to notice, a new project was easier than the old one.
Free software cannot give you the discipline everyone keeps telling you to find. It can make the discipline unnecessary at the five places where it was doing all the work, and that turns out to be most of what finishing is.
Start with the first one. Open the oldest project you still believe in, and before you touch a fader, write down what it needs.