I would suggest naming them after the object that is the sound source for the recording. In the metadata you can then get descriptive and just add anything that would help you find them later into the keywords but as the main name I'd stick with source and other relevant details (e.g. induction_harddrive_writing_... or shorter ind_hd_writing ...).


What André said. Then try describing what you HEAR. Buzz, hiss, whirr, growl, whine. You're basically putting keywords into the filename - good practice in my opinion. If I was a sound editor/designer looking for buzzy, whiny electronic sounds, I would search my database for some of those adjectives first, unless i knew I had just the right recording of a ...


I think for sound design elements (very basic things like a low thud, tool clutter, cork pop) it is good to give files a rudimentary searchable name. For finished sound effects with many elements you might want to add terms to the name or give it tags. Personally I would love to be independent of metadata. My library is still a work in progress. The most ...

Only top voted, non community-wiki answers of a minimum length are eligible