Share Your Microphone Calibration Files to Help Us Improve Room Correction

[DG77]

Hi everyone! Our team is working on some new features and improve the ways we deliver exceptional audio experiences. To achieve this, we're collecting microphone calibration files from different sources, including the community. Your contributions will help us improve compatibility with different microphones, enhance audio processing algorithms, and deliver more accurate sound reproduction!

How You Can Help​

If you have microphone calibration files in any format (e.g., CSV, XML, JSON, DAT, etc.), please share them with us. Your microphone calibration files can make a significant impact. By sharing them with us, you'll aid our development team in understanding diverse file formats and structures, developing effective parsing methods, and optimizing audio processing. Any calibration file you share will contribute to our research and development.

What We Need​

We're looking for calibration files from various microphones, such as measurement mics and USB mics, in different formats like CSV, XML, JSON, DAT, and others. Additionally, please provide information about the file format, microphone model, measurement conditions (e.g., room type, distance), and any other relevant details.

How to Share​

• Reply to this thread with a link to your calibration file(s) or attach them directly. If you'd prefer to share this privately, please feel free to send it directly to myself and or @WiiM Team
• Provide a brief description of the file format, microphone model, and context.

Thank You!​

We appreciate your help and look forward to receiving your calibration files!

Hi everyone! Our team is working on some new features and improve the ways we deliver exceptional audio experiences. To achieve this, we're collecting microphone calibration files from different sources, including the community. Your contributions will help us improve compatibility with different microphones, enhance audio processing algorithms, and deliver more accurate sound reproduction!

How You Can Help​

If you have microphone calibration files in any format (e.g., CSV, XML, JSON, DAT, etc.), please share them with us. Your microphone calibration files can make a significant impact. By sharing them with us, you'll aid our development team in understanding diverse file formats and structures, developing effective parsing methods, and optimizing audio processing. Any calibration file you share will contribute to our research and development.

What We Need​

We're looking for calibration files from various microphones, such as measurement mics and USB mics, in different formats like CSV, XML, JSON, DAT, and others. Additionally, please provide information about the file format, microphone model, measurement conditions (e.g., room type, distance), and any other relevant details.

How to Share​

• Reply to this thread with a link to your calibration file(s) or attach them directly. If you'd prefer to share this privately, please feel free to send it directly to myself and or @WiiM Team
• Provide a brief description of the file format, microphone model, and context.

Thank You!​

We appreciate your help and look forward to receiving your calibration files!

Minidsp umik 1
Text file format
Mesurement conditions: using tripod from listening sweetspot
Room is 4x4,5 meters and height is 2.4 meters

 

[Pikouchou]

Hi,
Dayton IMM6-C
Calibration file from Dayton with serial number

 

[Francesco58]

iMM-6C

file released by manufacturer upon sending serial number

 

[s3igell]

Thats what I dont understand. We are asked for room type etc when the calibration files are produced by the manufacturer so you dont need that info. That info would have a value if you could export a file from the WiiM app after doing the sweep with the mic plugged in

I suspect that the phrasing and grammar went through at least one translation before Ryan posted it in the OP. And it seems that some folks here are (purposefully?) taking some of the more difficult interpretations.
Perhaps the OP is partly in response to the shear volume of RC related posts - many evincing dissatisfaction with the product or the results based mostly on expectations fostered from more sophisticated products such as Dirac.
Lets give them the benefit of the doubt, and appreciate that they are asking for productive input in the form of manufacturer's calibration files (perhaps to understand the general accuracy of add-on mics vs their original experiences with Apple embedded mics) and the mechanics of how users (not mic manufacturers) used those mics when performing their WiiM RC measurements (perhaps to understand those who kept offering that "only multiple measurements from multiple positions around the main listening position..." and such).

 

[guy48065]

Well sure... But this could all be cleared up in 1 paragraph by the OP.

 

[bherren]

Dayton IMM-6 (using with google USB-C jack adapter)

 

[Joseespona]

I suspect that the phrasing and grammar went through at least one translation before Ryan posted it in the OP. And it seems that some folks here are (purposefully?) taking some of the more difficult interpretations.
Perhaps the OP is partly in response to the shear volume of RC related posts - many evincing dissatisfaction with the product or the results based mostly on expectations fostered from more sophisticated products such as Dirac.
Lets give them the benefit of the doubt, and appreciate that they are asking for productive input in the form of manufacturer's calibration files (perhaps to understand the general accuracy of add-on mics vs their original experiences with Apple embedded mics) and the mechanics of how users (not mic manufacturers) used those mics when performing their WiiM RC measurements (perhaps to understand those who kept offering that "only multiple measurements from multiple positions around the main listening position..." and such).

Well, Its just constructive criticisim. WiiM is giving us the chance to give our feedback and that is something that I keep praising over and over again. Its a win win. We give our thoughts and they make better products. The problem with writing in a forum is that the message is just posted and can be regarded as toxic when it may just be an input. They are making a big efford with RC and trying to optimise it so thats why they ask for data, but as users we also want to know why and how they will use the data

 

[slartibartfast]

Dayton IMM-6 (using with google USB-C jack adapter)

How do you know the USB jack adapter isn't changing the frequency response? I have a TRRS to USB A adapter (not Google) and mine definitely does affect the frequency response.

 

[apeace]

Hi everyone! Our team is working on some new features and improve the ways we deliver exceptional audio experiences. To achieve this, we're collecting microphone calibration files from different sources, including the community. Your contributions will help us improve compatibility with different microphones, enhance audio processing algorithms, and deliver more accurate sound reproduction!

How You Can Help​

If you have microphone calibration files in any format (e.g., CSV, XML, JSON, DAT, etc.), please share them with us. Your microphone calibration files can make a significant impact. By sharing them with us, you'll aid our development team in understanding diverse file formats and structures, developing effective parsing methods, and optimizing audio processing. Any calibration file you share will contribute to our research and development.

