REW Beta Release REW API beta releases

I don't understand that question.


FDW and MTW results are log spaced at 96 PPO and so have inherent smoothing of 1/48 octave.
i mean,

1730160438645.png


In the current beta version, to apply something to number one, or to check it out, use Alt + keyboard numbers or arrows (It's not in the current capture, but in the capture, my mouse has already clicked number 1.)

1730160478115.png


You have to assign this to the graph that I'm trying to see.
But I used to use the old version at those times, because there are a lot of times when you just replace measurements with a mouse without a keyboard. (Old versions can be activated and viewed by simply clicking on it. I understand that the current beta version has that graph turned on like a toggle when you click on it, it's turned off, and you just have to use a keyboard.)

It also doesn't matter with a few measurements, but it takes some time to find and activate each one on the keyboard when it's over 20. (Of course, you can create a group, but it feels like there's too much pre-prep action compared to the previous version where you could see and activate the desired graph with a single mouse click and apply IR windows or something like that.)
 
Well it will if you don't configure any filters corresponding to the crossover function you want!
Perhaps I am unclear about when to use the type as a tarhet using the Target Setting versus using the EQ filters to shape the speaker response. Is there a way to configure the filter order and type from the EQ filter menu? I only see HP, HP1 and so on.
Snap1.png
 
Right click on the measurement you want to select and use this option:
thanks. But I'm still not sure why it was added one more step from the existing method.
Of course, we can adapt, but the same is true that the process has not been simplified or accelerated, but rather increased.

Original (before beta) : Just Click. Done.
Beta : Right Click and Choose that options.

The same goes for the toggle. The integration of left-click into toggle definitely seems simple, but it's actually more complicated.

For example, if you were looking at a few graphs that were active and you were applying an IR window to one of them
Previously, I just click on what I want and I just click on the IR window, and that's it.
But you can't do left-click now, because that will untangle the toggle.
Then you think this was a beta, right-click it again, change it to Current, and then click the IR window again. (Or you have to enable it with an Alt keyboard arrow or number.)


So I've left a post before. I remember you saying no at all about whether you'd like to include options for the previous UI.
Then we'll keep using this UI.

Of course, we can adapt. But apart from the problem of adaptation, why it should be more cumbersome and why the process should be added is honestly... It's a bit confusing as I keep use.
Of course, I am always grateful for providing good programs.
Before 5.3 was officially released, I always used beta well, reported bugs often, and I remember enjoying using it.
But I still don't know about this beta right now from the beginning until now, so I left a honest post.
 
Last edited:
Perhaps I am unclear about when to use the type as a tarhet using the Target Setting versus using the EQ filters to shape the speaker response. Is there a way to configure the filter order and type from the EQ filter menu? I only see HP, HP1 and so on.
View attachment 75050
When chosing a HP or LP filter in the EQ filters. Is there a way of determining the filter type i.e Butterworth, L-R or Bessel and is there a way to increase/decrease filter order without using to filter Qs? I think the filter selection options under the Target Settings are more intuitive.
 
Select the Generic - generic or Generic - Extended equaliser options for crossover filter options. There are two at the end of the list for Generic - generic, for Generic - extended any filter position can be a crossover filter.
 
I'm still not sure why it was added one more step from the existing method.
Of course, we can adapt, but the same is true that the process has not been simplified or accelerated, but rather increased.
Consider the use of the selector bank for the overlay graphs and perhaps it will become clear. As with every GUI-driven software, everyone has their own idea how it should work.
 
Select the Generic - generic or Generic - Extended equaliser options for crossover filter options. There are two at the end of the list for Generic - generic, for Generic - extended any filter position can be a crossover filter.
Brilliant. I was not aware of that feature. Thank you very much.
 
Hi John,

Can we please have an option to save a single "highlighted or selected" measurement within the right click pop-up menu of the All SPL tab? Thanks.
 
When one clicks on the EQ button without any measurement loaded onto REW, an exception is generated,
Snap2.png


REW V5.40 Beta 58 running Azul Systems, Inc. JRE 1.8.0_432 64-bit on Windows 10 Locale: language en, keyboard ZA, windows-1252 on 1920x1080 at 96 DPI Running in C:\Program Files\REW


Message:
java.lang.NullPointerException
Stack Trace:
roomeqwizard.xK.A(y:1462)
roomeqwizard.xK.A(y:1185)
roomeqwizard.xK.Z(y:998)
roomeqwizard.xK.A(y:2365)
roomeqwizard.xK.A(y:1912)
roomeqwizard.xK.paintComponent(y:306)
javax.swing.JComponent.paint(JComponent.java:1056)
javax.swing.JComponent.paintChildren(JComponent.java:889)
javax.swing.JComponent.paint(JComponent.java:1065)
javax.swing.JLayeredPane.paint(JLayeredPane.java:586)
javax.swing.JComponent.paintChildren(JComponent.java:889)
javax.swing.JComponent.paint(JComponent.java:1065)
javax.swing.JLayer.paint(JLayer.java:433)
javax.swing.plaf.LayerUI.paint(LayerUI.java:79)
javax.swing.plaf.ComponentUI.update(ComponentUI.java:161)
javax.swing.JComponent.paintComponent(JComponent.java:780)
javax.swing.JLayer.paint(JLayer.java:428)
javax.swing.JComponent.paintChildren(JComponent.java:889)
javax.swing.JComponent.paint(JComponent.java:1065)
javax.swing.JComponent.paintChildren(JComponent.java:889)
javax.swing.JSplitPane.paintChildren(JSplitPane.java:1047)
javax.swing.JComponent.paint(JComponent.java:1065)
javax.swing.JComponent.paintChildren(JComponent.java:889)
javax.swing.JComponent.paint(JComponent.java:1065)
javax.swing.JComponent.paintChildren(JComponent.java:889)
javax.swing.JComponent.paint(JComponent.java:1065)
javax.swing.JLayer.paint(JLayer.java:433)
javax.swing.plaf.LayerUI.paint(LayerUI.java:79)
roomeqwizard.QC.paint(y:2131)
javax.swing.plaf.ComponentUI.update(ComponentUI.java:161)
javax.swing.JComponent.paintComponent(JComponent.java:780)
javax.swing.JLayer.paint(JLayer.java:428)
javax.swing.JComponent.paintChildren(JComponent.java:889)
javax.swing.JComponent.paint(JComponent.java:1065)
javax.swing.JComponent.paintToOffscreen(JComponent.java:5210)
javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1579)
javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1502)
javax.swing.RepaintManager.paint(RepaintManager.java:1272)
javax.swing.JComponent._paintImmediately(JComponent.java:5158)
javax.swing.JComponent.paintImmediately(JComponent.java:4969)
javax.swing.JLayer.paintImmediately(JLayer.java:415)
javax.swing.plaf.LayerUI.paintImmediately(LayerUI.java:717)
javax.swing.JLayer.paintImmediately(JLayer.java:410)
javax.swing.JComponent.paintImmediately(JComponent.java:4950)
javax.swing.RepaintManager$4.run(RepaintManager.java:831)
javax.swing.RepaintManager$4.run(RepaintManager.java:814)
java.security.AccessController.doPrivileged(Native Method)
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:814)
javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:789)
javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:738)
javax.swing.RepaintManager.access$1200(RepaintManager.java:64)
javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1732)
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
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.awt.EventQueue.dispatchEvent(EventQueue.java:728)
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)
 
