REW Beta Release REW API beta releases

Builds updated today (beta 107) with these changes:
  • Added: Interface supports French
  • Changed: The siggen.properties bundle has additional entries for output level calibration
  • Changed: Add jdk.accessibility to the runtime
 
Hi

I have measure so SNR is mostly over 60 db. Can see in screenshot the calculated T60 values are more or less diffrent to real T60 values measured. maybe when SNR is over 60 db can use the real value that is in measurement at -60 db ?

you can see here how diffrent the real to calculate RT60 values are

188 T160.jpg


t60 51 hz.jpg


In the 51 hz slice there is show noise -50 db. but when look at the curve it is -55 - -56 db. also in the following is noise less than -61.4 db



t60 288.jpg


Is it possible with the API that there is every 1-2 sec a measure done at a frequency i need reduce reflections, for example 180 hz. usefull to walk thru room with basstraps or big basotect plate in hand and and see which place give the linearest decay. can hear with headphones. even if they are very diffrent in frequency response after short hear all sound great. so i hear and notice most important is to reduce this unlinear decay as can see ~180 hz with basotect basstrap placement or basotect placement and look that RT60 is simular after EQ too. I notice often EQ sound more worse but FR is good. because when boost frequency the decay time also increase this i think let sound the real EQ settings worse and give strange feeling in ears as when switch polarity of 1 speaker . foam do not much with FR. only can change Decay time of reverb good. and reduce decay time make sound lots better
 
Last edited:
Can see in screenshot the calculated T60 values are more or less diffrent to real T60 values measured.
T60 values as used in acoustics are defined by the slope of the decay curve, as set out in ISO3382, with an underlying assumption of a diffuse soundfield. That assumption breaks down at low frequencies in small spaces, but that doesn't mean that REW can arbitrarily redefine the meaning of the measure. The problem is not the calculation, but your use of RT60 in a frequency region and environment where it is not applicable.
 
I think the latest Beta may have a bug in convolution generation (was not a problem a ~month ago) - when exporting stereo as filters impulse response as wav both L/R channels are identical. My speakers are not identical so I always EQ them separately and now it stopped working. I can still generate 2 separate mono wav files, no bug there.
 
T60 values as used in acoustics are defined by the slope of the decay curve, as set out in ISO3382, with an underlying assumption of a diffuse soundfield. That assumption breaks down at low frequencies in small spaces, but that doesn't mean that REW can arbitrarily redefine the meaning of the measure. The problem is not the calculation, but your use of RT60 in a frequency region and environment where it is not applicable.

currently it is a version of ISO 3382-3 from 2022 . original ISO 3382 is very old, i dont know what they change in newer version, maybe the calculation ? https://www.din.de/de/mitwirken/nor...dc-beuth:din21:345469066/toc-3338603/download and here is the german page(can translate in browser) which contain previous link


this is the -2


this is the -1


ISO and DIN is same, seem the ISO is come from germany DIN and accept in ISO
 
Last edited:
John, when I look at the distortion tab for the downloaded FSAF measurement file, and the TD+N graph is displayed, there is an option to change the maximum number of harmonics displayed in the THD. If you change this digit up or down from the current number, a Java exception occurs.
 
Currently, to generate a measurement from the target shape, we’re forced to use an existing measurement in order to send the command:

POST /measurements/{id}/eq/command → "Generate target measurement"

Sometimes, no measurement exists yet. That’s why I’d like to be able to trigger this command directly from the EQ block of the API (for example):

POST /eq/default-house-curve/commands → "Generate target measurement"

This action is already possible outside the API via the application’s user interface, so it would be great to have an endpoint that exposes the same functionality.
 
Back
Top