What We Need​

We're looking for calibration files from various microphones, such as measurement mics and USB mics, in different formats like CSV, XML, JSON, DAT, and others. Additionally, please provide information about the file format, microphone model, measurement conditions (e.g., room type, distance), and any other relevant details.

How to Share​

• Reply to this thread with a link to your calibration file(s) or attach them directly. If you'd prefer to share this privately, please feel free to send it directly to myself and or @WiiM Team
• Provide a brief description of the file format, microphone model, and context.

Thank You!​

We appreciate your help and look forward to receiving your calibration files!

MiniDSP UMIK-1

 

[harkpabst]

How do you know the USB jack adapter isn't changing the frequency response? I have a TRRS to USB A adapter (not Google) and mine definitely does affect the frequency response.

These "adapters" are really ADCs (with all the necessary circuitry) and often also contain a DAC (if they provide an analogue output, too). You don't know how they perform unless somebody measured one of them

Definitely an additional variable in the mix, yes.

 

[guy48065]

Can someone post a pic of one of these micro-USB to USB-C adapters?
My previous phone came with one and it looks too small to be an active interface.

 

[slartibartfast]

Can someone post a pic of one of these micro-USB to USB-C adapters?
My previous phone came with one and it looks too small to be an active interface.

We are talking about TRRS jack to USB adapters not USB to USB adapters.

 

[jac-st]

Product description when purchasing:

"High-quality sound - With the ALC4050/5686 chip with 32-bit 384 kHz DAC and high-quality cable, the AUX to USB-C adapter offers excellent sound quality without interference. This allows you to enjoy the highest possible sound quality.
High-quality microphone - The ADC parameters are 24Bit 96Khz, which ensures that the microphone input of the Type-C to AUX adapter is capable of recording the audio signal in great detail and accurately. This results in excellent sound quality and a more faithful reproduction of the original sound. "

 

[jac-st]

Imm-6 99-56504 (clean calibration file from the manufacturer)

 

[guy48065]

We are talking about TRRS jack to USB adapters not USB to USB adapters.

Brain fart--I forgot the imm-6 was TRRS.

I notice many of the dongles sold on Amazon are tagged with a "frequently returned item" note so maybe crappy audio quality is a "feature" of many of these dongles.

 

[rcon7]

Hi everyone! Our team is working on some new features and improve the ways we deliver exceptional audio experiences. To achieve this, we're collecting microphone calibration files from different sources, including the community. Your contributions will help us improve compatibility with different microphones, enhance audio processing algorithms, and deliver more accurate sound reproduction!

How You Can Help​

If you have microphone calibration files in any format (e.g., CSV, XML, JSON, DAT, etc.), please share them with us. Your microphone calibration files can make a significant impact. By sharing them with us, you'll aid our development team in understanding diverse file formats and structures, developing effective parsing methods, and optimizing audio processing. Any calibration file you share will contribute to our research and development.

What We Need​

We're looking for calibration files from various microphones, such as measurement mics and USB mics, in different formats like CSV, XML, JSON, DAT, and others. Additionally, please provide information about the file format, microphone model, measurement conditions (e.g., room type, distance), and any other relevant details.

How to Share​

• Reply to this thread with a link to your calibration file(s) or attach them directly. If you'd prefer to share this privately, please feel free to send it directly to myself and or @WiiM Team

• Provide a brief description of the file format, microphone model, and context.

Thank You!​

We appreciate your help and look forward to receiving your calibration files!

Dayton imm6c

 

[harkpabst]

MiniDSP UMIK-2
Omni-directional USB "digital" measurement microphone, 1/2" capsule, ADC supporting 32 bit, 44.1 kHz - 192 kHz output.

The calibration files for 0° and 90° are in text format.

The first line of the of the calibration files is enclosed in quotes. REW and HouseCurve (and possibly most other measurement software) ignore lines not starting with a number, so this is not directly read as calibration data. However, the comment contains data describing the sensitivity of the microphone. The UMIK-2 calibration file slightly differs from the UMIK-1. The UMIK-2 file contains separate values for "Sens Factor" and "AGain". According to the MiniDSP devteam "Sens Factor" denotes the sensitivity and "AGain" describes the fixed, analogue gain of the circuitry. AGain is always 18 dB for those 9 UMIK-2 calibration files I have reviewed so far.

It appears that these two values must be used in combination to put them to work. E.g.:
Sens Factor =-10.38dB
AGain =18dB
But according to the manual:
Sensitivity: -31.9 dB FS (94 dB SPL. 1 kHz)
MAX SPL(0dBfs): 125dB SPL

• The sensitivity value almost matches the max. SPL number perfectly, it should be 94 dB - 125 dB = -31 dB (or the max. SPL should be 124.1 dB, resulting in a sensitivity of -31.9 dB FS).
• Since there is an analogue gain of 18 dB, the digital reading at 94 dB SPL, 1 kHz is not -31 dB FS, but rather around -13 dB FS (=> Sens Factor). Looking at different cal files, some mics come close to that, some are closer to -10 dB FS.

All this is mainly of interest for absolute SPL measurements, not necessarily for room correction. It's important to stay clear of the maximum SPL, of course.

The calibration file for 90° contains a second comment line. It states that it has been created automatically, based on previously collected reference data for 90° use vs. 0° use. So, the 90° file is not the result of direct calibration, but derived from the 0° file.

 

[pieterv1]

These are the calibration files of my individual Sonarworks SoundID Reference measurement microphone.
Seems to be measured at 90, 30 and 0 degrees by the manufacturer.

 

[Odzi]

UMIK-1

 

[Atlas B170]

Dayton iMM-6
.txt