I'm not quite sure what purpose a metadata loader/ extractor will serve.
At the NDIIPP website you will find the Version 0.2 Technical specification:
If you read pages 4 and 5 there is a reference to how "metadata evolves over
time". Additionally, there is precious little space in the BWF header,
certainly not enough to incorporate every piece of metadata collected.
Beyond that, as I have mentioned before, some DAW apps may overwrite the
stored information if the file is opened. In our commercial digital
migration business, most (if not all) of the BWF files end up on data
storage tapes - the metadata collected would not be very accessible if you
wanted to search individual fields.
If someone is to build something like this, I would assume that they are
using the SMPTE metadata dictionary (RP210v8) as a baseline?
XML would be the preferred way to go.
> From: "Richard L. Hess" <[log in to unmask]>
> Reply-To: Association for Recorded Sound Discussion List <[log in to unmask]>
> Date: Wed, 23 Mar 2005 11:31:01 -0500
> To: [log in to unmask]
> Subject: Re: [ARSCLIST] .wav file content information
> At the top of my list is a way of both loading or extracting the metadata
> from across multiple BWF files to a database structure.
> If fields can be long then CSV would not work, but dbf would. I guess XML
> would be the modern choice, but then we'd need a parser from XML to
> office-type apps.
> At 10:12 AM 3/23/2005, you wrote:
>> 2 of the software developers I contacted have shown some real interest
>> in writing some decent BWF metadata editors. Functional / interface
>> desires, anyone? Send to me or better yet post them for discussion, and
>> I'll pass them on to the developers who seem interested. I have no
>> commercial interests myself here...
> Richard L. Hess email: [log in to unmask]
> Media web: http://www.richardhess.com/tape/
> Aurora, Ontario, Canada (905) 713 6733 1-877-TAPE-FIX