Abstract
We present a database of acoustic transfer functions of the Hearpiece, a commercially available multi-microphone multi-driver in-the-ear earpiece for hearing device research. The database includes HRTFs for 87 incidence directions as well as responses of the drivers, all measured at the four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human participants and a KEMAR with anthropometric pinnae for five insertions of the device. We describe the measurements of the database and analyse derived acoustic parameters of the device. All regarded transfer functions are subject to differences between participants and insertions. Also, the KEMAR measurements are close to the median of human data in the present results for all assessed transfer functions. The database is a rich basis for development, evaluation and robustness analysis of multiple hearing device algorithms and applications. It is openly available at https://doi.org/10.5281/zenodo.3733190.
Highlights
Development and evaluation of hearing devices like hearing aids or hearables and appropriate algorithms is greatly facilitated by utilizing simulations
To simulate input signals of hearing devices, signals can be convolved with appropriate Headrelated Transfer Functions (HRTF) that describe the acoustic free-field transmission to the hearing device microphone from a certain incidence direction
We present a database of all linear transfer functions of the Hearpiece, an in-the-ear earpiece with wired transducers for hearing device research introduced in 2019 that is commercially available [16]
Summary
Development and evaluation of hearing devices like hearing aids or hearables and appropriate algorithms is greatly facilitated by utilizing simulations. One limitation of existing hearing device HRTF datasets is that while they can be utilized well to study the theoretical performance of algorithms, most authors used custom devices that are not available to other researchers. This means that others would have to build their own devices given the (often sparse) documentation in order to transfer their developments to real-time devices that are usable in the field
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