When one clicks on the EQ button without any measurement loaded onto REW, an exception is generated
That could happen if the Y axis of the filter adjust graph is set to dBr. I have fixed it for the next build, in the meantime set the Y axis for that graph to something else.
 
Hi John in the latest beta, 5.40 beta 58 when using the alignment tool, if I click anywhere on the wave form the alignment tool windows goes to the back. it does not stay on top as it did before. Is there any option to make it always stay on top?
 
Dotted line is the actual phase response and does anyone know what the black line represents below?

1730532539333.png
 
Vice versa.
No, I have the phase response open in Overlays, too and green is the phase response. I just don't understand what the slightly different black phase response is since there's no offset at that point.

On a different note, I observe recently that "Calculate target level" only gets the level right in the second attempt. The first click will stop at 100dB for an actual level of around 105dB.
 
Last edited:
Builds updated today (beta 58) with these changes:
  • Added: Show busy indicator while updating FSAF signal
  • Added: Ctrl+click can be used to bring up the right click menus on macOS
  • Fixed: Filter text export for LSQ and HSQ shelf filters had incorrect Q values
  • Fixed: Selecting dBr as the Y axis on the SPL & Phase graph for a saved RTA measurement was not handled correctly
  • Fixed: FSAF measurement could give a "file too short" warning on changing the signal duration when not using a file
  • Fixed: API InputCalData structure fullScaleSineVrms field was mislabelled fullScalSineVrms
  • Fixed: API per-input cal file paths posted to /audio/input-cal were not saved properly in the cal data
Is there a changelog somewhere?
 
That's ultra useful!
 
Does the latest Beta have a known issue with the noisefloor reading incorrectly (or something related to that).

See my screenshots of just a quite room measurement...I'm comparing the results of 5.31.3 to Beta 58 (everything set up the same) and I'm getting wildly wrong readings with Beta 58 for the noisefloor, which has me concerned that I cannot trust the measurements (which do look about the same between versions).
 

Attachments

  • Screenshot 2024-11-02 162124.jpg
    Screenshot 2024-11-02 162124.jpg
    210.4 KB · Views: 14
  • Screenshot 2024-11-02 161934.jpg
    Screenshot 2024-11-02 161934.jpg
    201.9 KB · Views: 14
  • Screenshot 2024-11-02 162747.jpg
    Screenshot 2024-11-02 162747.jpg
    483.8 KB · Views: 13
See changelog posted above..


V5.40 beta 45 27th July 2024
  • Changed: Use frequency-dependent windows to reduce the noise floor of sweep distortion measurements
  • Fixed: Index out of bounds when saving an RTA peak measurement with multiple inputs and group averages enabled
 
in the latest beta, 5.40 beta 58 when using the alignment tool, if I click anywhere on the wave form the alignment tool windows goes to the back.
There have not been any changes to the alignment tool dialog. That dialog is owned by the All SPL graph and remains on top with viewing the All SPL graph (at least on Windows and macOS). It is hidden if you view another graph type.
 
Dotted line is the actual phase response and does anyone know what the black line represents below?
It is a preview of the response with the chosen delay, generated at 96 PPO. It looks like there is a bug with the smoothing application causing it to differ when the response is smoothed, I'll look at that.
 
I observe recently that "Calculate target level" only gets the level right in the second attempt.
Works fine for me at any level, if you have measurements that don't seem to work please provide them along with the EQ and target settings.
 
Back
Top