REW Beta Release REW API beta releases

[John Mulcahy]

Builds updated today (beta 78) with these changes:

• Added: Burst decay waterfall and spectrogram plots have more octave fraction choices
• Changed: Equalisers that run at the rate of the measurement (e.g. Generic) will default to the REW sample rate when no measurements are loaded
• Changed: Longer measurement names are allowed, but the name will be truncated if necessary in graph legends
• Fixed: Setting a toneburst with a burst length longer than the burst period caused an error
• Fixed: Alignment tool phase traces were plotted red if the alignment tool smoothing differed from the measurement smoothing
• Fixed: Measurement names might be truncated in the overlay view selectors used by All SPL and the Overlays window
• Fixed: Stepped IMD plots used total input RMS as the reference level for dBr and percent instead of the relevant reference for the IMD measure
• Fixed: The measurement name preview on the Measure dialog did not enforce the name length limit, name preview now turns red if name is too long and will be truncated
• Fixed: API commands to make a measurement did not check that measurement was possible
• Fixed: API changes to the default target settings might be overridden by GUI components
• Fixed: House curve file set through the API was not remembered for the next startup
• Fixed: API gets that should return String values returned the string as a message field, affecting the following endpoints:
  • /alignment-tool/uuid-a
  • /alignment-tool/uuid-b
  • /eq/house-curve
  • /import/sweep-recordings/stimulus
  • /import/sweep-recordings/response
  • /import/frequency-response
  • /import/frequency-response-data
  • /import/impulse-response
  • /import/impulse-response-data
  • /import/rta-file
  • /measure/notes
  • /measure/measurement-mode
  • /measure/filtered-spl-filter-source-uuid
  • /measure/playback-mode
  • /measure/file-playback-stimulus
  • /measure/timing/reference
  • /measure/timing/reference/none/tzero
  • /measurements//selected-uuid
  • /rta/y-axis
  • /stepped-measurement/type

 

[Nicoo]

Hi John,

Have been trying all the afternoon to get it working on my end (Denon 4700H with Audyssey App and A1 Evo) but keep having the same error from A1 Evo (both on my Windows PC and Mac).

[WARNING!] Target curve not found! Browse to and select 'TargetCurve_MJ.txt' (or any other) in 'REW / EQ window / House curve'!

However, I confirm that I did include this file coming straight from A1 Evo into the House curve field as shown below.

Any idea on what I am doing wrong here?

Thanks a lot for your help!!

 

[John Mulcahy]

The release fixed a bug affecting the way some endpoints, including the house curve endpoint, return String values. The A1 script probably needs an update to account for that.

 

[Nicoo]

Appreciate the express response here!

Is there a way to get access to the previous version by chance?

 

[John Mulcahy]

The files, including some earlier beta builds, are at https://www.roomeqwizard.com/installers/

 

[Nicoo]

Works! Thanks a lot again!

 

[serko70]

Sorry to hijack the REW Beta thread but to avoid further queries:

A1 Evo Acoustica v3.2 has been uploaded and is fully compatible with REW Beta 78 (and no longer compatible with any lower REW versions).

Thanks.

 

[JoinUs]

Hi John, this isn’t a big deal, but it just occurred to me and I wanted to ask: when using REW’s capture feature, weren’t the names of each measurement tab (in the current image, “SPL & Phase”) center-aligned? Why are they shifted to the left like this?


## and btw I just watched the AV NIRVANA YouTube replay. Once again, thank you and your REW.

 

[JoinUs]

I got Error.

errorrr.mdat

drive.google.com

Clicking the exported RoomSim entry at the very bottom of the mdat file causes an error.

REW V5.40 Beta 78 running Azul Systems, Inc. JRE 1.8.0_452 64-bit on Windows 10 Locale: language ko, keyboard KR, x-windows-949 on 2048x1152 at 96 DPI Running in C:\Program Files\REWbeta


Message:
java.lang.NullPointerException
Stack Trace:

Spoiler

