I'm not really following that, where would the "current filters" come from? You can make REW use specific filter positions by disabling the positions you do not want it to use or deselecting "Auto EQ" for those positions.
A more sensible SPL span would be around 60 dB, at the moment you have a span of about 160 dB. You can use the Limits button top right of the graph to set suitable top and bottom SPL values for the graph.
Probably not, but a modal filter is just a peaking filter with internal constraints applied so you could try changing the modal filter to peaking before exporting it. The frequency, gain and Q values will not be altered.
Make sure there is no monitoring active on the interface mixer. One way to check that would be to leave all the connections as they are and just make a normal SPL measurement and look at the result, which should be flat.
With what driver selection? If you are using ASIO you should get the same result, with Java drivers the Windows volume control may be in the path. For Java choose device names starting with EXCL to use WASAPI Exclusive drivers.
Cal results are generally in dB, offset to be zero at 1kHz. They are ratios in effect so the unit doesn't matter. If you have individual cal file results you could drag them into REW and use trace arithmetic to sum them.
The Decay graph might be a better option to view a series of spectral decay traces.
Time and frequency resolution are a trade-off, longer windows have higher frequency resolution and lower time resolution, shorter windows the opposite. Window type has an influence, but Gaussian is a good...
Seeing the same error messages at 96k suggests a problem with the Mac's connection to the Cosmos ADC.
Manual fundamental is for use with a notch filter to tell REW the level of the pre-notch signal. There is help. The fundamental frequency is found automatically from the largest peak in the...
Builds updated today (beta 132) with these changes:
Added: ETON Audio equaliser entries
Added: MiniDSP Tide-16 equaliser entry
Changed: The full paths to mic and soundcard cal files are no longer saved in the mdat file to address any related privacy concerns
Fixed: NPE when generating a warning...
No, but you do not need a soundcard calibration.
The internal routing loopback should work as the timing reference. It is something that gets used every time you make a measurement, it is not a one-time process.
I think the difference arises from the way the API is trying to handle a requested smoothing of None and 96 PPO. Try setting the API smoothing to 1/48. I'll get the API to handle that automatically in the next build.
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.