The short answer
Notion, and Airtable alongside it, are general databases that a lot of writers and producers bend into a music catalogue, usually with real ingenuity. It works, up to a point. The limitation is structural rather than a missing feature: Notion holds information about your songs while the songs themselves live somewhere else, so you are maintaining a second index by hand and keeping it in step with a hard drive that keeps changing. Locker holds the audio and the information as one thing, and fills in tempo, key, versions and credits from the files themselves. If you enjoy building your own system and your catalogue is stable, Notion is a legitimate answer. If you are spending Sunday updating rows, that is the drift showing.
Locker compared to Notion
| Locker | Notion | |
|---|---|---|
| Holds the actual audio | The catalogue and the files are one thing | Links out to wherever the audio really lives |
| Filling in the details | Tempo, key, genre and mood read from the audio | Every field typed in by you |
| Versions of a song | Versions and stems grouped under one title | A row per file, or a relation you maintain |
| Staying in sync | Nothing to reconcile, there is one copy | The database drifts from the drive as work continues |
| Playing music back | A real player with waveform and version switching | An embed, if the file is somewhere embeddable |
| Sending music out | A branded player with versions, lyrics and credits | A shared page, and a separate link to the audio |
| Setup cost | Drop a folder in and it sorts itself | You design and maintain the system as well as use it |
Holds the actual audio
Filling in the details
Versions of a song
Staying in sync
Playing music back
Sending music out
Setup cost
The second index problem
Any catalogue built in a general database is a description of your music kept separately from the music. That is fine on the day you build it, when the two agree perfectly. The gap opens quietly: you bounce a new mix at midnight and do not add the row, you rename a folder, you move a drive. Six months later the database and the drive disagree and there is no way to tell which is right. This is what usually kills these systems, and it is not a discipline failure, it is what two copies of the truth always do.
Typing in what the audio already knows
In a Notion catalogue, every tempo, key, duration and genre is a field somebody typed. The audio file already contains all of it. Locker reads it directly, per version, so the metadata arrives without anyone deciding to enter it. That difference compounds: the catalogue that fills itself in stays complete, and the one that depends on a habit ends up half empty.
What a database cannot do with a song
A row can record that a song is 120 beats per minute in F minor. It cannot let you hear it, compare two mixes back to back, scrub a waveform to the second chorus, or send it to an A and R as something that plays. Those are the things you actually do with music all day, and they are the reason a music tool exists rather than a spreadsheet.
When Notion is the right answer
Notion is better than Locker at being flexible, and that is a genuine advantage rather than a technicality. If your process is unusual, if you need fields nobody else would want, or if the catalogue is one part of a bigger workspace that also holds your release plans, tour notes and label admin, Notion will bend to fit in a way a dedicated tool will not. It is also excellent for the writing around the music: session notes, project briefs, plans. Plenty of people run Locker for the catalogue and keep Notion for everything wrapped around it, which is a sensible split rather than a compromise.
Common questions
Can I import my Notion catalogue into Locker?
The audio is the part that matters, and you bring that in by dropping the folders it lives in. Locker sorts them into songs, versions and stems and reads tempo, key and the rest from the files, so most of what you were maintaining by hand rebuilds itself. Anything genuinely bespoke to your process can go in notes and tags.
Is Airtable any different from Notion for this?
Not in the way that counts. Airtable is the stronger database of the two and its views are better suited to a catalogue, but it has the same structural issue: it holds information about music that lives somewhere else, so you are still maintaining a second index and keeping it in step by hand.
Should I keep using Notion at all?
Very possibly. Notion is genuinely good for the work around the music, meaning session notes, release plans, briefs and admin. The case for moving is specifically about the catalogue: the list of what you have made, which versions exist, and who did what.