It would be fine to look at low frequencies, up to 1 kHz or so. It's also fine to look at RT60 data, since the rates of decay don't depend on the frequency response shape. There is no point using a generic cal file as the mics vary too much.
Apparently that's the control panel rather than the driver and it has no effect on the operation of the driver, which is not subject to the priority settings of user programs like the control panel.
Meaning you want two decimal places? I can't see the point of that.
I could add it, but the reason it only appears on Predicted SPL is that's the only place the action will have a visible effect on the traces.
Seems a lot, but you haven't said which version you are running or shown the source or head positions, so difficult to say. Current release build is 5.31.3.
The message is a bug which occurs if the ref output (not used for impedance measurements) is not the same as the measurement output as the test signal is incorrectly being sent to the ref output. I have fixed it for the next beta build.
That's impractical, I'm afraid. The mdat files are serialised Java objects, reading them would require the Java class files for all the classes they contain.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.