Data about data, that’s got to be pretty interesting right? Well, it turns out to be more interesting than you might think. But first lets get the definition under control: Metadata is data about other data – that’s where its value lies, but the metadata is only of value if you have a use for it, and the same could be said of the data itself.
More than likely like me you are constantly generating new material – be it photos, sounds, video, music, text or whatever. All that data is getting stored and, in the present tense, we know what that data is and its relative importance. But time passes, memories blurr and data soon becomes lost in the archive constantly growing in parallel to your life. And thats where metadata can help!
Chances are you’re already generating metadata, either automatically or manually. Every time you take a photo or record a sound, the device you use is generating metadata for you eg metadata fields such as creation date and the device name & model are embedded in every photo or sound. But if you’ve ever uploaded a video to youtube or vimeo, or uploaded photos on flickr you might also notice you are obliged to enter descriptive tags to specify the genre, style or topic. This also is metadata…
Not coincidentally I have recently read an interesting book by Gene Smith called Tagging: People Powered Metadata and the Social Web and it outlines three main motives for tagging:
1. helps you (or others) find your data
2. helps you manage your data
3. lets you relate your data to other data
While most people probably don’t worry too much about ever setting it up, metadata is crucial in the process of film making. For example the location sound recordist must be very, very sure his file naming & metadata are correct because his media is inherited by a lot of people & is accessed repeatedly for many months, long after he is off the payroll & has archived his work.
For sound effects editors and sound designers, one of the most important assets you own is your own personal sound library and it is this application of metadata I’m going to discuss, as it represents a means of including far more descriptive information than is possible with just the filename, and it can have a major impact on the accessibility & useability of your library. But it is not as straight forward as perhaps it should be, since as with many technical developments we meet the clash of open source versus proprietry systems.
The first issue is what applications support metadata? With ProTools you can display and edit metadata in the workspace browser. Open it via Window menu > Browsers > Workspace and open one of your drives with sound files on it & see what metadata already exists in your files. You can see from this example that it easily gives you the ability to tag the file with more descriptive terms than is used in the file name, so eg as below if I searched for ‘chomp’ in filename alone I would get zero results, whereas searching filename & metadata would find the file….
Now this is an example of metadata stored within the source file itself & it is not the only way; the other option is to store metadata in a seperate database, and some apps give you the choice of both scenarios eg the sound library application SoundMiner allows you to tag additional descriptive terms to any file & by default these added terms are stored in SoundMiners own database file. But the danger here is what happens if that database file is lost or becomes corrupt?
Once you have spent the time entering metadata, it is so important that there is no way you ever want to risk losing it, so apart from regularly backing up your SoundMiner databases I also believe you should export your metadata into the source files themselves.
If you have ever used a nice, user friendly database app like FileMaker Pro you will know that you can keep adding fields to the database to your hearts content, but does the same apply to metadata? Well… yes and no… And here’s where we need to do some research into the actual format of metadata and how it is embedded into your soundfiles.
In terms of digital audio files, first there was the .WAV audio format which stores audio data in a straightforward linear fashion. But as software and hardware has evolved we’ve seen the evolution to the BWF (Broadcast Wave Format). Whats the difference? Basically a BWF file is a .WAV audio file that also contains an extra data “chunk” to carry information about the content, you guessed it metadata. Now the great thing with this extra chunk of data is that if your software or hardware device has no use for the metadata then it ignores it and treats it like a normal .WAV file.
So what sort of data can we add? And more importantly, is it standardised?
As I mentioned earlier, from a sound point of view the idea of metadata that is entered during a film shoot is very important and accordingly a lot of work has been done to establish a standard for this use, and this form of audio metadata has been given the name: iXML
So for example a production recordist on a film shoot enters the slate & take number every time he rolls sound, and that information is embedded into the .WAV files, which are delivered to picture editorial who load it into their AVID or whatever. Months later a dialogue editor inherits the work of the picture editor (as well as all of the material recorded) and in ProTools he can verify from metadata the slate and take of any piece of audio because of iXML.
As you can imagine it has been a herculean task to get all of the manufacturers of sound recording hardware (along with the DAW developers) to agree to a standard, but it has been achieved! For more info on the iXML spec check wikipedia and the official support site.
So for the workflow of [shoot -> picture editorial -> sound editorial] metadata works, with the caveat that nothing is presumed and camera/workflow tests are ALWAYS done before the shoot to verify this fact. So now lets presume you are doing something similar to me ie recording wild ambiences & FX, editing & mastering them and then adding them to your sound library. What’s the best way to integrate metadata in that scenario?
About now is the point where use of the word standards starts to get a little shakey. It seems anyone can create an app that adds metadata to a .WAV file, the issue then becomes who can read it? Now I’ve used ProTools as my primary sound editing DAW for the last 18 years so whatever metadata I embed I want it to be readable by ProTools. But over the years I’ve tried & used many different solutions for managing my sound library and at the moment SoundMiner is my app of choice. Now I’m pretty sure I’ll still be using ProTools 5 years from now, but SoundMiner? I’m not so sure… It does a great job but I have also investigated a number of other options and I’m not 100% convinced that give or take a year or two of development I may well end up switching to a different sound library app. With this knowledge the idea of proprietry metadata becomes a significant issue: why invest time & energy adding metadata that can’t be read by other apps, should I eventually migrate?
So what metadata do I add via SoundMiner?
When I started HISSandaROAR, after doing tests with the main Mac contenders (SoundMiner, Basehead, AudioFinder, Snapper) I discovered the only metadata that worked with all of them was the DESCRIPTION field, and the easiest way to enter that data was via the ProTools Workplace as described above. But after a few emails from people asking for more metadata I revisited the released libraries and created a spreadsheet for each library with all the fields I thought were relevant, and have published them here for people to download and embed in their chosen sound library app. So the metadata fields I have provided are listed below (along with one files metadata as an example)
LIBRARY: VEGE VIOLENCE
FILENAME: VEGE CABBAGE bat hit MAX.wav
DESCRIPTION: Vegetable Violence Cabbage bat hit smack impact
BIT RATE: 24
SAMPLE RATE: 96
DESIGNER: TIM PREBBLE
MICROPHONE: Sanken CSS5
RECORDER: Sound Devices 722
LOCATION: SUBSTATION, Wellington, New Zealand
GPS LATITUDE: 41°18’29.11″”S”
GPS LONGITUDE: 174°49’22.40″”E
GPS POSITION: 41°18’29.11″”S, 174°49’22.40″”E”
Now some of these fields I know are particular to SoundMiner eg the ability to tag the Designers name, and embed an image. So if you own SoundMiner and embed all of this metadata, and then are working from your laptop using AudioFinder, that Designer and Image metadata will not be available to you. And there lies the quandry of the world we live: commercial imperatives vs practical long term use.
Its worth having a read of a white paper that the SoundMIner developers published in the name of establishing and encouraging sound library developers to include their implementation of metadata. In an effort to be fair and balanced I shall send a link to the developers of each of the sound library application creators and ask for their comments about metadata support.
So aside from the ProTools workplace how else can we get metadata into our files?
Sound Devices who have been actively involved in the development of the iXML open standard have a free metadata application available for mac & PC called WAVE AGENT – downloadable here which allows playback of polyphonic and monophonic BWF and standard WAV files from any source, up to 12-tracks wide, plus allows viewing and editing metadata, batch editing, file-renaming and mono/poly file conversion! Here’s a demo of it in use:
Ok so thats my metadata rant for now, tomorrow I am going to send an email to each company that sells a sound library app, and ask for a specific explanation of their metadata implementation and support. I shall report back!
Please also feel free to consider this an open thread on the subject of metadata…
- do you inject metadata into your sound library files?
- what sound library app/s do you use?