SOFA conventions: Difference between revisions
m Petibub moved page SOFA Conventions to SOFA conventions |
No edit summary |
||
| Line 1: | Line 1: | ||
SOFA conventions specify the description of data and metadata for a particular kind of measured data. |
|||
SOFA conventions can be implemented without any programming by using the Common Data Form Language (CDL) as suggested for netCDF. CDL files allow for a platform-independent interpretation of specifications and can be compiled to a binary netCDF file using the ncgen tool from the netCDF package: |
|||
This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. |
|||
ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl |
|||
The binaries of the nc-tools are available at the Unidata. |
|||
We consider following rules for new SOFA conventions: |
|||
In the following, two SOFA conventions are described. Note that instead of aiming at foreseeing the future, conventions should be developed only for known measurement setups. The known features should be consistently described while not limiting the development of future conventions. |
|||
* Data must exist (do not foresee the future) |
|||
* Data can not be described by existing SOFA conventions |
|||
==Stable Conventions== |
==Stable Conventions== |
||
Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: |
|||
* [[SimpleFreeFieldHRIR]] |
|||
* [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source |
|||
==Proposed SOFA Conventions== |
==Proposed SOFA Conventions== |
||
Proposed SOFA conventions are currently being discussed. Measured data exist and the description must be fixed in order to create publicly available SOFA files and software. |
|||
* [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a reverberant space |
|||
* [[SimpleDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source |
|||
==Discussion & Requests== |
==Discussion & Requests== |
||
Here we discuss suggestions from the peer group |
|||
* Item 1 (Author 1) |
|||
* Item 2 (Author 2) |
|||
Revision as of 10:42, 17 May 2013
SOFA conventions specify the description of data and metadata for a particular kind of measured data.
This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions.
We consider following rules for new SOFA conventions:
- Data must exist (do not foresee the future)
- Data can not be described by existing SOFA conventions
Stable Conventions
Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now:
- SimpleFreeFieldHRIR: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source
Proposed SOFA Conventions
Proposed SOFA conventions are currently being discussed. Measured data exist and the description must be fixed in order to create publicly available SOFA files and software.
- SimpleBRIR: Binaural room impulse responses measured with an omnidirectional source in a reverberant space
- SimpleDRIR: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source
Discussion & Requests
Here we discuss suggestions from the peer group
- Item 1 (Author 1)
- Item 2 (Author 2)