java.lang.System.arraycopy(Native Method)
roomeqwizard.MeasData.<init>(y:2675)
roomeqwizard.MeasData.filterNoIR(y:3091)
roomeqwizard.MeasData.filterMeasurement(y:833)
roomeqwizard.MeasData.applyFiltersImmediate(y:288)
roomeqwizard.uB.p(y:2414)
roomeqwizard.ZE.I(y:960)
roomeqwizard.ZE.ǜ(y:3319)
roomeqwizard.ZE.valueChanged(y:530)
ca.odell.glazedlists.swing.DefaultEventSelectionModel.fireSelectionChanged(Unknown Source)
ca.odell.glazedlists.swing.DefaultEventSelectionModel.access$100(Unknown Source)
ca.odell.glazedlists.swing.DefaultEventSelectionModel$SwingSelectionListener.selectionChanged(Unknown Source)
ca.odell.glazedlists.ListSelection.fireSelectionChanged(Unknown Source)
ca.odell.glazedlists.ListSelection.setSubRangeOfRange(Unknown Source)
ca.odell.glazedlists.ListSelection.select(Unknown Source)
ca.odell.glazedlists.swing.DefaultEventSelectionModel.addSelectionInterval(Unknown Source)
javax.swing.plaf.basic.BasicTableUI$Handler.mousePressedDND(BasicTableUI.java:1058)
javax.swing.plaf.basic.BasicTableUI$Handler.mousePressed(BasicTableUI.java:1032)
ca.odell.glazedlists.swing.TreeTableSupport$ExpandAndCollapseMouseListener.mousePressed(Unknown Source)
java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:280)
java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:279)
java.awt.Component.processMouseEvent(Component.java:6536)
javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
java.awt.Component.processEvent(Component.java:6304)
java.awt.Container.processEvent(Container.java:2239)
java.awt.Component.dispatchEventImpl(Component.java:4889)
java.awt.Container.dispatchEventImpl(Container.java:2297)
java.awt.Component.dispatchEvent(Component.java:4711)
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4904)
java.awt.LightweightDispatcher.processMouseEvent(Container.java:4532)
java.awt.LightweightDispatcher.dispatchEvent(Container.java:4476)
java.awt.Container.dispatchEventImpl(Container.java:2283)
java.awt.Window.dispatchEventImpl(Window.java:2746)
java.awt.Component.dispatchEvent(Component.java:4711)
java.awt.EventQueue.dispatchEventImpl(EventQueue.java:760)
java.awt.EventQueue.access$500(EventQueue.java:97)
java.awt.EventQueue$3.run(EventQueue.java:709)
java.awt.EventQueue$3.run(EventQueue.java:703)
java.security.AccessController.doPrivileged(Native Method)
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:84)
java.awt.EventQueue$4.run(EventQueue.java:733)
java.awt.EventQueue$4.run(EventQueue.java:731)
java.security.AccessController.doPrivileged(Native Method)
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
java.awt.EventQueue.dispatchEvent(EventQueue.java:730)
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

 

[John Mulcahy]

I got Error.

Fixed for the next build.

 

[John Mulcahy]

this isn’t a big deal, but it just occurred to me and I wanted to ask: when using REW’s capture feature, weren’t the names of each measurement tab (in the current image, “SPL & Phase”) center-aligned? Why are they shifted to the left like this?

When the cursor isn't included in a capture the data values at the cursor position are omitted, that could make the labels appear to be offset to the left a little since the space for the data values is still allocated.

 

[JoinUs]

When the cursor isn't included in a capture the data values at the cursor position are omitted, that could make the labels appear to be offset to the left a little since the space for the data values is still allocated.

Hmm... When i check in Photoshop

Of course, this isn’t really that far off, but…

They’re definitely shifted too far to the left when viewed relative to the center. =(

 

[John Mulcahy]

They’re definitely shifted too far to the left when viewed relative to the center. =(

Sorry, I misread your post. I have fixed that for the next build.

 

[Tikkidy]

Dear John,

The screen capture in MacOS doesn't seem to work. Or that it works, but then I can't seem to paste it directly here:

eg. pasting here... uploading...

-progress to 100%-


-error message-



I was only able to post this message by taking a screenshot, saving to a file...then uploading the file...

Inconvenient but of course no end of the world.

Thought I would let you know.

BR,
Thanh
Australia

 

[John Mulcahy]

I can copy an image using the image capture dialog and paste it into an email OK, so this doesn't seem to be an REW problem.

 

[Tikkidy]

Totally works fine on my windows system too

 

[John Mulcahy]

I used a Mac for the check.

 

[Tikkidy]

Testing 123

Windows 10 Home 64bit 10.0 Build 190945
Forum browser- Chrome Version 135.0.7049.115 (Official Build) (64-bit)
REW V5.40Beta78

 

[Tikkidy]

macOS 15.4.1 (24E263)
Forum browser- Safari 18.4 (20621.1.15.11.10)
REW V5.40Beta78

Capture -> Copy
Paste:

 

[Tikkidy]

macOS 15.4.1 (24E263)
Forum browser- Chrome Version 136.0.7103.49 (Official Build) (arm64)
REW V5.40Beta78

Capture -> Copy
Paste:


gets stuck on this screen:


Must be my mac...

 

[JoinUs]

Added: Action to make response copies of all selected measurements

Hello John,

Thank you as always. Previously, I asked for a feature to copy selected measurements all at once, and you implemented it—it's incredibly convenient. If it’s not too much trouble, could you add a similar function that generates the minimum-phase and excess-phase for selected measurements in one go?
The current duplicate feature is already fantastic, but I still have to create minimum/excess phase manually.

 

[John Mulcahy]

If you carry out a lot of manual steps on multiple measurements it would probably make sense to invest some time to learn enough of a programming language to automate the whole process via the API.

 

[JoinUs]

If you carry out a lot of manual steps on multiple measurements it would probably make sense to invest some time to learn enough of a programming language to automate the whole process via the API.

You are right. I understand.
I previously built part of my workflow automation using the API, and it was really convenient. However, since what I’m trying to automate isn’t always consistent, I wanted to ask about that. It would be even better if we could assign custom keyboard shortcuts… but I guess that’s not possible, right? =(

 

[John Mulcahy]

It would be even better if we could assign custom keyboard shortcuts

That's also something you could emulate with the API, having API calls that retrieve the currently selected measurement and then run a set of operations.