REW Beta Release REW API beta releases

Can you attach the mdat file which produced that? What equaliser were you using? Any other info on what led up to the error?
It seems to be an intermittent issue that pops up when I open an .mdat file that contains the results from an Audyssey One run (this script specifically). I always use the Generic/Generic equalizer. Next time it happens I'll send you the .mdat. The challenge though is that anytime it happens and I close REW, opening the .mdat next time does not result in the same error.
 
Could you send me an mdat from running that script? Preferably before changing anything in it.
 
Those files look fine. I added a check to avoid the error, which was due to an un-initialised filter, but I don't know how that might occur so the fix might not help.
 
@John Mulcahy Quick question regarding the RTA:

When I set RTA Mode to e.g. RTA 1/12 octave, why can I still configure FFT Length manually?
In RTA mode (not Spectrum mode), I'd expect the FFT length to be purely a function of RTA resolution and sample rate.

Related to that, when I've created an RTA 1/12 Octave measurement at 48kHz, click "Save current", then "File->Export->Export measurement as text" with the options "Use range/resolution/smoothing of measurement" enabled, then I get a file with 1020 data points between 14.6484438Hz and 22966.735945Hz.

So that appears to be 1020/log2(22967/14.6) = 1/96 Octave resolution, even though the RTA with "Use bars on RTA" definitely showed 1/12-typical resolution (e.g. 12 distinct data points between 1kHz and 2kHz) and I chose to export at that same resolution.

But now in the exported file I have some 96 data points in the same 1-2kHz range where there should've been 12 and I'm wondering where they came from.

This is on REW V5.40 Beta 124.
 
Last edited:
When I set RTA Mode to e.g. RTA 1/12 octave, why can I still configure FFT Length manually?
The RTA mode affects how the data are displayed, the data still come from an FFT.

Related to that, when I've created an RTA 1/12 Octave measurement at 48kHz, click "Save current", then "File->Export->Export measurement as text" with the options "Use range/resolution/smoothing of measurement", then I get a file with 1020 data points between 14.6484438Hz and 22966.735945Hz.

So that appears to be 1020/log2(22967/14.6) = 1/96 Octave resolution, even though I selected "Use resolution of measurement" and the measurement was created with 1/12 Oct resolution?
Log spaced data are stored internally with 96 PPO resolution.
 
Running sweeps from REW, it appears that longer sweeps are louder than shorter sweeps.
:ponder:
rew.jpg

Michael
 
The behaviour of dynamic volume depends on the signal it sees, longer sweeps spend more time at lower frequencies so it treats them differently. All such effects should be off for measuring.
 
Builds updated today (beta 125) with these changes:
  • Added: The 3D settings dialog has preset buttons
  • Changed: Allow the RTA input trace to be hidden
  • Fixed: Changing the settings of a configurable equaliser for a measurement did not update the configuration saved in the measurement
  • Fixed: French and German help table of contents used incorrect character set
  • Fixed: Filtered periodic noise signals (including CTA2034 and Speech) had the same data on both channels even if the "uncorrelated" option was selected
  • Fixed: After level checks the signal generator was not fully restored to its previous settings if it had been using the same noise signal as the level check

Windows builds from beta 125 are signed with a new certificate. Windows SmartScreen will warn that the app is not recognised until it has seen sufficient downloads, click "More info" to run the installer.
 
FYI: Downloading in Edge puts me into an endless loop of Windows trying to protect itself, me telling Windows REW is safe, Windows again trying to protect itself. And I long ago disabled every form of protection modes I was able to find and control myself (Win 10, final revision).

Downloading with Chrome and opening the file, I simply had to confirm REW was safe before the install started, and I was good to go.

'Might help others who have run into the same or similar issue.

*Chrome is my default browser, but the site opens in Edge when I click the link from the REW popup window.

1778337585377.png
 
Back
Top