Build a DaVinci Resolve sound library you actually reuse

Resolve has a sound library. You can point Fairlight at a folder, index it, and search it from inside the app. On paper that is the whole problem solved, and for a lot of people it works fine for about a year.

Then it stops. Not dramatically: you just notice you have started dragging things in from Finder again, because it was faster than finding them in the library you built. This post is about why that happens and what to do instead.

Why the Media Pool approach falls apart

The Media Pool is project-scoped, and your sound library is not. That single mismatch causes most of the pain.

Import twenty sounds into a project and they belong to that project. Next week, new project, and those twenty sounds are somewhere on a drive with whatever names they had. So you import them again. Multiply by fifty projects and you have fifty copies of the same whoosh, none of which is authoritative, and a Media Pool that is 70 percent sound effects you scroll past to reach your footage.

The Fairlight sound library sidesteps the project scoping, and hits a different wall: it searches metadata and filenames. If your files are named mixkit-fast-whoosh-1489.wav and Transition_04_FINAL.wav, there is nothing there to search. The index is real; the thing being indexed is not.

The problem was never Resolve. It is that a sound library is a thing you keep for a decade, and a video project is a thing you keep for a month. Storing one inside the other never had a chance.

What a library needs to survive

Four properties, and they are all boring:

1. It lives outside any one project. One folder, one source of truth, referenced by every project rather than copied into each.
2. It is searchable by how you think, not how the file is named. You do not remember filenames. You remember “that dry click”.
3. You can hear it before you commit. A waveform you can scrub beats a filename every single time, and it is why Finder auditioning never quite works.
4. Adding to it is nearly free. If filing a new sound takes two minutes, you will not do it while you are mid-edit, and a library you do not add to dies.

A labeling system that holds past 10,000 files

The instinct is to build a taxonomy: categories, subcategories, a folder tree. It feels organized and it fails, because every real sound belongs in three places and you have to decide which one at the moment you are least interested in deciding.

Labels beat folders here, and the rule that makes them work is to label by what it does, not what it is.

• Function first. transition, impact, riser,ui, ambience, foley. This is how you search, because it is how you think when the timeline is open.
• Then character. bright, dark, dry, wet, tight, long. Two or three of these narrow a hundred results to four.
• Then source, only if it matters. own-recording, pack-name, needs-license-check. Mostly useful for rights, not for finding.

Keep the vocabulary small on purpose. Fifteen labels you actually reuse beat sixty precise ones you have to remember. If you find yourself inventing a label for one sound, it does not need one.

Doing it with Sonault

This is our app, so the useful thing to describe is how it maps onto the four properties above rather than to list features.

• Outside the project. Sounds live in a normal folder on your Mac. Not a proprietary database, not a project bin. You can open it in Finder and back it up with Time Machine, and Resolve projects reference sounds rather than owning them.
• Searchable how you think. Labels in your own words, favorites that surface first, and ⌘K from anywhere, including the menu bar while Resolve is in front.
• Audible before you commit. Every card carries a waveform you can scrub, so you audition four candidates in about ten seconds rather than opening files.
• Cheap to add to. Drag a whole folder in and it lands in one pass, originals untouched. Paste a video link and keep the segment you wanted. Drop in your own footage and it keeps only the audio, leaving the video alone.

Getting a sound into Resolve is then just a drag, onto the timeline or into the Media Pool, because it was a real audio file the whole time.

Getting your existing sounds in

If you have been at this a while, your sounds are scattered: a few pack folders, some loose downloads, and a lot of individual files buried inside old project directories. The migration is one evening and it goes in this order.

1. Find them. In Finder, search your drive for wav and mp3, sorted by size. Sound effects are small and cluster together, so this surfaces the pack folders fast.
2. Consolidate into one folder. Wherever you want the library to live permanently. Keep the pack folders intact; you are not reorganizing yet.
3. Import in one pass. Drag the whole thing in. Do not try to label as you go on this first import, there are too many.
4. Label only what you use. This is the part that saves the weekend. Do not label 8,000 sounds. Label them the next time you reach for one. Within a month or two the sounds you actually use are all labeled, and the rest were never going to be searched anyway.
5. Mine your old projects. Room tone, ambience, a door that sounded right. Drop the video files in and keep the audio. It is the cheapest library material you will ever get, and it is already yours.

Keeping it alive

Two habits, and they are the whole maintenance burden.

Never save a sound to Downloads. The moment you decide you want to keep something, it goes in the library with a label. The alternative is not “file it later”, it is “download it again in three weeks”, which is what everyone actually does.

Back the folder up. It is a normal folder, so Time Machine already does this if the drive is included. Check that it is. A sound library is a decade of small decisions and losing it is genuinely painful in a way losing a project file is not.

Do those two things and the library compounds. A year in, the reason you are fast is not that you found a better plugin. It is that you own four hundred sounds you chose, and you can find any of them in four seconds.