REW Beta Release REW API beta releases

trobbins · Jan 7, 2025

Removed.

John Mulcahy · Jan 7, 2025

dcibel said:
It would be great if REW would close the triangle and show slope as well, in dB/oct.

You can get that from the graph metrics.

dcibel · Jan 7, 2025

Ah, I knew it had to be in there somewhere. Thanks for the reminder John.

JoinUs · Jan 9, 2025

Hello John, is there a way to disable the Data Offset when importing WAV files?

For example, let’s assume that a Dirac Pulse is generated in REW, which has an offset of 0.
When it is re-imported, an offset is applied. (This also happens with various WAV files, including those generated in RePhase.)

And in the case of a simple pulse like this, applying the Data Offset is intuitive.
However, for something like noise, it can be more difficult to determine.

Something like this.

Is there any way to disable this feature?

serko70 · Jan 10, 2025

JoinUs said:
Hello John, is there a way to disable the Data Offset when importing WAV files?

View attachment 77212

For example, let’s assume that a Dirac Pulse is generated in REW, which has an offset of 0.
When it is re-imported, an offset is applied. (This also happens with various WAV files, including those generated in RePhase.)

View attachment 77213

And in the case of a simple pulse like this, applying the Data Offset is intuitive.
However, for something like noise, it can be more difficult to determine.

View attachment 77214

Something like this.

Is there any way to disable this feature?

You can find the volume offset applied to the imported impulse in the Info window under "Data offset"

JoinUs · Jan 10, 2025

serko70 said:
You can find the volume offset applied to the imported impulse in the Info window under "Data offset"

I can't see volume offset.

serko70 · Jan 10, 2025

JoinUs said:
View attachment 77217

I can't see volume offset.

120dB, you have to apply -120dB offset to that response...

JoinUs · Jan 10, 2025

serko70 said:
120dB, you have to apply -120dB offset to that response...

wow.
If different offsets are applied to each impulse, does subtracting that value make all the volumes equal?
I was aware of those offsets, but it seems I misunderstood them to some extent.

John Mulcahy · Jan 10, 2025

The offset depends on the input device, it converts dBFS values from the input data to SPL according to the input SPL calibration.

sm52 · Jan 11, 2025

John Mulcahy

At the bottom of the Measurement info panel, the Output FS sine line should show the current measurement level?

John Mulcahy · Jan 12, 2025

sm52 said:
At the bottom of the Measurement info panel, the Output FS sine line should show the current measurement level?

No, it shows the full scale ("FS") voltage for the output.

sm52 · Jan 12, 2025

Thank you.

John Mulcahy · Jan 13, 2025

Builds updated today (beta 66) with these changes:

Added: The Impulse graph has an "Apply 2Hz HP" action to help counter the effect of DC offsets in measurements
Fixed: FSAF file selector was disabled after making a sweep measurement
Fixed: Loading a large number of measurements or importing a large number of files was very slow
Fixed: Saving a large number of measurements was very slow

armagedon · Jan 15, 2025

hello, first tank you for this amazing software. I actively support it.
I have 3 feature request.
1: it is possible to add support for "addMTW" into the API (/measurements/{id}/ir-windows) like it doing for "addFDW".
2: it is possible to force the "Align offset" value, through the API. For 2 reasons, first, AVR only allow 0.5dB steep, and want to set the closer value. Second, want to be able to cancel this by "undo spl alignment" function.
3: I know this point was already discussed, but, will be nice to have new API path to be able to upload file content instead of the file path. the existing "/import/frequency-response" and "/import/impulse-response" makes sense and should be keeped. Data can be posted in base64 as is done by "/measurements/{id}/impulse-response". this will solve some problems.

John Mulcahy · Friday at 9:26 AM

armagedon said:
1: it is possible to add support for "addMTW" into the API (/measurements/{id}/ir-windows) like it doing for "addFDW".

I have added that for the next build.

