At 11:54 AM +0000 11/8/10, Raimund wrote:
>
>
>I have recently added a metadata managing tool to the Avisoft-SASLab
>Pro sound analysis software
>(<http://www.avisoft.com/soundanalysis.htm>http://www.avisoft.com/soundana=
lysis.htm)
>that allows entering user-defined data fields, which are embedded
>into the individual .wav files by using a custom-specific "dXML"
>RIFF chunk. These embedded data sets can subsequently be exported
>into separate .xml formatted sidecar files or they can be integrated
>into a simple XML-formatted metadata base.
>
>Here are a few screen shots that illustrate how it looks like:
><http://www.avisoft.com/dxml/dxml.pdf>http://www.avisoft.com/dxml/dxml.pdf
>
>Sample files:
><http://www.avisoft.com/dxml/T0037.wav>http://www.avisoft.com/dxml/T0037.w=
av
><http://www.avisoft.com/dxml/T0037_dxml.xml>http://www.avisoft.com/dxml/T0=
Message: 037_dxml.
Subject: xml
>
>This (expensive) software is however primarily aimed at bioacoustic
>research and probably not suited for general use.
>
>Regards,
>Raimund
>
Hi Raimund--
I think it makes a lot of sense to use metadata this way-- especially
between researchers who have agreed upon data needs and have the same
app. Same is true for SoundMiner and FileMaker.
It also shows how much we need a global database structure to work
backwards from so developers like you can be writing and testing the
translators at the same time. No developer can sell apps to everyone,
of course, but we recordists can make a global database structure
from open source, free and very low cost software options and
increase demand for more cooperation. Ambitious, yes, but maybe the
only direction that can support many of the good things we are
imagining. Rob D.
--
|