armagedon said:
2: it is possible to force the "Align offset" value, through the API. For 2 reasons, first, AVR only allow 0.5dB steep, and want to set the closer value. Second, want to be able to cancel this by "undo spl alignment" function.

No, but you can set your own SPL offsets through the API.

armagedon said:
3: I know this point was already discussed, but, will be nice to have new API path to be able to upload file content instead of the file path. the existing "/import/frequency-response" and "/import/impulse-response" makes sense and should be keeped. Data can be posted in base64 as is done by "/measurements/{id}/impulse-response". this will solve some problems.

I'll add that to the request list.

armagedon · Friday at 1:51 PM

thank you for all you are doing for us.
waiting for next release.

sm52 · Saturday at 1:33 PM

John Mulcahy,

Should the 'restore last deleted' measurements button restore the one measurement that was just deleted? And if I deleted 8 measurements, this function does not work? I removed 1 measurement - it works. I deleted 8 measurements - it is not active. This happened several times. And after the restart, REW reported that it could not complete normally and there were 138 measurements to restore. I took impedance measurements.

sm52 · Saturday at 1:43 PM

Second question. There is confusion with measurement numbers. I'm removing one measurement from the Impedance & Phase tab. Then I go to the ALL Impedance tab. There are 35 left in the legend, and 34 on the left.

sm52 · Saturday at 1:47 PM

The third question, I'm not sure about this one. I assumed that I was deleting one group of measurements, but another one was deleted. The measurements are not arranged in groups, just one part and another part of the general list.

John Mulcahy · Saturday at 4:05 PM

sm52 said:
Should the 'restore last deleted' measurements button restore the one measurement that was just deleted? And if I deleted 8 measurements, this function does not work?

Yes.

John Mulcahy · Saturday at 4:32 PM

sm52 said:
I'm removing one measurement from the Impedance & Phase tab. Then I go to the ALL Impedance tab. There are 35 left in the legend, and 34 on the left.

Actually both have 34 measurements, but the numbering shown in the legend is wrong for measurements after the one that was removed. I have fixed it for the next build.

John Mulcahy · Saturday at 4:50 PM

sm52 said:
I assumed that I was deleting one group of measurements, but another one was deleted.

That's a bit too vague for me to do anything with.

John Mulcahy · Sunday at 11:53 AM

Builds updated today (beta 67) with these changes:

Added: API supports reading and setting IR Multi-Time Windows
Changed: Impedance measurement dialog allows sense resistor values up to 1M and input impedance up to 100M
Fixed: Trace numbers shown in overlay graph legends could be wrong after measurements were removed
Fixed: Multi-line HTML-formatted comments on graph image captures were not rendered correctly

armagedon · Monday at 3:38 AM

thank you for the update. everything is working perfectly.
I would like to take this opportunity to also ask for an other feature request. nothing urgent.
this concern the measurement window. It is possible to port some of the new functionality to "from file" playback.
the idea is to load atmos files for each channel in the playlist of the player, then be able to ask REW to repeat measurements until the end of the playlist.
also there is no possibility to disable the "capture noise floor", it would be great to be able to do it.

John Mulcahy · Monday at 10:47 AM

armagedon said:
the idea is to load atmos files for each channel in the playlist of the player, then be able to ask REW to repeat measurements until the end of the playlist.

That has been requested previously, it is on the list to look at.

armagedon said:
there is no possibility to disable the "capture noise floor"

That's a bug, it should be visible. I have fixed it for the next build.

REW Beta Release REW API beta releases

Member

REW Author

Member

New Member

Member

New Member

Member

New Member

REW Author

Member

John Mulcahy​

REW Author

Member

REW Author

Registered

REW Author

Registered

Member

John Mulcahy,​

Attachments

Member

Attachments

Member

REW Author

REW Author

REW Author

REW Author

Registered

REW Author

Popular tags

John Mulcahy

John Mulcahy,